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



JF Mezei wrote:
I don't recall how I succeeded this yet.

But this is what SHOW MOUNT/FULL shows:
$ tcpip show mount/full
_DNFS1:[000000] mounted
BRAKES.vixenation.ca:/
Transport TCPIP-UDP Writing Enabled
Read/write size 8192/8192 Write conversion Enabled
RPC timeout 0 00:00:01.00 ADF usage USE,UPDATE,CREATE
RPC retry limit 4 Fileids Unique
Attribute time 0 00:00:15.00 Server type UNIX
Directory time 0 00:00:30.00 Advisory Locking Disabled
Cache Validation MODIFY TIME Default user [DECNET]
Superuser No Default UID,GID 501,501


501,501 is the uid/gid of my account on the mac. So by default, the mac
lets the vms machine act as me in terms of file accesses.

But I also have a proxy for both incoming and outgoing mapping my VMS
username to 501,501, and mapping SYSTEM to 0,0

To get ODS5 capabilities, you need to specify the server type of UNIX,
even if the doc says it is there by default.

Hi JF

What is your mount command, as I can't see a path in the listing above?

If I use tcpip mou/host="x.y.z"/path="NFSdata" etc...(which is the NFS share exported name ) I get:
$ tcpip sho mou/fu
_DNFS1:[000000] mounted
monitorserver.x.y.z:nfsdata
Transport TCPIP-UDP Writing Enabled
Read/write size 8192/8192 Write conversion Enabled
RPC timeout 0 00:00:01.00 ADF usage NOUSE,NOUPDATE,NOCREATE
RPC retry limit 4 Fileids Unique
Attribute time 0 00:00:15.00 Server type UNIX
Directory time 0 00:00:30.00 Advisory Locking Disabled
Cache Validation MODIFY TIME Default user [DEFAULT]
Superuser No Default UID,GID 0,0

If I use tcpip mou/host="x.y.z"/path="/d/nfsdata/" etc...(which is the disk/directory structure location on the windows server) I get:
$ tcpip sho mou/fu
_DNFS1:[000000] mounted
monitorserver.x.y.z:/d/nfsdata
Transport TCPIP-UDP Writing Enabled
Read/write size 8192/8192 Write conversion Enabled
RPC timeout 0 00:00:01.00 ADF usage NOUSE,NOUPDATE,NOCREATE
RPC retry limit 4 Fileids Unique
Attribute time 0 00:00:15.00 Server type UNIX
Directory time 0 00:00:30.00 Advisory Locking Disabled
Cache Validation MODIFY TIME Default user [DEFAULT]
Superuser No Default UID,GID 0,0

0,0 doesn't exist - so I deleted the mappings in Windows and started by creating a group mapping of 4 for system and 100 for users. I then mapped users with 1 for domain admins and also 1 for my windows username.

So, when I issue the mount command I have now tried it with /UID=1/GID=4 (VMS system account UIC) and /UID=1/GID=100 (my vms UIC). Both mount fine but neither will not allow me to list the files - I still get a user mapping error - only on Windows, the others still work fine *without* any of the crazy flags.......

So, using a /UID/GID that matches a VMS UIC still gives me the RMS-E-PRV, but *doesn't* give a windows mapping failure!!!!! By default, the anonymous UID/GID on windows is -2,-2. If I change that to 1,4 (ie VMS system), then I again get windows mapping failures even if I mount with /UID=1/GID=4.

In summary, on VMS using a "real" UIC to map to a windows UID/GID makes no difference to the mount result, but *does* stop the windows mapping errors in the log file. However, I still get the RMS-E-PRV, so VMS still doesn't like something.....
.