Updating netid byname callback timed out
Edit the /etc/sysconfig/network file In Red Hat-based distributions need to add the NIS domain name we wish to use in the /etc/sysconfig/network file. You will have to delete the /var/yp/LINUX-NIS directory and restart portmap, yppasswd, and ypserv before you'll be able to do this again successfully.For this example, we will call the domain "LINUX-NIS". On Redhat, you can now start the ypbind and the ypxfrd daemons because the NIS domain had been initialized and the files have been created.[[email protected]]# /etc/init.d/ypbind start Binding to the NIS domain: [ OK ] Listening for an NIS domain server.Both Linux distributions have a configuration file for YP. NIS servers also need to be NIS clients themselves, so we will have to edit the to point this file towards the server itself, or localhost. [[email protected]]# /etc/init.d/ypxfrd start Starting YP map server: [ OK ] [[email protected]]# chkconfig ypbind on [r[email protected]]# chkconfig ypxfrd on [[email protected]]# rpcinfo -p localhost program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100003 nfs 100003 nfs 100021 nlockmgr 100021 nlockmgr 100021 nlockmgr 100004 2 udp 784 ypserv 100004 1 udp 784 ypserv 100004 2 tcp 787 ypserv 100004 1 tcp 787 ypserv 100009 1 udp 798 yppasswdd 600100069 1 udp 850 fypxfrd 600100069 1 tcp 852 fypxfrd 100007 2 udp 924 ypbind 100007 1 udp 924 ypbind 100007 2 tcp 927 ypbind 100007 1 tcp 927 ypbind New NIS users can be created by logging into the NIS server and creating the new user account.We now need to start a couple of the NIS daemons in the /etc/init.d directory. In this case, you'll create a user account called nisuser and give it a new password.In extreme cases where local server binding is not possible, use of the options can result in serious security breaches because while the daemons are running, anyone can alter server bindings causing trouble for others and permitting unauthorized access to sensitive data.If you must start program version netid address service owner ...
If many NIS clients are failing to bind properly, the problem probably exists on one or more of the NIS servers. One client has problems, but other clients on the same subnet are operating normally.This has always worked for me on SLES 11 setups, the new map gets built on the master and then pushed out to the slave.