Install Nfs Client Windows 2003

24.07.2019
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 bsdboxhomejdoe) 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.
  1. Nfs Client Windows 2003
  2. Nfs Client Windows 2003 R2
Nfs

Nfs Client Windows 2003

Install Nfs Client Windows 2003

Nfs Client Windows 2003 R2

Install Nfs Client Windows 2003

Installation Instructions and Configuration Guide for ProNFS v2.1 Client using SSH on Windows XP www.Labtam-inc.com help@Labtam-inc.com Labtam Inc. To install Services for NFS components. Click Start, point to Administrative Tools, and then click Server Manager. In the left pane, click Manage Roles. Click Add Roles. Select the File Services check box, and then click Next. The File Services screen appears. Implement Active Directory lookup functionality (available in Windows 2003 Server R2 implementation of Services for Unix but not in the downloadable version), which requires configuring a Windows 2003 Server R2 based Active Directory domain controller as part of NIS infrastructure in the master role, since a Windows system cannot operate as a subordinate to a Unix-based master.

Comments are closed.