home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.nfs
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!jvnc.net!yale.edu!ira.uka.de!chx400!bernina!hanke
- From: hanke@nessie.cs.id.ethz.ch (Norbert Hanke)
- Subject: PC-NFS & NIS
- Message-ID: <1992Aug27.103457.5374@bernina.ethz.ch>
- Summary: PC-NFS 4.0a fails to find NIS server, 3.5c works
- Sender: news@bernina.ethz.ch (USENET News System)
- Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
- Date: Thu, 27 Aug 1992 10:34:57 GMT
- Lines: 43
-
- A few days ago we upgraded our installation from PC-NFS 3.5c to 4.0a, and
- since then, PC-NFS has problems finding the NIS server.
- Exactly the same configuration works ok with 3.5c but has problems with 4.0a.
-
- We issue the following commands:
-
- NET NISDOMAIN ournisdomain
-
- --> [PC-NFS is Installed]
-
- NET START RDR
-
- --> NFS126W : Unable to get hostname by ip addr (cor.rect.ip.address)
-
- NET NAME
-
- --> The name of this system is UNKNOWN
- --> , and its IP address is cor.rect.ip.address.
- --> The subnet mask is 255.255.255.192 [0xffffffc0].
- --> It is in network information service domain ournisdomain, for which there is no NIS server.
- --> There is no authentication (PCNFSD) server
- --> No gateway is currently defined.
- --> You are logged in as nobody, with UID -2 and GID -2.
- --> It is Thu Aug 27 10:58:52 1992, CET
-
- It seems that RARP works correctly: the PC knows its IP address after the
- NET START RDR command, also the subnet mask is correct. But it's unable to
- contact the NIS (and simulatinous PCNFSD) server.
-
- There exists a workaround, however: If I replace the simple NET START RDR from
- above with the following sequence, everything works ok, apart from the same
- error message as described above.
-
- NET START RDR
- NET NISSET ournisserver
- NET STOP RDR
- NET START RDR
-
- Any explanations for this behaviour? Any help is appreciated.
-
- Norbert Hanke
- ETH Zurich, Switzerland
-
-