I had the same problem, and the solution described in post #2 worked perfectly. The culprit was the netbios driver. I did, however, not change the tcp/ip sync limit, therefore I think it probably doesn't matter. I also noticed something I don't find perfectly logical: using the same settings for removing drivers and services, but changing the service startup states, sometimes the netbios driver startup would be set to system, sometimes to disabled. When I left the startup state for services all on default, the netbios driver would be configured to startup automatically, when, however, I changed several services (dhcp disabled, etc), the netbios driver would be disabled by default. I couldn't pinpoint the settings for exactly which services had an effect on the driver startup state, I stopped searching for it when I found out how to solve the issue.