Vista - Internet connectivity issue

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?

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?

Does that command permenantly disable that autotuning thing or do I have to
redo it everytime I startup?

"Sergej" <sbatovanja@undp.ba> wrote in message
news:08C1FFFB-C0FE-417F-8B1E-81F3133F3DE4@microsoft.com...
> 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?
>

Permanent. If you later want to 'undo' it, then it's "netsh int tcp set
global autotuninglevel=normal"


--
Jane, not plain 64 bit enabled
Batteries not included. Braincell on vacation :-)
"Gary" <marauder2004@hotmail.com> wrote in message
news:%23lzE5ft1GHA.2516@TK2MSFTNGP06.phx.gbl...
> Does that command permenantly disable that autotuning thing or do I have
> to redo it everytime I startup?
>
> "Sergej" <sbatovanja@undp.ba> wrote in message
> news:08C1FFFB-C0FE-417F-8B1E-81F3133F3DE4@microsoft.com...
>> 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?
>>
>

Cool, thanks for the tip.
What does that setting do anyway?

I'm having the issue where after a certain amount of time (hours), internet
activity on browsing/email etc ceases to function, but other computers
connected on the network still get internet. I thought maybe it might fix
that up, but will have to let it run overnight to see.

"Jane C" <jellybean@nospam.xjgarage.org> wrote in message
news:90C4517F-F6FB-4B72-98CA-ED5D46223474@microsoft.com...
> Permanent. If you later want to 'undo' it, then it's "netsh int tcp set
> global autotuninglevel=normal"
>
>
> --
> Jane, not plain 64 bit enabled
> Batteries not included. Braincell on vacation :-)
> "Gary" <marauder2004@hotmail.com> wrote in message
> news:%23lzE5ft1GHA.2516@TK2MSFTNGP06.phx.gbl...
>> Does that command permenantly disable that autotuning thing or do I have
>> to redo it everytime I startup?
>>
>> "Sergej" <sbatovanja@undp.ba> wrote in message
>> news:08C1FFFB-C0FE-417F-8B1E-81F3133F3DE4@microsoft.com...
>>> 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?
>>>
>>
>

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?
>
>

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?
>>
>>

It's not 100% conclusive yet, but it seems that fix fixed my issue with
internet connectivity (only in browser and mail) dying after quite a few
hours or something. It seemed it always died overnight. Today though I get
on and everything's still working great.


"Jane C" <jellybean@nospam.xjgarage.org> wrote in message
news838F1D2-4A08-4EC4-AC2D-A701139437B0@microsoft.com...
> 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?
>>>
>>>
>

I found this on http://www.longhornblogs.com/
I thought my problem was my Linksys router but it was really my network
card. I have an onboard Marvell Yukon NIC on my Asus AV8. This fix worked
for me.

Anyone who has installed Vista 5536 on a machine with a Marvell Yukon NIC
knows that it has issues, you cannot browse websites or really do anything
functional on the network. One easy way to fix it is to of course install
the XP NIC Drivers. The other way however, lets you keep the Vista driver
and just fix the root of the problem. Here's how to do it:

1. Go to Start -- Run and type "devmgmt.msc" without quotes.
2. Expand Network Adapters
3. Right Click the Marvell device and go to properties.
4. Click on the advanced tab.
5. Select IPv4 Checksum Offload and set the Value to Disabled.
6. Hit ok and enjoy!

NOTE: This may also work for people who have Realtek network devices and are
experiencing hard system lock-ups when doing anything on the network. No
promises there but I can confirm this works 100% for Marvell.

Additionally if you have a Marvell NIC in 5536 AND then upgrade to 5600, you
will have to uninstall the device (in devmgmt) and then click scan (in
devmgmt) so that it gets installed again. Otherwise the device will not work
properly.

This bug has already been fixed in current builds.

--
J.P.
_____________________________________
This posting is provided "AS IS" with
no warranties, and confers no rights.


"Kittie" <Kittie@discussions.microsoft.com> wrote in message
news:6758407A-BCAB-4062-93C1-FBFF607FB7A8@microsoft.com...
>I found this on http://www.longhornblogs.com/
> I thought my problem was my Linksys router but it was really my network
> card. I have an onboard Marvell Yukon NIC on my Asus AV8. This fix worked
> for me.
>
> Anyone who has installed Vista 5536 on a machine with a Marvell Yukon NIC
> knows that it has issues, you cannot browse websites or really do anything
> functional on the network. One easy way to fix it is to of course install
> the XP NIC Drivers. The other way however, lets you keep the Vista driver
> and just fix the root of the problem. Here's how to do it:
>
> 1. Go to Start -- Run and type "devmgmt.msc" without quotes.
> 2. Expand Network Adapters
> 3. Right Click the Marvell device and go to properties.
> 4. Click on the advanced tab.
> 5. Select IPv4 Checksum Offload and set the Value to Disabled.
> 6. Hit ok and enjoy!
>
> NOTE: This may also work for people who have Realtek network devices and
> are
> experiencing hard system lock-ups when doing anything on the network. No
> promises there but I can confirm this works 100% for Marvell.