home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!wupost!spool.mu.edu!sol.ctr.columbia.edu!eff!news.byu.edu!ux1!fcom.cc.utah.edu!park.uvcc.edu!ns.novell.com!thisbe.Eng.Sandy.Novell.COM!terry
- From: terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert)
- Subject: Re: Trouble using an NFS filesystem
- Message-ID: <BuDutI.32z@Novell.COM>
- Sender: usenet@Novell.COM (Usenet News)
- Nntp-Posting-Host: thisbe.eng.sandy.novell.com
- Organization: Novell NPD -- Sandy, UT
- References: <1992Sep10.162146.1@woods.ulowell.edu>
- Date: Thu, 10 Sep 1992 22:08:06 GMT
- Lines: 52
-
- In article <1992Sep10.162146.1@woods.ulowell.edu> jackson@woods.ulowell.edu writes:
- >Now, for something related:
- >
- >After ifconfig'ing ec0 and successfully ftp'ing/ping'ing a host on our net,
- >I am having problems trying to access an NFS server. The NFS server is a
- >netware 3.11 box with Netware NFS v1.1. I can get the server volume to mount
- >on the 386bsd filesystem and running df gives an accurate report of the space
- >available, but I am unable to do anything in the directory where the NFS
- >volume is mounted. Trying to do an ls or cp'ing something into that directory
- >just gives me a permission denied error. Doing an ls -l of the mount
- >directory after I've mounted the volume shows the privledges as being:
- >
- > drwx------ 4 root 512 Sep 9 16:30 mcet1/
- >
- >It would seem as if I had the proper privledges, right? Last, if I explicitly
- >try to mount the NFS volume by hand with the command line:
- >
- > # mount /bsd386/@mcet1: /mcet1 (I know, I know, it should be /386bsd/ :-) )
- >
- >I get a message that reads "Can't get net id for host". I can't figure out if
- >I've got something set up incorrectly on the Netware NFS hosts's side or if
- >the problem is somewhere in how I've configured the 386bsd system. Anyone
- >want to offer any suggestions?
-
- 1. What are the permissions on the directory you are mounting over? I
- suspect that you don't have permission.
-
- 2. This information implies that you are root trying to access
- something in a directory owned by root on a remote machine. Have
- you done a "root=<client host name>" as an option on the exporting
- host? If not, you are coming in as id -2 ("nobody") and will not
- be allowed to access the directory. I realize that doing this is
- "a bit different" using NetWare as a server.
-
- 3. If you can't get an id for it, the host "mcet1" isn't in your hosts
- database. If it is, perhaps the "<directory>@<host>" syntax is
- broken on your NFS. Try "<host>:<directory>" instead. One way
- this "break" might show up is your use of a ":" and an "@" in the
- same line, configuing BFS into thinking "/bsd386/@mcet1" was the
- host name and "" was the file name (the part with no whitespace
- seperator following the colon is empty in the line you gave).
-
- Please post a followup telling which, if any of these, solved your problem.
-
-
- Terry Lambert
- terry_lambert@gateway.novell.com
- terry@icarus.weber.edu
-
- ---
- Disclaimer: Any opinions in this posting are my own and not those of
- my present or previous employers.
-