mount a windows shared folder in osf v5.1

[Renat Yakupov]

how can i mount a windows shared folder in tru64 unix?
i tried samba, but looks like the only thing samba can provide for osf is a command line ftp-like client to get files from a windows shared folder.
i installed windows sfu on the windows box and run nfs server there, and if i know try to mount the folder as:
mount -t nfs winbox:/DATA /DATA
it gives me:
winbox:/DATA on /DATA: I/O error.
please help?
winbox box runs win2k3 and sfu 2.3,
and unixbox runs osf1 v5.1.

[Hein van den Heuvel]

I do not have any experience in this matter (as we normally go the other way!), but this would appear to be 99% a windows question. Surely if the winbox runs a reasonable NFS server, then Tru64 (or any other client) can simply use it, blissfully unaware what server it is.
Just some random questions to maybe give your ideas:

Can an other Unix box mount that windoze share?
Can your tru64 box mount an other (unix) share?
Is that share name 100% correct?
You did a mkdir on the /data locally?
You can ping that winbox nicely?
Can you ping -flood it without errors?
Can you verify that is has a reasonably speedy connection by ftp=ing a large file both ways?

fwiw,
Hein.

[Renat Yakupov]

thanx for your questions.
you are probably right about it being the winbox problem, because if i try to nfs mount from a computer with fedora core 3, it gives an error about some superblock size?
i think i have a bigger problem now... we have the share on a raid5 system, and if i try to nfs mount a share from a local hard disk, that it doesnt give me that superblock size error.
as for the other questions:
i can nfs mount shares from another linux box.
the share name is 100% correct.
i did mkdir on data remotely but as root. why does it matter if it was done remotely or locally?
both ping and ping -flood work fine.
ftp connection is alright.

i have another question though? is there mount -t smbfs thing for tru64? did i just not look hard enough and that's why came up with ftp-like samba client for osf1?

[Ivan Ferreira]

For nfs:

Use:

To find out if the services are running:
rpcinfo -p server_ip

To find out the list of exported directories
showmount -e server_ip

Verify the protocol used, tcp or udp.

And for SAMBA, is a very portable application and can be installed on Tru64 Unix.

[Jon Ward_3]

SFU v2.3 is rather old, a number of patches were released for improved UNIX compatibility. You should probably look at upgrading SFU to the latest:

http://www.microsoft.com/windowsserversystem/sfu/default.mspx

As for mount -t smbfs, to my knowledge that is a Linux only feature. It required kernel level support.

[Renat Yakupov]

here is the list of servrices that winbox is running:
program vers proto port
100000 2 udp 111 portmapper
100000 2 tcp 111 portmapper
351455 1 tcp 632
351455 1 udp 633
351455 2 tcp 634
351455 2 udp 635
100004 2 udp 716 ypserv
100009 1 udp 717 yppasswdd
100004 2 tcp 718 ypserv
1073741824 1 udp 719
100005 1 udp 1048 mountd
100005 2 udp 1048 mountd
100005 3 udp 1048 mountd
100005 1 tcp 1048 mountd
100005 2 tcp 1048 mountd
100005 3 tcp 1048 mountd
100021 1 udp 1077 nlockmgr
100021 2 udp 1077 nlockmgr
100021 3 udp 1077 nlockmgr
100021 4 udp 1077 nlockmgr
100021 1 tcp 1077 nlockmgr
100021 2 tcp 1077 nlockmgr
100021 3 tcp 1077 nlockmgr
100021 4 tcp 1077 nlockmgr
100024 1 udp 1059 status
100024 1 tcp 1059 status
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
and this is the list of mounts:
/temp Everyone
/SCANNER_DATA Everyone
if i mount /SCANNER_DATA, it wont even do it and give me "I/O error",
if i mount /temp, it wont complain and mount it, but when i try to access it, it would say:
NFS3 RFS3_ACCESS failed for server winbox : RPC: Authentication error
: I/O error
now the difference between the two directories is that /temp is on a local hard disk on winbox, while /SCANNER_DATA is on a locally attached RAID5 system.
any idea about this NFS3 RFS3_ACCESS error?

[Ivan Ferreira]

It seems that an NTFS/NFS sharing ACL is preventing the access to the exported directory, or you need a user name mapping.

See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;324089

http://support.microsoft.com/default.aspx?scid=kb;en-us;262965

You should enable anonymous access to the folder.

[Renat Yakupov]

i think it was both...
i added everyone in /temp dir permissions and enabled anonymous login, now it just says permission denied rather than NFS3 RFC3 failure or something...
i am confused about that name mapping though :(
it asks for unix domain name. we have only one unix computer that will be accessing the shared files. what should i enter there in this case?

[Ralf Puchner]

If you mount from Tru64 to Windows it depend on the Serverimplementation, so on Windows side.

Have a closer look to the manual of the windows implementation. But you must grant access to the unix user so mapping the incoming user-id to a lokal windows id. Some implementations allow "non-root" mounts or map all incoming users to "anonymous" (guest in windows).