How do I mount a UNIX NFS file on my Windows 2003 system?

You need NFS from the Windows Services for UNIX, download: here, description on how to install the NFS client is here (I cannot test this for you btw).

According to the Windows administrators, the requisite software is already there. They just don't know how to set up the server as a client so that it can access the directory on the UNIX server. For example, on a UNIX client we simply enter mount node:/directory. The node reference denotes the UNIX server from which the file is being "shared." I don't know what the Windows equivalent is.

Yes. I too am a Samba fan, but this is a production system and I'd have a hard time selling a solution to my management that IBM doesn't support.

The Windows administrator told me that he'll need to reinstall the services which might require a reboot. I know nothing about the Windows side so I'm at his mercy. That's why I'm relying on you guys.

I did show them the mount command suggested by gerwinjansen. As a UNIX administrator, I'm quite familiar with that command. I'm still waiting for a response from our Windows guy. Stay tuned!

Please tell me what the effect of the following would be...

mount newt:/env01/lsf9dev/law/systest/work/ARRIVAL *

I don't know why the administrator chose to use an asterisk instead of a drive letter. The system responded with a message similar to the following:

Y: successfully connected to newt:/env01/lsf9dev/law/systest/work/ARRIVAL

However, when we went looking for drive Y, we couldn't find it. When we tried entering "Y:" at the DOS prompt, we got an error stating that something was too small, etc. I'm sorry I don't have the exact message.

Hi, the start (in Windows) means to map just an available drive letter, apparantly the unix mount command does the same. It would help if you could get the error message otherwise we don't know what is going on or what needs to be changed. Can you post the error message?

Was this perhaps the error:

http://blogs.msdn.com/b/sfu/archive/2007/06/05/network-error-53-the-data-area-passed-to-a-system-call-is-too-small-or-unknown-error.aspx

Yes, I believe that was the error. Based on the information I found on that site, I have made some modifications to the NFS configuration on the UNIX server. I'm waiting for the Windows administrator to try mounting the directory again.

I just wanted to let the experts know that I haven't abandoned this question. I'm still waiting for feedback from our Windows administrator.

No problem, we're patient :-)

I don't think the directorty is being mounted correctly. In the UNIX world, if I mount newt:/env01/lsf9dev/law/systest/work/ARRIVAL as a partition I can access as /mnt (equivalent to a drive letter in Windows), all I can see are the contents of ARRIVAL. I cannot traverse ARRIVAL's path. In fact, /mnt behaves like the root directory - it has no parent. That's how I was hoping the Windows client would behave. From the client's perspective, nothing should exist above the ARRIVAL directory. Part of the problem might be that they're treating it like a folder. They should be treating it like a partition. From the server's perspective it's a folder. From the client's perspective, it's a partition.

Eventually we discovered that the security settings on the (Windows) client were too restrictive. Additionally, they reconfigured the client to use UPD instead of TCP.