NFS Mounts on Windows using Services for Unix

[Adam Smith]

Hey,

I'm trying to mount an NFS share on Windows. I've installed Services for
Unix on this Windows machine and am able to successfully mount a share
anonymously, however whenever I specify a different username to use,
Windows doesn't like it.

The username used on this Windows machine is different to the one on the
FreeBSD 5.2 machine.

Eg:

C:\Documents and Settings\bugman>mount host.server.com:/data Q:
Q: is now successfully connected to host.server.com:/data

The command completed successfully.


This is virtually useless now, as I can not create or delete any files from
this mount point, as I do not technically own them. I can create a
subdirectory with writeable permissions, but then any files created in it I
can not delete because they have the wrong UID.

Obviously to get around it, I would specify the -u:username option using
SFU's mount program:

C:\Documents and Settings\bugman>net use /delete Q:
Q: was deleted successfully.


C:\Documents and Settings\bugman>mount -u:adam host.server.com:/data Q:
Password:
Network Error - 1326

Type 'NET HELPMSG 1326' for more information.

C:\Documents and Settings\bugman>net helpmsg 1326

Logon failure: unknown user name or bad password.


Well, it's not a bad username or password. I tried looking at that
"Username Mapping" program however it seems to want to talk to an NIS
server. I'm not sure I can (or want to) do anything about that.

The workaround for now is to create a "working" directory in the mount in
which I can write files, and set the permissions to 770. At least that way
my group membership allows me to read and delete these files from my own
machine.

As to why the password error is coming up at all, I know that when you
mount an NFS share the UID and GID of your account is matched up against
the server, so when using NFS it is prudent to keep your UID/GID's the
same. In the case of Windows connecting to NFS, I would assume the -u:
flag or the username mapping system would do this for me. I'm not sure
which one is supposed to do what.

Any suggestions would be great, otherwise I'll just continue writing to the
one directory on this mount :)


Happy Valentines Day,

[Adam Smith]

I fixed the following by adding a -mapall=adam to the end, which is mapping
all client uid's back to my own.

Post by Adam Smith
Hey,
I'm trying to mount an NFS share on Windows. I've installed Services for
Unix on this Windows machine and am able to successfully mount a share
anonymously, however whenever I specify a different username to use,
Windows doesn't like it.
The username used on this Windows machine is different to the one on the
FreeBSD 5.2 machine.
Q: is now successfully connected to host.server.com:/data
The command completed successfully.
This is virtually useless now, as I can not create or delete any files from
this mount point, as I do not technically own them. I can create a
subdirectory with writeable permissions, but then any files created in it I
can not delete because they have the wrong UID.
Obviously to get around it, I would specify the -u:username option using
Q: was deleted successfully.
Network Error - 1326
Type 'NET HELPMSG 1326' for more information.
C:\Documents and Settings\bugman>net helpmsg 1326
Logon failure: unknown user name or bad password.
Well, it's not a bad username or password. I tried looking at that
"Username Mapping" program however it seems to want to talk to an NIS
server. I'm not sure I can (or want to) do anything about that.
The workaround for now is to create a "working" directory in the mount in
which I can write files, and set the permissions to 770. At least that way
my group membership allows me to read and delete these files from my own
machine.
As to why the password error is coming up at all, I know that when you
mount an NFS share the UID and GID of your account is matched up against
the server, so when using NFS it is prudent to keep your UID/GID's the
flag or the username mapping system would do this for me. I'm not sure
which one is supposed to do what.
Any suggestions would be great, otherwise I'll just continue writing to the
one directory on this mount :)
Happy Valentines Day,
--
Internode : http://www.internode.on.net
Phone : [phone]
--
LinuxSA WWW: http://www.linuxsa.org.au/ IRC: #linuxsa on irc.freenode.net

[Adam Smith]

Post by Adam Smith
I fixed the following by adding a -mapall=adam to the end, which is mapping
all client uid's back to my own.

No, I didn't.

I have had to set SFU to set file/directory modes to 777 otherwise I can
create new files but not write to them again. It's really annoying. It
seems to be relying on the "everyone" permissions as well as my own.

Does anyone know how to set this up "properly"?

Maybe I should just install samba...



Adam

Post by Adam Smith

Post by Adam Smith
Hey,
I'm trying to mount an NFS share on Windows. I've installed Services for
Unix on this Windows machine and am able to successfully mount a share
anonymously, however whenever I specify a different username to use,
Windows doesn't like it.
The username used on this Windows machine is different to the one on the
FreeBSD 5.2 machine.
Q: is now successfully connected to host.server.com:/data
The command completed successfully.
This is virtually useless now, as I can not create or delete any files from
this mount point, as I do not technically own them. I can create a
subdirectory with writeable permissions, but then any files created in it I
can not delete because they have the wrong UID.
Obviously to get around it, I would specify the -u:username option using
Q: was deleted successfully.
Network Error - 1326
Type 'NET HELPMSG 1326' for more information.
C:\Documents and Settings\bugman>net helpmsg 1326
Logon failure: unknown user name or bad password.
Well, it's not a bad username or password. I tried looking at that
"Username Mapping" program however it seems to want to talk to an NIS
server. I'm not sure I can (or want to) do anything about that.
The workaround for now is to create a "working" directory in the mount in
which I can write files, and set the permissions to 770. At least that way
my group membership allows me to read and delete these files from my own
machine.
As to why the password error is coming up at all, I know that when you
mount an NFS share the UID and GID of your account is matched up against
the server, so when using NFS it is prudent to keep your UID/GID's the
flag or the username mapping system would do this for me. I'm not sure
which one is supposed to do what.
Any suggestions would be great, otherwise I'll just continue writing to the
one directory on this mount :)
Happy Valentines Day,
--
Internode : http://www.internode.on.net
Phone : [phone]
--
LinuxSA WWW: http://www.linuxsa.org.au/ IRC: #linuxsa on irc.freenode.net

--
LinuxSA WWW: http://www.linuxsa.org.au/ IRC: #linuxsa on irc.freenode.net