In December I built a new computer for testing the 32-bit version of Vista RC1. The motherboard was the Intel DG965WH (w/ onboard Gigabit LAN). Vista would install fine, but when I used IE7 to browse the internet it would only pull up the default home page of msn.com. Clicking on any linkson msn.com, or attempting to go to other sites like cnn.com, slashdot.org, etc. would result in the web browser stalling out. In similar fashion, attempting to do updates within Vista or the Online help failed. When watching the graph of network traffic it would show an initial spike when I submitted a request, but it would immediately drop to nothing. On one occasion I was able to get to mozilla.org and download Firefox, but after installing it I ran into the exact same problems. After several days of failed troubleshooting I installed XP Pro and have been using the computer just fine ever since. Today (knowing that on January 30th I will have to be able to answer people's questions about Vista since I work as the manager for an electronics retailer) I decided to attempt to install Vista RC1on anolder computerbased on a Intel D865GBF motherboard (w/ 10/100 LAN). Again, it installed just fine but I have experienced the exact same problems when attempting to access the internet (and again, strangely the default msn.com pulls up just fine). The closest thread that I have found with these types of issues relates to a Marvell line of Gigabit adapters on the 64-bit version of the OS. I have a standard home network with cable modem running to Linsksys wired router and Netgear gigabit switch. I checked ipconfig and the router is succesfully assigning an IP address to the computer. If anybody has any suggestions I would highly appreciate it. Thanks! --Brad W.River Falls, WI

I found this response to one of the other questions and 'lo and behold' it worked! Open up the command prompt as administrator. You can quickly do this by typing command in the Instant Search and hitting return. It will add Command Prompt to the Start menu. Right-click on this and "Run as Administrator". In the command prompt type netsh int tcp set global autotuninglevel=disabled This fixed the problem and there was much rejoicing.