In my recently installed server, NIS client was not working/binding even though I install everything using same kickstart server.
The only difference was that this system is sitting in different VLAN and hence I needed to manually key in the NIS master/slave server information on this server.
Upon detailed troubleshooting, I found that NIS slaves/master servers names were not resolved by this server hence it could not find/translate the NIS servers and hence could not bind. The moment host name resolution became ok, NIS also was ok. :)
My checklist for NIS client troubleshooting:
1) Check VLAN (if NIS slave/master is in same VLAN as of server. If not, add entry in /etc/yp.conf)
2) Make sure NIS servers are pingable (with hostname and hostname resolution is working)
3) Check the network cable & network status
4) Restart portmap + ypbind.
Showing posts with label NIS. Show all posts
Showing posts with label NIS. Show all posts
Friday, June 17, 2011
How to troubleshoot NIS client on Linux?
Labels:
How-to series,
Linux fundamentals,
NIS
Tuesday, November 17, 2009
How to setup NIS client in different subnet in Linux?
I recently added one Linux client (from different subnet) to NIS master located in different subnet. Normally, they say that it is not possible to add NIS client without having NIS slave in the target VLAN. WRONG!
Almost everything remains the same as of normal NIS client addition process except editing /etc/yp.conf file. Add "broadcast" keyword into this file and restart ypbind using "service ypbind restart" and it should bind to any NIS master or slave available.
Please note that /etc/yp.conf should have only "broadcast" line enabled.. nothing else!
Almost everything remains the same as of normal NIS client addition process except editing /etc/yp.conf file. Add "broadcast" keyword into this file and restart ypbind using "service ypbind restart" and it should bind to any NIS master or slave available.
Please note that /etc/yp.conf should have only "broadcast" line enabled.. nothing else!
Labels:
How-to series,
Linux fundamentals,
NIS
Thursday, April 30, 2009
Netgroup (using NIS) implementation - Solaris
I wanted to limit only a certain number of users from NIS to login to some servers using NIS. The simplest way to do this is to use netgroups. It is NIS map created separately to restrict users to login certain machines, to export any file system to certain servers only and provide many other features.
To restrict users to any server, here are the simplest steps:
With "splgroup" netgroup in place, only "username1 - 3" will be allowed to login to the NIS client.
To restrict users to any server, here are the simplest steps:
Step 1:
On NIS server, edit "netgroup" map and add:
#tail -1 /etc/yp/netgroup
splgroup username1 username2 username3
Step 2:
On NIS server, Re-Make this map by doing following:
# cd /var/yp
# ./make netgroup
Step 3:
On NIS client (i.e. where I need to restrict users)
Edit /etc/passwd file and add the following line:
+@splgroup:x:::::
Edit /etc/shadow file and add following line:
+@splgroup::::::::
Edit /etc/nsswitch.conf file and in passwd entry, change as follows:
passwd: compat
Restart NIS client. For Solaris 10, it can be done by:
# svcadm refresh /network/nis/client
With "splgroup" netgroup in place, only "username1 - 3" will be allowed to login to the NIS client.
Subscribe to:
Posts (Atom)