Vista Networking Problems

[Guest]

Either Vista (Beta 2 and now build 5536 -- I just joined Technet and
downloaded it) has a serious problem with it's networking code, or a lot of
the internet just happens to randomly have problems when I'm using Vista.

For example, today I went to Adobe.com (because I noticed Vista 5536
includes a link to "Windows Live Mail Desktop Beta" on the startup screen --
however it does not include the required flashplayer, making it impossible
to view/download the Windows Live Mail Desktop) and adobe.com was down
(according to vista). I checked for networking problems, and none were
found. Later I went to msn.com (one of my homepage tabs) and -- well, that
was down (but live.com was up). Then, well, this one appears to be "real"
(no pun intended) -- real player had trouble signing in -- but when I went
to check forgotten password (because it couldn't sign me in) the screen said
the server is down for "scheduled maintenance".

Ok, so 2 out of three this session I think I can blame on Vista, because
multiple reloads eventually loaded the page. Out of frustration, I tried
(1) Turning off Windows Firewall, and (2) Turning off the phishing filter.
This didn't help the situation.

-Rob

 

[Tom Ziegmann]

Hello,

Please try the following command from a command prompt and see if IE works.

netsh int tcp set global autotuningleve;=disabled

Tom Ziegmann
Microsoft Certified Professional
Windows Vista / Server Longhorn Technical Beta Tester
Windows Server 2003 Service Pack 2 Technical Beta Tester

 

[Tim Payne]

Are you behind a home router? Using a Marvell ethernet controller? Tom
Ziegmann has posted a command line fix plus a Marvel driver setting that
address issues such as you describe. Search for his posts...Tim.

 

[Guest]

Tom,
I think you have a typo in your command. I believe it's suppose to be netsh
int tcp set global autotuninglevel=disabled

However, when I entered this I got the following message.

Set global command failed on IPv4. The requested operation requires elevation.

I am having the same problem as the original poster.

 

[MICHAEL]

You need to do what the message says. Run CMD as Administrator.


-Michael