Windows 2003 R2 NFS Client

[Sunner]

I'm trying to use the built in NFS client to mount a share residing on an OpenBSD box.
The BSD box has one share that it exports to two clients, another OpenBSD 4.5 box and said 2K3 server. The other BSD box can use the share just fine, and there's nothing peculiar about the setup, no firewalls in between the boxes, etc.
The Windows box however seems to be...somewhat confused.
I've setup a user mapping for the user that owns the files on the BSD box, he has a matching user on the Windows box, and the User Name Mapping service picked it up just fine from the passwd/group files(I copied just the relevant lines over to the Windows box).

If I use the "Map Netowkr Drive" UI to try to mount the share, I can browse my way to the server, and I see the share.
Regardless of whether I choose to mount "straight away" or if I try to mount as the above mentioned user, I get the message "The drive could not be mapped because no network was found.".

Using the command line mount, I can get some more variation in my results.
If I simply try "mount bsdbox:/home/jdoe Z:" I get network error 53, "The network path was not found.". Trying this with some various options, or using the regular Windows path style(ie \\bsdbox\home\jdoe) gives me the same result.
Using the -u switch to specify the user I setup will give me error 1326, "Logon failure: unknown user name or bad password.".

And, as an extra added bonus I managed to get an entirely new error while typing this post, I was just doing as mentioned above to get my error messages right, and I somehow managed to get an error 21, "The device is not ready.".
I honestly have no idea how I managed that, I simply used the mount command with the -u switch, and just once it gave me that, I can't seem to reproduce it now...

Anyways, any tips?

Edit: oh and yeah, using the IP instead of the hostname doesn't change what errors I get, browsing using the map network drive UI will show the machine using it's IP, but I've added it to the hosts file as well, so as far as I can tell, IP or hostname makes no difference.
More edit: obviously meant to say R2 in the topic.

 

[bstxx]

Im dealing with setting up NFS-Server and NFS-Client on Server 2003 R2 (SP2). The Server works adequate and UNIX-Clients (AIX) can connect right. But with the NFS-Client I've the same problems as described (here to connect to the AIX-Hosts) and it's impossible too to make connection from R2 NFS-Client to his own NFS-Server (on the same machine..) ! Did You find a solution for the "Error 53" ? In the web I found to set "UseReservedPorts" in the registry for the Client, but it didn't help..

Thanks very much in advance !

 

[Sunner]

Ok, this is old now, but just in case you do read it, yes I did find the problem, and the solution pissed me off.
The solution to my problem was indeed the UseReservedPorts reg hack, however there was one ever so slight problem. Using the normal service controls(services.msc for example) to restart the NFS Client service won't work.
It looks like it works, it says it restarted, etc, but in reality it does jack shit from what I can tell.
You have to use the nfsadmin command, "nfsadmin client stop" and "nfsadmin client start" to actually have the registry change take effect.

As far as I remember, that was the only thing I needed to make this work.