| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
Making NFS mounts available
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 Making NFS mounts available - Jul. 7, '06, 10:58:05 AM
|
|
|
edrosen
Posts: 7
Joined: Mar. 30, '06,
Status: offline
|
I've got 2003R2 w/SP2 - NFS client installed, user names mapped - exported NFS filesystem from remote machine mounted onto Windows drive. If I open a ksh window on my Win2003 box, I can find the NFS filesystem under /dev/fs/<driveletter>
If I telnet to the Win2003 box (using Interix telnet server), I don't see the NFS filesystem. The "net use" command shows the filesystem as "unavailable".
If I type a "net use .........." or a "mount......." command from my telnet session, then the filesystem becomes available.
Am I doing something wrong here, or is this the "way it works"? Is it possible for one's home directory to reside in a filesystem that is NFS mounted onto a windows box?
|
|
|
|
|
RE: Making NFS mounts available - Jul. 7, '06, 4:24:22 PM
|
|
|
edrosen
Posts: 7
Joined: Mar. 30, '06,
Status: offline
|
I added a mount command to the profile.loc, which has gotten me closer to where I would like to be with this - yet -
from the Interix telnet session, all files in NFS tree appear as owned by nouser nobody. If I look at a file created in the NFS tree from the Win box, on the NFS server itself, the ownership is ok - as if the name mapping only displays on a UNIX system
- is this expected?
|
|
|
|
|
RE: Making NFS mounts available - Jul. 9, '06, 12:45:02 AM
|
|
|
Rodney
Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Back with Windows 2000, Microsoft changed how remote filesystems behave when
mounted as a drive letter (i.e. "X:") for security. The traditional behavior
prior to this was a big security hole. So it was changed to seal the gap.
It doesn't matter if you are the same user or not, a mounted remote disk as
a drive letter is associate with the specific Window Station that the mount
happened from. The telnet session is in a different Window Station.
The security hole getting plugged is who's security credentials were being used
to respresent access (read or write). However, if you access by UNC (in Win32)
or by "/net" (in Interix) then the specific user credentials are always used.
It is recommended that you make the access through /net with Interix. The
pathname will be formed as "/net/MACHINE/share/...". If you have Username
Mapping (UNM) active then owner/group should appear correct (provide there
is a mapping for the uid & gid).
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
