NFS Client HCLNFSD Authentication Error
(Last modified: 19Apr1999)
This document (2917614) is provided subject to the disclaimer at the end of this document.
Symptom
Customer can link from LAN WorkPlace 5 for MS Windows and DOS but with LAN WorkPlace Pro for Windows 95 he gets... "wnfs4001: authentication not supported by server". Verified he's pointing to the correct authentication server.
They are using Sun Solaris ver 2.5.1 and the hclnfsd daemon was ver. 5.1.0.1
Troubleshooting
WFNS4001: Authentication is not supported by the Server. Using Default UID and GID's
Some probable causes of this error include:
1.There is no PCNFSD running on the NFS server.
2.The first attempt to authenticate failed either because of an NIS authentication failure or because no NIS or PCNFSD server was available during the authentication cycle. A netmon trace my be necessary to further investigate this problem.
If you are attempting to mount a UNIX system, verify that there is a portmapper, pcnfsd and optionally nlockmgr or lockd program running on the server as well (if file locking/sharing is to be implemented).
NOTE: This can be checked by telneting to the UNIX machine and typing at the prompt:
rpcinfo -p hostname (-p for processes running).
In the following example, the program number will be listed first, followed by the version number, type of protocol, port number and program name.
- EXAMPLE -
isc|2|30>rpcinfo -p servername
program ver proto port pgm name
100000 2 udp 111 portmapper
100000 2 tcp 111 portmapper
100005 1 udp 1025 mountd
100003 2 udp 2049 nfs
100021 3 udp 1026 nlockmgr
150001 1 udp 1027 pcnfsd
150001 2 udp 1027 pcnfsd
NOTE: This can also be checked by telneting to the UNIX machine and typing at the prompt:
ps | grep nfs
This command shows all processes running that have "nfs" contained within them.
NOTE about RISC AIX: By default, PCNFSD is enabled to run upon boot-up. If however it is not found in the "rpcinfo -p" listing explained below, there is configuration file in the "etc" directory called "inetd.conf" which activates and deactives these daemons. Any program from the above list that should be started upon boot-up which isn't loading can be added to this file or activated by removing the slash mark which was used to remark that program out.
NOTE about Sun Solaris 2.x: We believe that mountd & nfsd are started by a program called "share" on Sun Solaris 2.x systems.
If the user wishes to mount as a default (nobody) user without authentication, have him/her delete the Username and Password fields in the Connect box before pressing Enter or O.K. NFS protocol dictates that the default U.I.D. and G.I.D's are -2, -2 for a nobody user.
NOTE: LAN WorkPlace Pro does not support AUTH_UNIX, nor does it support BWNFSD or HCLNFSD.
If the UNIX host is a SUN Solaris with a 2.x operating system: The PCNFSD.TAZ file is from the Sunsoft forum, PCNFS Family on compuserve as well as the Frontier BBS and contains both source code and the specific executable code for Solaris 2.x operating systems. Once this file has been obtained, the administrator must:
1.copy this file onto a UNIX machine as "pcnfsd.tar.Z".
2.on the UNIX, run the command "uncompress pcnfsd.tar.Z"
3.on the UNIX, run the command "tar xvf pcnfsd.tar"
4.follow the directions in the README file.
The alternatives you have are to use NIS authentication or point NFS Client to a different machine that does have PCNFSD.
Cause
LAN WorkPlace 5 uses an NFS Client licensed from Beame & Whiteside which later became Hummingbird. The daemon was BWNFSD or HCLNFSD. LAN WorkPlace Pro uses an NFS Client licensed from Frontier and the host daemon should be PCNFSD.
Solutions
Customer used the latest PCNFSD daemon from Sun and everything works fine now.
document
| Document Title: | NFS Client HCLNFSD Authentication Error |
| Document ID: | 2917614 |
| Creation Date: | 27Nov1996 |
| Modified Date: | 19Apr1999 |
| Revision: | 4 |
| Novell Product Class: | Connectivity Products |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.