Post some details about your router, network card, etc. and the text
output of ipconfig /all from an elevated cmd prompt. Maybe there is
a firmware update available for your router if
http://support.microsoft.com/default.aspx/kb/932134 is your issue.
Or you may need a new driver for your network card.
I love the use of the word "outdated" in the title of that KB entry.
That explicitly translates into that the problem is with your router
not the new TCP/IP stack. How can products based on open standards
suddenly become out of date? It's not like TCP/IP communication is a
new thing.
I ran the Internet Connectivity Evaluation tool and it told me that
everything but uPnP worked. I was overwhelmed with joy and thought to
myself, "surely, this means that I should have no problem connecting
to the internet". Alas, I was fooled. Downloads lag. Web pages take
forever to load, if at all. And on and on the problems go. I updated
the driver. I changed the netsh interface tcp global settings. Static
IP. Dynamic IP. Direct connect to cable modem. Direct connect to
router. I have a few more things to try, but I'm running out of ideas
and patience.
The 'outdated' TCP/IP stack in XP SP2 has no problems connecting with
the router that passed with flying color. Surfing on my four-year old
laptop over a 11mpbs wireless connection is fast and a pleasure. The
shiny new TCP/IP stack in Vista on the other hand can't make up it's
mind leading to surfing that is not as fast and sporadic at best. MS
should have included some form of backward-compatibility in the new
TCP/IP stack - some sort of "Work like XP" option.
The most amusing thing is when I ask Vista to repair my network
connection. After performing its review, one of the options is to turn
off a setting that is not compatible with my router. The setting is
autotuning. But the Internet Connectivity Evaluation tool told me
everything is hunky dory. Which one do I believe?
without details, we can only guess.
Much like MS did with the new TCP/IP stack.
