HELP: VMS as an NFS client to Windows or Linux - primer please

OK, so perhaps we can start and do a primer for VMS8.2 as a client to NFS on Windows2003 and/or Linux.

Starting point:
- I have an NFS server on Windows2003R2 and SuSE Linux and Solaris10 and Reh Hat EL5 and can connect any client OS to them using anonymous access rights - except VMS (which I can't even connect when I specify username/GID/UID). I feel it is safe to say the NFS servers are working OK on all the OSes.

- I can ping the server names from VMS
- the files in the NFS share area are full access to anyone, including anonymous - the directory is the same
- tcpip sho proxy shows my VMS username with UID 0 GID 0 outbound to all the NFS servers
- Windows mapping shows the "unix" username the same as my VMS username and it is mapped to a Windows domain administrator account
- The Windows domain administrator account has full access to all files (I checked) and also the share and all the directories.

- I can issue the following commands to any OS noted above and the command(s)complete OK:
-tcpip mount DNSF0: data /host="servername" /path="NFSshareName" /system /struct=5 /noadf
-tcpip mount DNSF0: data /host="servername" /path="NFSshareName" /struct=5 /noadf /gid=0 /uid=0
-tcpip mount DNSF0: data /host="servername" /path="NFSshareName" /struct=5 /noadf /gid=-2 /uid=-2
where DNSF0: can also be DNSF1: or any other integer to give it the same mount point each time
where NFSshareName has been the NFS share as exported by the OS, or the actual path (/f/data/nfs/)

- I cannot successfully do dir dnsf0:[000000] - I typically get device timeout....however, thanks to a reply on a similar post a couple of days ago, I added to /NOADF flag and now I get -RMS-E-PRV, insufficient privilege or file protection violation, AND now Windows is logging mapping errors - still works fine with Solaris, SuSE etc....

So, the /NOADF flag got rid of the timeout but exposed a mapping flaw(?). On the Windows side, anonymous access is allowed on the share and my VMS username is mapped to a Windows Domain Administrator account with full access to everything - so why the mapping error......
.

Relevant Pages

  • user of nfs mounted dir is 4294967294
    ... for some reason after sucessfully mounting a Windows Services For Unix NFS share on the linux side as user or as root, for the mount owner the user id is -2. ... I'm not using NIS on the Windows server, but manual user name mapping. ...
    (comp.os.linux.networking)
  • Re: Windows 2000 Server and truly permanent network mappings?
    ... there cannot be a mapping because there are no permissions (credentials). ... NFS and other network file sharing protocols are for hosts not just users. ...
    (microsoft.public.windows.server.general)
  • Re: NFS Server einrichten
    ... Nun also TCPIP 5.5 ECO1 ... das mapping fest eingetragen. ... Danach mit @tcpip$nfs_shutdown und -startup NFS neu gestartet damit sich ...
    (de.comp.os.vms)