Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!news.cs.su.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!pipex!uunet!world!mcgovern From: mcgovern@world.std.com (Brian J McGovern) Subject: NFS and toor... Message-ID: <CLFDtI.n1A@world.std.com> Organization: The World Public Access UNIX, Brookline, MA References: <dvdjnsCL5IHL.A4E@netcom.com> <CLC3y2.JAF@cix.compulink.co.uk> <2k2iqg$96a@hrd769.brooks.af.mil> Date: Fri, 18 Feb 1994 15:03:16 GMT Lines: 18 I've been having a rather interesting problem with FreeBSD 1.0's NFS. If anyone has seen anything similar, I'd like some input as to cause/resolution. Thanks in advance and here goes. I recently installed FreeBSD 1.0 here at work as a quasi-file server. I'm playing around with several network operating systems, and NFS is one I'd like to be compatible with, as rumor has it my company plans to move in that direction soon. I am able to have the FreeBSD system mount to any other system (being logged in as root, won't work with other ids). The problem is when I try to have my PC mount to the FreeBSD system. I'm using FTP's PC/TCPIP package (version 2.2) to make the connection, with a ported PCNFSD from their host (vax.ftp.com), and it seems to work ok. However, when I go to mount to the system, I can only establish drives when I use the uid of "toor". If I use any non-root uid, I get "RPC: Authentication error"s, and if I use root, I get invalid password. Seems pretty bizzare that only toor would work. Any ideas wouldbe helpful and appreciated. -Brian