Slow access speed on Shared Drive
Hi,
I've just setup a new Windows 2008 file server and users are experiencing extremely slow speeds when first accessing their drives on this server. ie. when users click their Home Directories which reside on this server you get an hour glass for about 20 seconds before any files appear. Once they appear speeds are good. If the Home Directory is unused for a length of time (seems to be 20-30minutes) then when it's accessed you experience the slow speeds again.
Network Drives are mapped at login through Active Directory.
I've done some searching on EE and other sites but nothing i've come across has fixed the issue. I've turned off Indexing on the volume, disabled IPv6, disabled the Windows firewall, added the server to dns manually. Removed the registry key from in Namespace etc.
Still no changes, any ideas of things i can check or try?
Server is virtual running in same subnet as the computers having the issue. Seem's like it's running a search to see what files are in the folder, once it's done this speed is just as quick as if it was a local drive.
I've just setup a new Windows 2008 file server and users are experiencing extremely slow speeds when first accessing their drives on this server. ie. when users click their Home Directories which reside on this server you get an hour glass for about 20 seconds before any files appear. Once they appear speeds are good. If the Home Directory is unused for a length of time (seems to be 20-30minutes) then when it's accessed you experience the slow speeds again.
Network Drives are mapped at login through Active Directory.
I've done some searching on EE and other sites but nothing i've come across has fixed the issue. I've turned off Indexing on the volume, disabled IPv6, disabled the Windows firewall, added the server to dns manually. Removed the registry key from in Namespace etc.
Still no changes, any ideas of things i can check or try?
Server is virtual running in same subnet as the computers having the issue. Seem's like it's running a search to see what files are in the folder, once it's done this speed is just as quick as if it was a local drive.
I suggest that you check the speed and duplex settings at both the Server and Switch end.
If its set to Auto Negotiate, disable Auto Negotiate and then set the speed manually to Fast Ethernet (100) or Gigabit Ethernet (1000) and duplex to half duplex or full duplex as per your Network Configuration.
Is the Server a Physical Machine or a Virtual Machine ?
If its set to Auto Negotiate, disable Auto Negotiate and then set the speed manually to Fast Ethernet (100) or Gigabit Ethernet (1000) and duplex to half duplex or full duplex as per your Network Configuration.
Is the Server a Physical Machine or a Virtual Machine ?
ASKER
It's a virtual server and changing speed & duplex settings didn't fix it.
this might sound noobish but could it be that the hard drive is turning itself off after 20minutes in power settings?
ASKER
No the HDD's are set to never turn off, I'm thinking it's more an authentication issue somewhere.
ie. I can access my M: Drive once and it takes 30 seconds then another user can access theirs and it will take them 30 seconds aswell.
ie. I can access my M: Drive once and it takes 30 seconds then another user can access theirs and it will take them 30 seconds aswell.
ASKER
The problem only occurs on clients using Windows XP i just ran up a Vista test machine and the connection was instant.
i found someone who has the exact problem as you with some possible fixed posted? have you seen this
http://www.tek-tips.com/viewthread.cfm?qid=1263393
http://www.tek-tips.com/viewthread.cfm?qid=1263393
ASKER
Thanks for the ideas but unfortunately no none of those solutions fixed it.
I also tried changed SMB2 to SMB1 on the server but this didn't fix it. Getting really stumped now...
I also tried changed SMB2 to SMB1 on the server but this didn't fix it. Getting really stumped now...
ASKER
The following seems to have resolved the issue for me.
http://www.eggheadcafe.com/conversation.aspx?messageid=34014349&threadid=33937859
Basically have to uninstall Client for Microsoft Networks then reboot.
I then can't login as a domain user and have to login as a local user, reinstall Client for Microsoft Networks then reboot.
Problem solved.... (I think) will need to test this on afew more machines to confirm but seems rather retarded to have to do... No way i could do this accross our 600 users company manually.
Does anyone know how i could do something similar via Group Policy or login scripts? Basically just reinstalling Client for Microsoft Networks from the NIC on each machine...
http://www.eggheadcafe.com/conversation.aspx?messageid=34014349&threadid=33937859
Basically have to uninstall Client for Microsoft Networks then reboot.
I then can't login as a domain user and have to login as a local user, reinstall Client for Microsoft Networks then reboot.
Problem solved.... (I think) will need to test this on afew more machines to confirm but seems rather retarded to have to do... No way i could do this accross our 600 users company manually.
Does anyone know how i could do something similar via Group Policy or login scripts? Basically just reinstalling Client for Microsoft Networks from the NIC on each machine...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER