Sponsored Content
Full Discussion: Removing NIS configuration
Special Forums IP Networking Removing NIS configuration Post 302428944 by nitin on Friday 11th of June 2010 09:38:41 AM
Old 06-11-2010
I don't know much about SCO. But you can try this:

As always stop NIS:
Code:
# /usr/lib/netsvc/yp/ypstop

Remove the NIS config files in /etc:
Code:
# cd  /etc
# cp nsswitch.files  nsswitch.conf
# rm defaultdomain
# cd /var/yp/bindings
# rm  -r <your_domainname>

Remove automount configuration:
Code:
# vi  /etc/auto_master

And finally, reboot. Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Removing a replica server from NIS+

How can I remove a replica server from my NIS+ domain? From reading the man page, it looks like this will work nisrmdir -s hostname org_dir.domain.com. But it comes back with remove "org_dir.domain.com."? I am afraid that will remove all the tables associated with the domain, not just the... (1 Reply)
Discussion started by: 98_1LE
1 Replies

2. UNIX for Dummies Questions & Answers

NIS Configuration Help

I have a Solaris 5.5 with NIS set-up. My plan is to change IP address. I used the ifconfig command to change IP and updated the /etc/hosts file, the problem is that ypmake command is not yet available with Solaris 5.5 and I don't know how I can update my NIS map. ypcat hosts still shows my old IP... (2 Replies)
Discussion started by: inquirer
2 Replies

3. UNIX for Dummies Questions & Answers

NIS map mail.aliases specified, but NIS not running

Hi all, I just took over the admin role from someone and I wanna setup sendmail (just to send mail from the host) however, after I config all the resolv.conf, nssitch.conf, hosts file and when I try to send a mail out, after I punched ctl-D, it returned he following, "NIS map mail.aliases... (2 Replies)
Discussion started by: stancwong
2 Replies

4. UNIX for Advanced & Expert Users

SUSE 9 and 10 NIS clients with RedHat 8.0 NIS server not working

We have a RedHat 8.0 NIS master, with a RedHat 8.0 NIS Slave. We also have a small number of SUSE 9.1 and SUSE 10 machines here for evaluation. However, no matter what i do, the SUSE machines will not talk to the NIS Servers. If i broadcast for NIS Servers for the specified NIS domain, it... (1 Reply)
Discussion started by: fishsponge
1 Replies

5. UNIX for Advanced & Expert Users

Problem: Automounting Home directory for nis & nfs configuration doesn't work

Hi all, First of all, i am so sorry about my bad level in English writing. I have some problem in linux and i hope the experts of this forum to help me if they have enough time to reply to me. I have a scenario of configuring NIS and NFS in Redhat Linux environment such that user can login... (0 Replies)
Discussion started by: pioneer
0 Replies

6. Solaris

How to configure a NIS client bound to the NIS server in another subnet?

Hi, all. I have a Solaris client here needs to bind to NIS server in another subnet. Following is the configuration i made on the client, 1) edit /etc/inet/hosts to add an entry of the NIS server -- nserver01 2) execute `domainname` to set local NIS domain to the domain of the NIS server.... (1 Reply)
Discussion started by: sn_wukong
1 Replies

7. AIX

Slave NIS server configuration change

Hello Everybody, I have a question regarding SLAVE NIS SERVER in aix. We are using NIS master of Sun Solaris 9.0 which is on different subnet i.e. 10.197.93.0. And Our slave server is having AIX 5.3 installed which is on 10.207.13.0 subnet. I have a query regarding its name and ip address... (0 Replies)
Discussion started by: jit15975
0 Replies

8. Red Hat

PAM configuration: Kerberos authentication and NIS authorization problem

Hi, I've configured two linux boxes to authenticate against Windows Active Directory using Kerberos while retrieving authorization data (uids, gids ,,,)from NIS. The problem I ran into with my PAM configuration is that all authentication attempts succeed in order.i.e. if someone tried his... (0 Replies)
Discussion started by: geek.ksa
0 Replies

9. Solaris

Solaris 10 NIS client configuration

Hi, I have a Solaris 10 machine and trying to connect it to a Linux NIS Server. Up till now I have set up NIS so that it does find the NIS server and gets the user list. Automounter also mounts some directories from an NFS server. However, I can't get it to map the shadow passwords (they... (4 Replies)
Discussion started by: dop
4 Replies

10. UNIX for Advanced & Expert Users

Inquiry: NIS configuration setup

Hello, Good day. I would like to ask for your inputs on this scenario. Currently, we have a NIS virtual machine with a Solaris 10 (32-bit) OS. And also we have another virtual machine with the same OS. And I am asked to set-up a secondary NIS on this another VM, bring down the primary NIS and... (0 Replies)
Discussion started by: SystemAddict
0 Replies
nisauthconf(1M) 					  System Administration Commands					   nisauthconf(1M)

NAME
nisauthconf - configure NIS+ security SYNOPSIS
nisauthconf [-v] [mechanism,...] DESCRIPTION
nisauthconf controls which authentication flavors NIS+ should use when communicating with other NIS+ clients and servers. If the command is not executed, then NIS+ will default to the AUTH_DES authentication flavor when running security level 2. See rpc.nisd(1M). nisauthconf takes a list of authentication mechanism's in order of preference. An authentication mechanism may use one or more authentica- tion flavors listed below. If des is the only specified mechanism, then NIS+ only use AUTH_DES with other NIS+ clients and servers. If des is the first mechanism, then other authentication mechanism's after des will be ignored by NIS+, except for nisaddcred(1M). After changing the mechanism configuration, the keyserv(1M) daemon must be restarted. Note that doing so will remove encryption keys stored by the running keyserv process. This means that a reboot usually is the safest option when the mechanism configuration has been changed. The following mechanisms are available: +-----------------------------+-----------------------------+ | Authentication mechanism | Authentication Flavor | +-----------------------------+-----------------------------+ |des |AUTH_DES | +-----------------------------+-----------------------------+ |dh640-0 |RPCSEC_GSS using 640-bit | | |Diffie-Hellman keys | +-----------------------------+-----------------------------+ |dh1024-0 |RPCSEC_GSS using 1024-bit | | |Diffie-Hellman keys | +-----------------------------+-----------------------------+ If no mechanisms are specified, then a list of currently configured mechanisms is printed. OPTIONS
-v Displays a verbose table listing the currently configured authentication mechanisms. EXAMPLES
Example 1: Configuring a System with only RPCSEC_GSS Authentication Flavor To configure a system to use only the RPCSEC_GSS authentication flavor with 640-bit Diffie-Hellman keys, execute the following as root: example# /usr/lib/nis/nisauthconf dh640-0 Example 2: Configuring a System with both RPCSEC_GSS and AUTH_DES Authentication Flavors To configure a system to use both RPCSEC_GSS (with 640-bit Diffie-Hellman keys) and AUTH_DES authentication flavors: example# /usr/lib/nis/nisauthconf dh640-0 des Example 3: Transitioning to Other Authentication Flavors The following example can be used while adding credentials for a new mechanism before NIS+ is authenticating with the new mechanism: example# /usr/lib/nis/nisauthconf des dh640-0 Note that except for nisaddcred(1M), NIS+ will not use mechanisms that follow 'des.' EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error occurred. FILES
/etc/rpcsec/nisplussec.conf NIS+ authentication configuration file. This file may change or be removed in future versions of Solaris. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ SEE ALSO
nis+(1), keyserv(1M), nisaddcred(1M), rpc.nisd(1M), attributes(5) NOTES
A NIS+ client of a server that is configured for either dh640-0 or dh1024-0 must run Solaris 7 or later, even if the server is also config- ured with des. NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html. SunOS 5.10 12 Dec 2001 nisauthconf(1M)
All times are GMT -4. The time now is 05:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy