VMS as NFS client - solved!!!!! (almost)

Firstly,

Thanks to all who contributed to this discussion, even though at times you must have been frustrated with my replies and lack of progress (not more than me, believe me!!)

The problem turns out to be a Windows problem - maybe; more on the what or why soon. I have tested this on Windows2003R2 Services for Unix and on Windows2003 Services for Unix v3.5 (different products). The "error" is the same on both and the solution applies to both and the bit of weirdness to come applies to both.

So, an NFS share is set up on the Windows server. I don't need/care about username mapping as this is all internal and I am happy with anonymous access. The share is set to allow anonymous, with a UID/GID of 100/100 (this to get around the -2 translation issues). NFS/UNIX permissions are set to owner/other full access. The Windows folder/file protection is set to Domain Admins/Everyone full access.

Solaris10, SuSE, RedHat and True64 can all access the files using a UID/GID of 100/100. There is *no* name mapping set up on Windows as I am telling/forcing the clients to connect as anonymous - this all works fine.

VMS uses $tcpip mount dnfs1: /host="x.y.z"/path="nfsdata"/system/noadf/struct=5/UID=100/GID=100

The mount works fine, reading, however, produces the RMS-E-PRV error but *nothing* is logged in the Windows log files other than the mount/unmount success - Windows apparently doesn't see a name mapping error because there is no name mapping - this is anonymous access. Wireshark shows the traffic I identified earlier.

Out of the mist came the memory of Windows Everyone not *really* being everyone, so I also added ANONYMOUS LOGON to the Windows file/folder protection list entries with full access - and - VOILA!! It works!!

Now for the weirdness, using the ANONYMOUS LOGON entry in the Windows file/folder protection makes some sort of sense when you think about it (VMS is using anonymous access to get to NFS), but why don't Linux/UNIX clients need it on to work?

I removed ANONYMOUS LOGON from the Windows entries, restared the NFS server and then had the Linux clients connect and read - they did so without any problems but VMS still failed. Put back the ANONYMOUS LOGON and VMS client works, as do the remainder.

So, someone else can work that one out - I still think that something is broken on the VMS side.....

Again, thatnks for all those who provided broad shoulders upon which I could stand to see a solution off in the distance.
.

Relevant Pages

  • Re: Drag it to the trash...
    ... There might be a piece of software utility out there to help in finding and administering these "roaming profiles" for windows. ... A lot of MSDOS programmers entering into the VMS system schools abhorred vms at first, but later it sank in to just how flexible the system was designed to be. ... the so called installer is basically just a script that has been given priviledges to create files and directories, make changes to the system logical tables, and creating new aliases. ... in hardware to do all that. ...
    (comp.sys.mac.advocacy)
  • Re: In the Shallow End
    ... When a document claims how an API is supposed to be used and then gives the user examples that actually work, ... Vague in your instance means you have no context to VMS or UNIX of that era. ... Windows offers lots of this stuff. ... That's why Apple had to dump a whole paradigm to plunge ahead and take the lead. ...
    (comp.sys.mac.advocacy)
  • Re: VMS as NFS client - solved!!!!! (almost)
    ... Windows-side is *only* needed for the VMS client to work properly, all the other clients work without it, so VMS must at least chare some of the blame. ... In this case it appears that all the clients are able to mount - so it is safe to expect that the server (Windows) and clients all meet the functionality and compliance test. ...
    (comp.os.vms)
  • Re: "Shanghai Stock Exchange" and OpenVMS
    ... Windows was shipping without any "documentation". ... "right out of the box" VMS has no applications at all. ... Guess it depends on the style of manuals you are used ... that I need to use the MS-DOS command window in the first place!)? ...
    (comp.os.vms)
  • Re: "Shanghai Stock Exchange" and OpenVMS
    ... Windows was shipping without any "documentation". ... What about VMS as a back-end? ... have never found the VMS manuals to be all that readable or easy to ... where's the secret documentation for all the MS-DOS commands, ...
    (comp.os.vms)