NFS - can not connect to export folder

[IFX_1]

Hi All,
I export a folder in VMS using add export but when I try to connect via WINDOWS MAP, I can not find the folder. Or I get the error \\10.83.146.76\statsapp\statsapp\emes\ network path can not be found.

Any reply would be very much appreciated.

TCPIP> sh export

File System Host name

/statsapp/statsapp/emes *
TCPIP> sh map
Dynamic Filesystem Map
Pathname Logical File System

/statsapp $1$DGA1336:
TCPIP> sh proxy

VMS User_name Type User_ID Group_ID Host_name

STATSAPP1 CD * *
STATSAPP1 OND -2 -2 *

TCPIP> show service nfs/full

Service: NFS
State: Enabled
Port: 2049 Protocol: UDP Address: 0.0.0.0
Inactivity: 0 User_name: TCPIP$NFS Process: TCPIP$NFS
Limit: 1 Active: 0 Peak: 0

File: TCPIP$SYSTEM:TCPIP$NFS_RUN.COM
Flags: None

Socket Opts: Rcheck Scheck
Receive: 64000 Send: 64000

Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
File: SYS$SYSDEVICE:[TCPIP$NFS]TCPIP$NFS_RUN.LOG

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

[Volker Halle]

Ronald,

I'm not a Windows expert, but don't you need a NFS Client on the Windows system to be able to acccess NFS file systems on the NFS host ?

Such a NFS client would typically use some kind of 'mount' command to map to an exported filesystem on the NFS host.

Volker.

[Daniel Fernandez Illan]

Hi Ronald
Are you using TYPELESS_DIRECTORIES when create exported service?

This is the help message to this option:

TYPELESS_DIRECTORIES, NOTYPELESS_DIRECTORIES

- TYPELESS_DIRECTORIES

Removes .dir.1 from the name of directories. A naming
conflict could arise if, for example, two files exist in
the parent directory:

DOVE.;1 (regular file)
DOVE.DIR;1 (directory file)

The name is returned as dove., rather than dove, if a file
and a conflicting directory exist.

- NOTYPELESS_DIRECTORIES (default)

Returns names as file.ext and file.dir.

If you does not use typeless_directory then your path from WINDOWS was:

tatsapp\statsapp.dir\emes.dir\

Saludos.
Daniel.

[Joseph Huber_1]

Not knowing anything about the Windows side, check on the VMS side, if there is a NFS mount request coming at all, and if so, any errors occurring:

Enable a VMS terminal as an operator terminal ($reply/enable/temp). Any message when the windows side tries to mount ?

Is something (error messages ?) written in SYS$SYSDEVICE:[TCPIP$NFS]TCPIP$*.LOG
after the server startup message ?

[IFX_1]

Hi Volker,
You are correct. I need a NFS client to access the NFS host. But, is it not a default in WINDOWS you use the MAP command?

regards,
ronald

[IFX_1]

Hi,
I am using the default, NOTYPELESS.
I actually did some simulation and even check the logs but I don't see any sign of errors. The only thing I noticed that when I connect from the WINDOWS client, it seems it cannot recognize the export folder. When doing this, I enable the reply/enable=network but messages displayed related to the connection I made.

Any help will do.

regards,
ronald

[Steven Schweda]

Can we assume that you actually have a
directory like this (with suitable ownership
and protection)?

$1$DGA1336:[statsapp.emes]


Incidentally, I see how to set the options
in an EXPORT command, but I don't see how to
_show_ those options later, so I don't know
how mine are set.

[Steven Schweda]

Hmmm. When in doubt, ask the victim.

SHOW MAP:

Pathname Logical File System

/dka0 ALP$DKA0:
[...]

SHOW EXPORT:

File System Host name

/dka0 urtx.antinode.org, [...]

On the Tru64 system:

urtx# ls -l /net/alp/dka0/anonymous/
total 402
-rwxr-xr-x 1 root daemon 41 Mar 12 2005 announce.txt
drwxr-xr-x 2 root daemon 512 Nov 28 22:14 boinc.dir
drwxr-xr-x 2 root daemon 512 Nov 28 22:14 bzip2.dir
[...]

Looks like NOTYPELESS. Note, however, that
there's no need to _specify_ ".dir" in a
path:

urtx# ls -l /net/alp/dka0/anonymous/bzip2/
total 52
-rwxr-xr-x 1 root daemon 383 Oct 5 2005 -bzip2_main_page-.html
drwxr-xr-x 2 root daemon 512 Nov 28 22:18 bzip2-1_0_3a_vms.dir
drwxr-xr-x 2 root daemon 512 Nov 28 22:18 bzip2-1_0_3b_vms.dir

Although it _does_ work to use it:

urtx# ls -l /net/alp/dka0/anonymous.dir/bzip2.dir/
total 52
-rwxr-xr-x 1 root daemon 383 Oct 5 2005 -bzip2_main_page-.html
drwxr-xr-x 2 root daemon 512 Nov 28 22:19 bzip2-1_0_3a_vms.dir
drwxr-xr-x 2 root daemon 512 Nov 28 22:19 bzip2-1_0_3b_vms.dir

I haven't tried exporting a subdirectory.

[John Travell]

There seems to be a missed point.
A windows MAP command is looking for an SMB share, not an NFS mount point.

If you want to use the windows MAP command, you should be looking at Pathworks (Advanced Server) or SAMBA.

As has been pointed out, to have the windows box use what you have setup, you need the NFS client.

JT:

[IFX_1]

Hi Steve,
Indeed, the folder $1$DGA1336:[statsapp.emes] exists. And somehow, until now, I still can not map it from WINDOWS box.

[IFX_1]

Hi John,
Do you mean that mounting the export folder from VMS to WINDOWS needs pathworks or SAMBA? Can you pls elaborate more on this?
Up to now, I still have this issue. I can not MAP the export folder from VMS to WINDOWS. Any help will do.

regards,
ronald

[Steven Schweda]

MAP on VMS TCPIP (NFS) is not the same as MAP
on Windows. If MAP on Windows involves NFS,
then there's some hope for using NFS on the
VMS system to serve the files to Windows. If
MAP on Windows involves SMB sharing (as Mr.
Travell claims), then a non-NFS solution on
the VMS side would be needed (as he
suggested).

Alternatively, an NFS client on the Windows
side could be used. (I don't use NFS on
Windows, so I can't say how to get or use
that.)

[Volker Halle]

Ronald,

you need a NFS client on the Windows system to access a NFS share on the VMS system.

If you don't beleive this, just try a simple experiment. From the VMS system do:

$ TCPTRACE ip-address-of-your-windows-client

Then try the MAP command on your Windows system and look at the Port number shown in the TCPTRACE.

$ TCPIP SHOW SERVICE NFS shows you, that NFS server will be using port 2049.

What is the port number in the TCPTRACE as the result of your Windows MAP command ?

Volker.

[John Travell]

Based on Ronald's original note, where he says he is trying to connect via Windows MAP to \\10.83.146.76\statsapp\statsapp\emes\ it is obvious to me that he is trying to use two non-compatible capabilities to talk to each other.

\\10.83.146.76\statsapp\statsapp\emes\ is a windows SMB share mapping path string. These are a result of using either the windows command 'net use \\server\share' or windows explorer 'map network drive' menu item.
To use this feature on the PC requires either Advanced Server or Samba on VMS.

OTOH, Ronald has already setup NFS on VMS, so he may prefer to use an NFS client on the PC.
I am not familiar with NFS at either end, so I could not advise what to do.

In either case, the PC will not understand VMS file versioning, so the chosen product should handle that, and the VMS disk that the shared file system is mapped to should probably be ODS5 to minimise grief when the PC tries to put files there that do not correspond to the VMS file naming conventions.

[IFX_1]

Thanks to all who replied.

I think, I need PWIP installed (pathworks) in VMS for WINDOWS client to work.

I don't have PWIP installed right now.

regards,
ronald

[IFX_1]

The problem has not been resolved yet. I am waiting for PWIP to be installed and then I can proceed my testing again.

[Volker Halle]

Ronald,

PWIP (i.e. PWIPDRIVER) is a TCPIP component, which just needs to be configured. You're probably needing Advanced Server (Pathworks) to be installed to allow SMB access to your OpenVMS system.

Volker.

[Ian Scrutton]

Consider using "Windows Services for Unix" on the Windows client if you must connect to an NFS share on the VAX.