home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!waikato.ac.nz!aukuni.ac.nz!raymond
- Newsgroups: comp.sys.sgi
- Subject: NIS failure whilst NFS still works
- Message-ID: <1992Sep15.232907.25403@ccu1.aukuni.ac.nz>
- From: raymond@ccu1.aukuni.ac.nz ( Raymond W L Martin)
- Date: Tue, 15 Sep 1992 23:29:07 GMT
- Organization: University of Auckland, New Zealand.
- Keywords: NIS NFS respond client master ypbind
- Summary: An NIS client was changed to a different subnet. NIS failed NFS OK.
- Lines: 22
-
- Our Local network was altered so that one of our NIS clients remained in
- c class subnet 1, eg 192.0.1 and the master and another client moved
- to c class subnet 3, eg 192.0.3 with a router 192.0.1.132 between them.
- NIS works fine for the master and client on subnet 3 and NFS
- works through to subnet 1 OK but as soon as I start the ypbind on the
- subnet 1 client the message ypbind[nnn]: NIS v.[12] server not
- responding for domain "cc-yp"; still trying occurs. A df command takes
- ages to run and after a few of these messages finishes. Attempted NIS
- logins fail and the ypbind messages continue.
- The only cure is to kill off ypbind.
-
- Can anyone enlightened me. It appears that NIS is interfering
- with a perfectly well routed system!
-
- Ray Martin
- IRIX administrator
- Computer Centre
- Auckland University
- New Zealand
-
-
-
-