I have a red hat 2.4.9-17 instance that I am having trouble with the YP/NIS.
I have referenced the red-hat manual and "fuzzy animal" book on the subject and cannot find how to resolve this. Here is the background and symptoms: I set up an NIS client. To do this I: 1. Made certain portmap was running. 2. changed /etc/resolv.conf to include several valid DNS servers. 3. added the master NIS server to /etc/hosts. 4. change /etc/sysconfig/network Added "NISDOMAIN=xxxx" . 5. change /etc/sysconfig/authconfig to USENIS=yes. 6. change /etc/yp.conf to include domain xxxx server yyyy etc. 7. changed /etc/nsswitch.conf to use yp first for passwd and group. 8. added the + entries to passwd and host. 9. start yp client with "ypbind -ypset" (necessary since no NIS servers are local on this sub-network) and then "ypset yyyy". 10. "ypwhich" returns yyyy as expected. 11. a "ypcat passwd | grep userid" returns the entry as expected. IT WORKS! Right? Wrong.... A long list of /u/userid shows the NIS is not resolving the UID to a CID. AND worse, after a time (about 15 seconds) ypwhich and ypcat return "Domain not bound" errors. For some reason the binding is not holding. It doesn't matter whether or not I issue yp related commands. After working with this for several days, I went ahead and configured this machine to be its own yp secondary server. But when I bind to the localhost it still drops after a short time. ???? It also doesn't matter if I bind to an IP address, master NIS server, slave NIS server, or local NIS server, it still drops after about 15 seconds. Has anyone experienced a similar phenomena and how did they correct the problem? Oh yes, When I run ypbind it creates four tasks rather that just one like other UNIX systems I am familiar with. Is this a problem and somehow related?
