I’m moving our file server from Netware to Windows Server 2012. I’ve setup a test share. While Netware never gave us any delays in accessing the drive, our test group immediately started complaining that our network drives “would not come up right
away”.
We’re hosting the share on a Server 2012 box and I used both Windows 7 (as that’s the standard in our office) and 8.1 to test the issue. I noticed that the problem shows itself if a user hasn’t accessed the drive for more than an hour. The effects are also exaggerated on Windows 7: if a user hasn’t used the drive, it takes on average 25 seconds to open the drive. This is lessened somewhat with Windows 8, which either doesn’t have the problem or has a delay of 5 seconds to open the drive. This is an improvement, but it’s still not acceptable considering we had *no* delays with Netware.
The first thing I surmised was a problem with the network drivers on my test machines, so I updated them. It didn’t affect the issue at all.
So then I assumed the problem was coming from some sort of reconnection issue from the end machine to the server, so I attempted to follow the fixes located at http://support.microsoft.com/kb/297684 in order to keep the connection alive indefinitely. This had no effect. The delays were just as long as they had been prior to making any changes.
I’m beginning to run out of ideas as to why our test network drive has these delays. Thanks in advance for any insight you all might have.
edit: Upon further testing, I have the following information:
- HD spindown times on the server are set to 0 mins, so there is no spin-down occuring.
- I haven't been able to find any useful information in the server's event logs.
- There is no third-party software installed on the server.
- There are no extra services running on this server. Just the file share.
- My network provider setup is as follows: NetWare Services >> Microsoft Remote Desktop Session Host Server >> Microsoft Windows Network >> Web Client Network
We’re hosting the share on a Server 2012 box and I used both Windows 7 (as that’s the standard in our office) and 8.1 to test the issue. I noticed that the problem shows itself if a user hasn’t accessed the drive for more than an hour. The effects are also exaggerated on Windows 7: if a user hasn’t used the drive, it takes on average 25 seconds to open the drive. This is lessened somewhat with Windows 8, which either doesn’t have the problem or has a delay of 5 seconds to open the drive. This is an improvement, but it’s still not acceptable considering we had *no* delays with Netware.
The first thing I surmised was a problem with the network drivers on my test machines, so I updated them. It didn’t affect the issue at all.
So then I assumed the problem was coming from some sort of reconnection issue from the end machine to the server, so I attempted to follow the fixes located at http://support.microsoft.com/kb/297684 in order to keep the connection alive indefinitely. This had no effect. The delays were just as long as they had been prior to making any changes.
I’m beginning to run out of ideas as to why our test network drive has these delays. Thanks in advance for any insight you all might have.
edit: Upon further testing, I have the following information:
- HD spindown times on the server are set to 0 mins, so there is no spin-down occuring.
- I haven't been able to find any useful information in the server's event logs.
- There is no third-party software installed on the server.
- There are no extra services running on this server. Just the file share.
- My network provider setup is as follows: NetWare Services >> Microsoft Remote Desktop Session Host Server >> Microsoft Windows Network >> Web Client Network