  Configuring TCP/IP (UCX) NFS? 
 The Question is:
 
I'm trying to configure NFS on Alpha OpenVMS 7.1-1H1 with UCX version 4.1. I
would like to
access the file system with NT Server 4.0 as client.
The hosts can "see" each other and FTP (WRQ Reflection) works fine. NFS,
PC-NFS and portmapper services on Alpha are enabled, the
file system is mapped and exported, proxy user
is created with 1,4 (gid,uid).
But when remote user tries to log on following
message apears:
"NFS logon failed: The PCNFSD deamon failed the requested authentication."
The same message appears by Windows 95 remote user.
Next I tried to acces the NFS with Digital Unix client (Unix version 4.0D).
I came a few steps further but also wasn't successful.
On the Unix client the message was:
"Can't access /test/nfsdir: Permission denied"
and on OpenVMS (NFS server) in the log file
SYS$SYSDEVICE:[UCX$NFS]UCX$NFS_TK533_LOGFILE.LOG
appeared messages:
 
%UCX-E-NFS_PROGVS, invalid RPC program version number
-UCX-S-NFS_RPCHDR, xid = 40FCDDE0  program = 100005  version = 3  procedure
= 1
-UCX-S-NFS_CLIENT, uid=4  gid=1  host_name = tk500.mb.telekom.si
 
%UCX-E-NFS_BFSCAL, Operation STATFS   failed on file /test/nfsdir
-UCX-S-NFS_CLIENT, uid=4  gid=1  host_name = tk500.mb.telekom.si
-SYSTEM-W-NOSUCHFILE, no such file
 
(What is RPC?)
 
/test/nfsdir  is the mapped and exported filesystem
tk500.mb.telekom.si  is the Unix client full host name
tk533.mb.telekom.si  is the OpenVMS server full host name
The proxy user had the same username, password and gid/uid on both - server
and client. On server the user had all privileges and uic [1,4]
I also experimented with other user qualifiers.
 
Thank you in advance
Robert
 
 
 The Answer is:
 
  Please install the current TCP/IP Services for OpenVMS (UCX) V4.1 ECO
  kit, or please upgrade to current (V5.1 or later, as of July 2001)
  with the associated ECO kit.
 
:%UCX-E-NFS_PROGVS, invalid RPC program version number
:-UCX-S-NFS_RPCHDR, xid = 40FCDDE0  program = 100005  version = 3  procedure
:= 1
:-UCX-S-NFS_CLIENT, uid=4  gid=1  host_name = tk500.mb.telekom.si
 
  This is part of the normal and expected protocol negotiation with
  an environment comprised of a mix of NFS V3 and NFS V2 protocols.
 
:%UCX-E-NFS_BFSCAL, Operation STATFS   failed on file /test/nfsdir
:-UCX-S-NFS_CLIENT, uid=4  gid=1  host_name = tk500.mb.telekom.si
:-SYSTEM-W-NOSUCHFILE, no such file
 
  Find out what happened to and where the /test/nfsdir file is, and
  make certain that it it is valid and accessable.  (The Wizard would
  expect this to be TEST:[NFSDIR].  TEST must be defined in the context
  visible to the NFS server -- this usually means a system-wide logical
  name TEST.  The Wizard would recommend against terse logical names
  such as TEST, as these can conflict with applications and tools also
  using TEST -- and this can lead to strange and interesting behaviour.)
 
  Please contact the customer support center for further assistance.
 
 
