Did you reboot after doing the "netsh int tcp set global
autotuninglevel=disabled" command?
Jane, not plain

64 bit enabled

Batteries not included. Braincell on vacation :-)
"Jason Mc" <JasonMc@discussions.microsoft.com> wrote in message
news:43FAA35A-11C2-4F64-BA53-3660F1B3D71E@microsoft.com...
> I'm having a similar issue and your suggestion didn't fix my problem.
> Here's
> an example:
>
> I can open up IE and type in http://www.yahoo.com and the page
> renders/displays just fine. Although, when I try to navigate using any
> link
> on the page, it appears to try to access the link (you see it down in the
> status bar) but the page times out with the page cannot be displayed
> error.
> DNS is working fine and from the command line I can resolve/ping domains
> no
> problem. PC is behind a Linksys router which is connected to a Comcast
> cable
> modem. I've got a laptop connected to the same router running XP and don't
> have any problems whatsoever with it. I had this same problem with Vista
> Pre
> RC1 and was hoping it would be fixed by now. Any other suggestions?
>
> "Sergej" wrote:
>
>> right-click on cmd.exe
>> select to run it as administrator
>> and execute this command "netsh int tcp set global
>> autotuninglevel=disabled"
>> without quotes ofcorse.
>>
>> that helped me sort it out.
>>
>>
>> "Garsty" <Garsty@discussions.microsoft.com> wrote in message
>> news:5AECA596-260B-4B4C-AA96-8141B57730C2@microsoft.com...
>> > So here's the issue I've run into both on RC1 and the public beta from
>> > earlier...
>> >
>> > I connect up to my network fine, pull an ip, able to browse shares and
>> > such,
>> > can even ping web sites but when opening Internet Explorer and trying
>> > to
>> > actually browse, the computer fails to find the site. I even see the
>> > browser
>> > status bar acknowledge a dns lookup by telling me the external ip of
>> > the
>> > page
>> > it's trying to hit but again, nothing ever loads. The other computers
>> > on
>> > the
>> > network have no issue of course. Another interesting thing was even
>> > though I
>> > was unable browse various web sites, I was able to download an update
>> > to
>> > Defender during my troubleshooting so it almost seems as if by default,
>> > some
>> > level of security is preventing me from leaving the safety of my
>> > private
>> > network.
>> >
>> > To add some background, the first time I saw the issue was while
>> > playing
>> > with the public beta. It was after a few weeks of normal use when all
>> > of
>> > a
>> > sudden I couldn't get out of the network no matter how hard I tried.
>> > This
>> > time with RC1, it started right after the initial install. I've done
>> > some
>> > browsing of forums and articles and such but haven't found anything
>> > detailing
>> > my issue so I thought it best to toss a question out there. I saw
>> > mention
>> > in
>> > another thread asking about the type of network card being usedso let
>> > me
>> > add
>> > that here too. In my first setup it was a Realtek card and this time
>> > it's
>> > a
>> > Marvell.
>> >
>> > Any thoughts?
>>
>>