I am having some issues with performance on a share I'm mounting through Client for NFS. The initial mapping works fine (although I have to re-connect it manually at startup, because Windows tries to re-map the drive before it starts client for NFS). When I connect, I see the first list of folders with no trouble. However, as soon as I click on a folder to open it up, Windows Explorer sits and goes 'Not Responding' for 1-2 minutes. Performance is the fine for the most part, but intermittently it will again take 30-60 seconds to open a folder.
Searching around on the internet, I found the suggestion to use the casesensitive=yes option on the command-line mount call. When I do this, mount tells me 'the command completed successfully,' and I can navigate to the mounted drive on the command prompt, but the drive does not become visible in Windows Explorer. Is there a second step I need to do to make the mount available to the GUI?
This seems to be an issue with 'mount' and not the specific options; casesensitive=no gives the same behavior.
Thank you very much in advance!
Thanks for the post!
The speed of accessing NFS could be effected by many reasons.
Please refer to this: Causes of slow access times for NFS.
Troubleshooting the possible causes mentioned in this doc.
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Thank you for the answer. Unfortunately, this document does not help me: it does not refer to utilities on the windows client for NFS, nor does it address the issue I am facing.
There are two main problems that need to be addressed:
1) Windows Explorer is very slow at accessing the NFS share, while other programs are very fast (e.g. if I browse through with FileZilla)
2) The NFS share does not properly reconnect at startup. Windows attempts to reconnect the share before the Client for NFS service is started.
I bought Windows Ultimate with the understanding that NFS was supported. Why haven't these issues been resolved?
... It seems that the browsing directories or read/writes is affected by any sort of download (as little as 200KB/s).
My computer and the NAS (using NFS) are separated by a netgear gigabit switch, and I think it fairly unlikely that the switch is dropping packets.
Could anyone else confirm this behavior? Is it possible that data inbound on differing ports is somehow confusing the NFS client?
NOTE: other connection & speed related workarounds I've discovered @ NFS Mounts don't properly reconnect
I can confirm that NFS speeds are around 200 KB/s... if you are lucky.What I can see from my tests is 180 KB/s max so its something going on with nfs and windows. I tested speeds both from command line and in the explorer ( as normal user and admin) and both are bad and can be used on production machines.
Not sure how to go about and troubleshoot this further, if anyone did some testing on firewall side or ports please advise.
Make the nfs client use TCP/IP.
Control Panel/System/Administrative Tools/Services for Network File System(NFS)
Right click on client for nfs
Network Protocol = TCP, not UDP+TCP
Disconnect your nfs mount and reconnect.
- Edited by Jack_Foobar Sunday, March 11, 2012 5:54 AM