Hi All-

Here's the sit'n:

Box #1 is a WinNT Server on Network A.

Box #2 is a Linux box and is serving as a router (IP Gateway) between Network A and Network B.

Box #3 is a Linux box on Network B.

==

I have an SMB share available on box #1.

I have successfully mounted that share on box #2 using smbmount.

Now I would like to use box #2 to export that SMB share using NFS and make it available to other machines (like box #3) on Network B.

I have already successfully exported a local ext2fs from box #2 to Network B, so I think I understand NFS well enough to do that.

However, when I try the same drill (same as what worked for the local ext2fs from box #2) with the smbmount'ed share from box #1, I get the following message:

mount: box2:/mnt/sambashare failed, reason given by server: Permission denied

When I check the system log on box 2, I see the following:

Date1 Time1 box2 rpc.mountd: authenticated mount request from box3 for /mnt/sambashare (/mnt/sambashare)
Date1 Time1 box2 rpc.mountd: getfh failed: Operation not permitted

My /etc/fstab on box3 looks like this:
=============
box2:/opt/public /mnt/ext2fs nfs exec,dev,suid,rw 1 1
box2:/mnt/sambashare /mnt/sambashare nfs exec,dev,suid,rw 1 1
=============

And my /etc/exports on box2 looks like this:

=============
/opt/public *.networkb.com(rw)
/mnt/sambashare *.networkb.com(rw)
=============

Box2 exports /opt/public with no problems to Network B. However, no joy with /mnt/sambashare

Any thoughts? I've read manpages, TCP/IP 2nd revision (by Craig Hunt), Linux NAG, etc. and can't seem to find anything addressing this situation.

Thanks very much for any help.


Joe

i'm not really sure about your actual problems, BUT i doubt it will acutally work. NFS will not export FAT32 partition, for very good reasons, and i wouldn't be in the slightest bit suprised if the same goes for NTFS, assuming it is NTFS you want to share.

Linux has a lot of things like this, which can seem annoying, but to be honest, what you're trying to do is one hell of a cludge, and cludges generally involve sticking two fingers up to security, and shouldn't ever be used in a proper environment.

Generally as far as samba is concerned, it always seems like a best attempt at deal with a fundamentally nasty cludge, and does a pretty good job at it, as it can never be perfect.

I'd guess that your best bet would be to make your samba gateway act as a WINS server, to take the share properly across the network, not using NFS, which is only intended for use with unix-like filesystems