home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.nfs
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!Sirius.dfn.de!chx400!bernina!hanke
- From: hanke@nessie.cs.id.ethz.ch (Norbert Hanke)
- Subject: Re: PC-NFS & NIS
- Message-ID: <1992Aug31.070610.21142@bernina.ethz.ch>
- Sender: news@bernina.ethz.ch (USENET News System)
- Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
- References: <1992Aug27.103457.5374@bernina.ethz.ch>
- Date: Mon, 31 Aug 1992 07:06:10 GMT
- Lines: 29
-
- In response to my newspost, tomiii@mtu.edu (Thomas Dwyer III) writes (by mail):
- >I was having the same problem when I upgraded to version 4.0,
- >and the answer seems to be this: make sure you put RNMFILE.EXE
- >on your bootdisk. Even though you want to use NIS, PC-NFS tries
- >to look at the local hosts file during the NET START RDR command.
- >If it cannot find RNMFILE.EXE in the PATH or NFSPATH, it fails
- >and prints the error message you describe.
- >
- >BTW, the local hosts file must exist, even if it is an empty file.
- >
- >
- >Hope this helps,
- >Tom.III
- >tomiii@mtu.edu
-
- This is exactly the solution to my problem: I didn't have RNMFILE.EXE
- present, now it works, with an empty hosts file.
-
- On quirk remains, however: trying to NET USE $NISSERVER:$HOME fails with
- the message
- NFS057F : $HOME may only be used if the network information service is up.
-
- Doing a NET NAME >NUL before NET USE makes also this problem disappear.
-
- Thanks, Tom, for the help!
-
- Norbert Hanke
- ETH Zurich, Switzerland
-
-