Cannot access a NSF mapped directory

[Bill Ostrander]

NFS Client = OpenVMS 7.3-2 TCPIP V5.4
NFS Server = Windows 2000 5.0 SP4

The TCPIP Mount command seems to succeed.
(Even the server log reports a successful mount)

However any attempt to access the structure times out with a failure such as:
-RMS-E-DNF, directory not found
-SYSTEM-F-TIMEOUT, device timeout

On the server no Event log entries or NFS log entries appear that correspond to the VMS access attempts.

The server has access allowed for "ALL MACHINES".

I cannot dismount the device specifically. I have to TCPIP Dismount /All.

Any suggestions would be appreciated.

Thanks,
Bill

[Petr Spisek]

Has it ever worked it?
If not, try to take the acction from basic again. Look to doc http://h71000.www7.hp.com/doc/732final/6526/6526pro_047.html#index_x_939

Mounting DNFS disk from client is the easiest from the NFS configuration. You need to start client NFS service and allowed access to server.

Petr

[Petr Spisek]

.... After mount your NFS disk, check it by TCPIP SHOW MOUNT

Petr

[Bill Ostrander]

Thanks.

Your reference to the documentation helped me realize we have no proxies set up yet not even a default. We will work on that.

Which raises the question - can NFS mounts succeed with an empty proxy database? Apparently they can.

BTW the TCPIP SHOW MOUNT also times out.

--Bill

[Bill Ostrander]

We did set up a proxy but still cannot access the NFS mounted directory.

$ sho dev/full disk$fs

Disk DNFS1:, device type Foreign disk type 7, is online, mounted, file-oriented
device, shareable, accessed via DFS or NFS.

Error count 0 Operations completed 6
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL
Reference count 1 Default buffer size 512
Total blocks 8380280 Sectors per track 0
Total cylinders 0 Tracks per cylinder 0
Logical Volume Size 2193045044 Expansion Size Limit 10841736

Volume label "FSLAB" Relative volume number 0
Cluster size 0 Transaction count 1
Free blocks unknown Maximum files allowed 0
Extend quantity 0 Mount count 1
Mount status System ACP process name "DNFS1ACP"

Volume Status: ODS-5, access dates enabled. {<-- /Struct=5}
Volume Status: ODS-2, caching is disabled. {<-- /Struct=2}

Still open to suggestions.

Thanks,
Bill

[Petr Spisek]

>Which raises the question - can NFS mounts succeed with an empty proxy database? Apparently they can.

Yes, i think you need proxy only to serving some nfs space to others. I haven't any proxy record on VMS for mounting nfs disk serving from unix server.


Can you type your mount command here? After succesful mount command TCPIP SHOW MOUNT must returns mounted device and path to nfs container on server.
Petr

[Bill Ostrander]

We've tried many different flavors of this TCPIP Mount command but here is the basic command:

TCPIP Mount DNFS1: fslab Disk$FS /Host="WHOW2K" /Path="/TEST_NFS"

--Bill

[Petr Spisek]

Hi,
mount command looks right.

Is the network access correctly configured? (the same vlan for server and client nodes or firewall rules are setting...)
You can sniff your attempt when the command is timed out - check who doesn't return packets.

I think problem could be on the NFS server (your Windows server). Especialy try to check rights and protections of mapped disk on NFS server.

Petr

[Bill Ostrander]

Thanks Petr for the replies,

We have thought about network issues so we put the W2K box and the VMS client box on the same segment but it didn't help. Sniffing might be worth a try.

We've tried everything we can think of with the W2K box to open it up. Like I said before, the W2K system acknowledges a good mount from the VMS system. But, it gets no indication at all when we try to access it from VMS. My gut feeling is we are not getting out of the VMS box.

I will leave this thread open a bit longer but also thinking of opening a similar question on the OpenVMS Networking forum.

Thanks again,
Bill

[Bill Ostrander]

Thanks Petr for the replies,

We have thought about network issues so we put the W2K box and the VMS client box on the same segment but it didn't help. Sniffing is a good idea.

We've tried everything we can think of with the W2K box to open it up. Like I said before, the W2K system acknowledges a good mount from the VMS system. But, it gets no indication at all when we try to access it from VMS. My gut feeling is we are not getting out of the VMS box.

I will leave this thread open a bit longer but also thinking of opening a similar question on the OpenVMS Networking forum.

Thanks again,
Bill