Xref: utzoo comp.protocols.nfs:446 alt.sys.sun:65
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!texbell!texsun!newstop!east!hinode!geoff
From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs,alt.sys.sun
Subject: Re: pcnfsd from inetd.conf, SunOS 4.0.3 question.
Message-ID: <892@east.East.Sun.COM>
Date: 5 Oct 89 14:48:53 GMT
References: <27622@amdcad.AMD.COM>
Sender: news@east.East.Sun.COM
Reply-To: geoff@East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Followup-To: comp.protocols.nfs
Organization: Sun Microsystems, Billerica MA
Lines: 71

In article <27622@amdcad.AMD.COM> indra@amdcad.AMD.COM (Indra Singhal) writes:
>I just installed pcnfsd and popd on our Sun 3/280 running SunOS 4.0.3. 
>I have the following entry in /etc/inetd.conf:
>
>pcnfsd/1 dgram	rpc/udp	wait	root	/usr/etc/rpc.pcnfsd	rpc.pcnfsd
>
>and I start /usr/etc/popd from /etc/rc.local.
>On the PC side, testing is being done using an old IBM XT with a 3C501
>card running PC-NFS 3.0.

You ought to upgrade to 3.0.1, on general principles....

>Strangely: I am able to mount a disk on the PC and type out an ascii
>	   file successfully even though the process table does not
>	   show that rpc.pcnfsd is running.

Nothing strange about it. The current version of PC-NFS does not
require that you log in, so you can mount and access file systems
as NOBODY without pcnfsd being involved.

[I say "the current version" because we have been asked by many
people to fix things so that access as NOBODY is disallowed.
Opinions?]

Furthermore, when starting a service through "inetd" you wouldn't expect
to see the process running. Instead you should use "rpcinfo".

>	   I am unable to get logged in, authentication fails. Login as
>	   noboby (UID -2, GID -2) results.
>
>	   I am unable to redirect LPT1: (with: net use LPT1: \\host\lp).
>	   I get: NFS033F: Unable to contact PCNFSD daemon on server ...

Both of these are consistent with pcnfsd not being active, or (more
precisely) with inetd not registering a port for the pcnfsd program with the
portmapper.

>If I then manually issue: /usr/etc/rpc.pcnfsd (as root) to start the
>daemon, I get success all around.

Bingo.

>Does this mean inetd is not being able to start rpc.pcnfsd? How am I able
>to mount a disk on to my PC without rpc.pcnfsd even without
>authentication? What can I do to fix it?

I assume that the line:

pcnfsd         150001

appears in /etc/rpc. Even with this, some users still have problems;
the simplest fix is to change inetd.conf to include the program
number instead of the name, thus:

150001/1 dgram rpc/udp wait    root    /usr/etc/rpc.pcnfsd     rpc.pcnfsd

Not sure why this works, but it does. (Probably descriptor starvation
somewhere.)

If this STILL doesn't fix things, you may be trying to start too many
services through inetd. I haven't checked the 4.0.3 version, but earlier
inetd's were limited to 24 listen's (derived from the number of descriptors
available minus 8 for other purposes). Try commenting out stuff you don't need.

>iNDRA | indra@amdcad.AMD.COM                       


Geoff Arnold,                              Internet: geoff@East.Sun.COM
PCDS Group, Sun Microsystems Inc.
---------------------------------------------------------------------------
"Who's next?" "Me, doctor?" "No, ME doctor, YOU patient." (Graham Chapman, RIP)