The problem has been resolved, I received the following mail, explaining how
:
I have found the solution to the pcnfs problem by removing the -i switch
from the mountd daemon. This switch instigates a requirement for client ip
address resolution (via /etc/hosts) which is not used here. The strange
thing is that under Dec Unix 3.2C I could not make connections without the
-i switch. I.e. even though client resolution was used. This seems to
indicate that there may have been a problem with 3.2C and that 4.0F is ok.
Still awaiting a call back from Compaq support.
Many thanks to John Joehnk, Pete Joseph and Frank Wortner for their
responses which included : ensuring that the mountd had both -i and -n
switches (!!!?!!!), no underscores are present in hosts or exports files and
checking that PCNFS=1 in rc.config.
Original Posting :-
> Hello Again
>
I have today upgraded an Alphaserver 1000 4/266 from DU V3.2C to TU V4.0F
with patch kit 1, using the installupdate process following the steps
3.2C->4.0->4.0B -4.0D->4.0F
Prior to the upgrade the system was PCNFS exporting a directory to remote
PC's running Windows 95 and a product called Lan Workplace Pro (from Novell
I believe).
Since the upgrade the PC clients have been unable to mount the drives from
the Alphaserver.
Has anyone seen anything similar to this ?
-------------------------------------------------------------------
Standard Email disclaimer follows for legal reasons....
The information in this e-mail is confidential and is intended for the
addressee only. Copying or use by anybody else is not authorised. Its
content does not necessarily represent the opinion of Hamilton Rentals
PLC (part of the Compel Group) or any of its affiliates. If you are not
the intended recipient, please advise the sender by return e-mail.
This email was scanned for over 40,000 known viruses by
kerberos.hamilton.co.uk. It was deemed clean for transmission.
--------------------------------------------------------------------
Received on Fri Oct 01 1999 - 18:29:13 NZST