Vista - Internet connectivity issue

I have the Marvell NIC (onboard) on my other system (A8N-SLI) and had that
issue, but the other Nvidia Nforce onboard NIC wasn't being used so just did
a simple change. But at least I can incorporate that fix now incase I do use
the Marvel. Nice find

"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.

Thanks.

It helped me a lot.

Cyb


"Kittie" wrote:

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

OK, I have a question.... I have the Marvell Yukon NIC. I could not connect
to most website, but could to a select few. I DL'ed & installed the drivers
from Yukon for my 32bit RC1 installation. This seemed to fix my concern.
However, I could not connect to a specific website...namely
https://secure.spiritbank.com. So I have been searching and found this "fix".
I applied it and now I am able to connect to and display that page.

So, my question is......
What is "autotuning" and how did you come to find that fix? It seems to have
worked for me and I do appreciate it. THANK YOU Sergej!!!!!!

"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.
>

OK, I have a question.... I have the Marvell Yukon NIC. I could not connect
to most website, but could to a select few. I DL'ed & installed the drivers
from Yukon for my 32bit RC1 installation. This seemed to fix my concern.
However, I could not connect to a specific website...namely
https://secure.spiritbank.com. So I have been searching and found this "fix".
I applied it and now I am able to connect to and display that page.

So, my question is......
What is "autotuning" and how did you come to find that fix? It seems to have
worked for me and I do appreciate it. THANK YOU Sergej!!!!!!

"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.

http://windowshelp.microsoft.com/com...sloc=en-us&p=1

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

OK, I have a question.... I have the Marvell Yukon NIC. I could not connect
to most website, but could to a select few. I DL'ed & installed the drivers
from Yukon for my 32bit RC1 installation. This seemed to fix my concern.
However, I could not connect to a specific website...namely
https://secure.spiritbank.com. So I have been searching and found this "fix".
I applied it and now I am able to connect to and display that page.

So, my question is......
What is "autotuning" and how did you come to find that fix? It seems to have
worked for me and I do appreciate it. THANK YOU Sergej!!!!!!

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

Sorry about the duplicates, guys. It told me several time that the post
failed & to try again. By the time it went through. it had gone through 5
times.

Slaton