Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

My problem is simple: network discovery is way too slow when using Windows Server 2008 R2 or Windows 7. I have hunted around the Internet only to find guesses as to the real problem, with no definitive solution. So I thougth I'd post the question here.

I run a Windows Workgroup with 3 computers: Win 7, Server 2008 R2 and an XP box. When I use Explorer to browse network shares on the XP box, it shows other network items instantly as normal. But from the server or Win 7 machines, it takes a good 1-2 minutes to begin showing anything else on the network. This is with only 3 machines connected to a known-good router.

The rules of logic indicate that it's a configuration problem or a bug in the Windows 7/Server kernel. So, how do I fix it?


share|improve this question
I will assume that you have applied all Windows updates, since there were issues that were previously fixed. Please confirm the testing results between the Win7 and Win 2008 R2 only. Do you have a home group configured? Do you still experience slowness by typing in the path to a share directly into the Run command? –  Bernie White Oct 22 '12 at 3:45
Yes all windows updates are current. Typing a path directly into explorer (I don't use the search box) does work but it is still sluggish compared to XP. And besides, I don't want to have to do that, which is the reason I browse the network rather than typing in a path. –  Stephen Falken Oct 22 '12 at 14:08
Suggest building a new XP box to test if it's the same as the current XP behaviour. Also ask the computer "would you like to play a game? How about a nice game of chess?" ;-D –  Lizz Jan 5 '13 at 6:45

1 Answer 1

Apparently these are due to changes made in Vista which have been inherited by later versions of Windows.

In an elevated cmd prompt:

netsh interface tcp set global autotuning=disabled
netsh interface tcp set global rss=disabled

I would recommend rebooting after running these. It made a pretty drastic improvement for my workgroup.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.