- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: NFS - can not connect to export folder
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2006 09:20 PM
тАО11-27-2006 09:20 PM
NFS - can not connect to export folder
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2006 09:45 PM
тАО11-27-2006 09:45 PM
Re: NFS - can not connect to export folder
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2006 09:52 PM
тАО11-27-2006 09:52 PM
Re: NFS - can not connect to export folder
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2006 12:21 AM
тАО11-28-2006 12:21 AM
Re: NFS - can not connect to export folder
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 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2006 11:55 AM
тАО11-28-2006 11:55 AM
Re: NFS - can not connect to export folder
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2006 12:10 PM
тАО11-28-2006 12:10 PM
Re: NFS - can not connect to export folder
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2006 03:13 PM
тАО11-28-2006 03:13 PM
Re: NFS - can not connect to export folder
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2006 03:24 PM
тАО11-28-2006 03:24 PM
Re: NFS - can not connect to export folder
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2006 04:51 AM
тАО11-30-2006 04:51 AM
Re: NFS - can not connect to export folder
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:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2006 01:26 PM
тАО12-04-2006 01:26 PM
Re: NFS - can not connect to export folder
Indeed, the folder $1$DGA1336:[statsapp.emes] exists. And somehow, until now, I still can not map it from WINDOWS box.