Vista - Can't Access Internet - Vista Only

**ekleist** · 06-16-2008

Hi. I just upgraded from Windows XP x86 to Windows Vista x64 on my desktop. Immediately after my successful installation, I plugged the computer in to the internet but was unable to connect. First, let me explain my connection

I am using the motherboards (Asus P5NSLI) integrated network jack. I have a wired connection to a router (Netgear WGT624 v2.) There is also a wired connection from the router to this XP x86 laptop that I am posting this from, so the internet and router definitely work. My ISP is Comcast.

With everything in its default settings (before attempting any suggested fixes), here is my ipconfig /all

Code:

Microsoft Windows [Version 6.0.6001]
  Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
   
  C:\Users\Evan>ipconfig /all
   
  Windows IP Configuration
   
     Host Name . . . . . . . . . . . . : Evan-PC
     Primary Dns Suffix  . . . . . . . :
     Node Type . . . . . . . . . . . . : Hybrid
     IP Routing Enabled. . . . . . . . : No
     WINS Proxy Enabled. . . . . . . . : No
     DNS Suffix Search List. . . . . . : comcast.net
   
  Ethernet adapter Local Area Connection:
   
     Connection-specific DNS Suffix  . : comcast.net
     Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigab
  it Ethernet Controller
     Physical Address. . . . . . . . . : 00-18-F3-64-D9-9B
     DHCP Enabled. . . . . . . . . . . : Yes
     Autoconfiguration Enabled . . . . : Yes
     Link-local IPv6 Address . . . . . : fe80::811a:a0c3:61ae:a93c%11(Preferred)
     IPv4 Address. . . . . . . . . . . : 192.168.0.5(Preferred)
     Subnet Mask . . . . . . . . . . . : 255.255.255.0
     Lease Obtained. . . . . . . . . . : Sunday, June 15, 2008 7:12:54 PM
     Lease Expires . . . . . . . . . . : Monday, June 16, 2008 7:12:30 PM
     Default Gateway . . . . . . . . . : 192.168.0.1
     DHCP Server . . . . . . . . . . . : 192.168.0.1
     DNS Servers . . . . . . . . . . . : 192.168.0.1
     NetBIOS over Tcpip. . . . . . . . : Enabled
   
  Tunnel adapter Local Area Connection* 6:
   
     Media State . . . . . . . . . . . : Media disconnected
     Connection-specific DNS Suffix  . : comcast.net
     Description . . . . . . . . . . . : Microsoft ISATAP Adapter
     Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes
   
  Tunnel adapter Local Area Connection* 7:
   
     Media State . . . . . . . . . . . : Media disconnected
     Connection-specific DNS Suffix  . :
     Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
     Physical Address. . . . . . . . . : 02-00-54-55-4E-01
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes

Here are some attempts at pinging, with everything at default settings.

localhost: Successful

127.0.0.1: Successful

192.168.0.1 (Router) :

Code:

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.5: Destination host unreachable.

64.233.167.147 (Google):

Code:

Pinging 64.233.167.147 with 32 bytes of data:
Reply from 192.168.0.5: Destination host unreachable.
Request timed out.

www.google.com:

Code:

Pinging www.l.google.com [64.233.167.104] with 32 bytes of data:
Request timed out.

I began by searching the internet for people experiencing similar problems, and I attempted all the suggested fixes with no success. It is possible that I may have done one or more of the steps incorrectly, but I tried multiple times. Here is what I have tried with no luck.

- Disabling UAC
- Disabling Windows Firewall
- Disabling IPv6
- Disabling TCP and IPv4 Checksum Offload
- Manually assigning an IP address, DNS Server, and gateway

After disabling IPv6 and disabling Checksum Offload, I saw some differences in ipconfig and pinging.

Code:

Microsoft Windows [Version 6.0.6001]
  Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
   
  C:\Users\Evan>ipconfig /all
   
  Windows IP Configuration
   
     Host Name . . . . . . . . . . . . : Evan-PC
     Primary Dns Suffix  . . . . . . . :
     Node Type . . . . . . . . . . . . : Hybrid
     IP Routing Enabled. . . . . . . . : No
     WINS Proxy Enabled. . . . . . . . : No
   
  Ethernet adapter Local Area Connection:
   
     Connection-specific DNS Suffix  . :
     Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigab
  it Ethernet Controller
     Physical Address. . . . . . . . . : 00-18-F3-64-D9-9B
     DHCP Enabled. . . . . . . . . . . : Yes
     Autoconfiguration Enabled . . . . : Yes
     Autoconfiguration IPv4 Address. . : 169.254.169.60(Preferred)
     Subnet Mask . . . . . . . . . . . : 255.255.0.0
     Default Gateway . . . . . . . . . :
     NetBIOS over Tcpip. . . . . . . . : Enabled
   
  Tunnel adapter Local Area Connection* 6:
   
     Media State . . . . . . . . . . . : Media disconnected
     Connection-specific DNS Suffix  . :
     Description . . . . . . . . . . . : Microsoft ISATAP Adapter
     Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes
   
  Tunnel adapter Local Area Connection* 7:
   
     Media State . . . . . . . . . . . : Media disconnected
     Connection-specific DNS Suffix  . :
     Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
     Physical Address. . . . . . . . . : 02-00-54-55-4E-01
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes
   
  C:\Users\Evan>

Ping results now

localhost: Successful

127.0.0.1: Successful

192.168.0.1 (Router) :

Code:

Pinging 192.168.0.1 with 32 bytes of data:
PING: transmit failed, error code 1231.

64.233.167.147 (Google):

Code:

Pinging 64.233.167.147 with 32 bytes of data:
PING: transmit failed, error code 1231.

- www.google.com

Code:

Ping request could not find host www.google.com. Please check the name and try again.

I noticed in the ipconfig that the ip assigned was 169.254 which i thought was strange because it had always been 192.168 before. I then edited the IPv4 settings to use manual ip assignment to 192.168.0.5, subnet mask to 255.255.255.0, gateway to 192.168.0.1, and dns to 192.168.0.1.

Ping results now:

localhost: Successful

127.0.0.1: Successful

192.168.0.1 (Router) :

Code:

Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.

64.233.167.147 (Google):

Code:

Pinging 64.233.167.147 with 32 bytes of data:
Reply from 64.233.167.147: bytes=32 time=2549ms TTL=238
  Request timed out.
  Reply from 64.233.167.147: bytes=32 time=1795ms TTL=238
  Request timed out.

www.google.com:

Code:

Ping request could not find host www.google.com. Please check the name and try again.

www.google.com (second attempt):

Code:

Pinging www.l.google.com [74.125.19.103] with 32 bytes of data:
Request timed out.
  Reply from 74.125.19.103: bytes=32 time=1974ms TTL=241
  Request timed out.
  Request timed out.

I hope that the information provided will help in troubleshooting my network problem. Thank you in advance for your time in aiding me.

**sidney1st** · 06-16-2008

Hi ekleist and welcome to the Vista forums.

First, reconfigure to get automatic IP, you can eventually change after ping resolution.
Verify your ethernet cable.
Then verify your "inboard" ethernet card. (64 bit driver, bios setup, etc...)
Verify that it does not come from the AV software.

**ekleist** · 06-16-2008

I reconfigured for automatic ip. I verified the ethernet cable, and then went ahead and tried a different cable in a different port on router, no luck. I double chekced the drivers and they are the most recent Marvell Yukon drivers for Vista x64. Since this is a fresh install, I have not installed any antivirus yet. I double checked to make sure windows firewall is disabled.

Edit - I wanted to add that I also reverted my bios back to default after reading that it worked for someone. No luck. I saw two things in bios that seemed related to the network card.
Onboard Marvell Lab [Enabled]
Onboard Marvell Lan Boot ROM [Disabled]

**sidney1st** · 06-16-2008

In the device manager ( devmgmt.msc ) the inboard controller does not show any problems?

**ekleist** · 06-16-2008

Correct - It says this device is working properly.

I poked around the netgear website a bit and saw that they no longer offer updates for my version of router. I think tomorrow I am going to try buying a new router that has the "vista certified" logo on it to see if maybe the router just isnt compatible with vista

**sidney1st** · 06-16-2008

Yep but strange, you should be able to ping the router via ethernet.
Can you check the router configuration with the other computer (DHCP, allocated IP, etc...)

**ekleist** · 06-16-2008

Yes, I am able to log in to the router fine from my laptop. I checked to make sure I have the most recent firmware installed.

Today I went out and bought a new router, one that was labeled as supporting windows vista. I purchased a Netgear WGR614 v7. I set it up and have the same problems. I am able to access the internet from this laptop wired or wirelessly, but not on the desktop running vista x64.

Its very strange, I believe the desktop connects to the router fine because ipconfig /all shows it having a proper IP and everything. But, when I ping the router or any website I get usually get request timed out, or sometimes it will ping correctly but the delay is like 2k. So it seems like it talks to the router fine but the response time is very very slow, causing it to time out.

**ekleist** · 06-16-2008

the connection with the new router is wired. I posted multiple ipconfig /all in the original post, but here is another one.

This is an ipconfig /all with everything at default vista settings, except for UAC and windows firewall disabled. Autotuning=normal, Checksum Offload enabled, reg edits normal (dhcp broadcast), etc

Code:

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Evan>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Evan-PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigab
it Ethernet Controller
   Physical Address. . . . . . . . . : 00-18-F3-64-D9-9B
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::2122:d70a:26f3:124e%11(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.18.78(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Evan>

It seems very hit and miss. I notice in there that the IP is 169. which I think indicates a problem with DHCP and obviously why I cant connect to router, but sometimes I am able to get it to give me a 192.168 address which means it connected to router fine. When I have a 169 address pinging the router gives an error code 1231, but when I have a 192 address sometimes it is able to ping with a huge delay, sometimes it says destination host unreachable, and sometimes it says request timed out.

**ekleist** · 06-16-2008

Update - After purchasing the new router and having no luck I decided to purchase a new netowork card, one labeled as "vista compatible." Plugged it in and viola, internet access. Now, the onboard network worked prior to upgrading from xp x86 to vista x64. My board, p5nsli, is listed as vista compatible. This would indicate that the network /should/ work. Is it something to do with 64 bit? I would still like to indentify the problem with this onboard device.

Now that I am connected ot the internet I am going to check for windows updates and make sure all drivers are up to date. Maybe then it will work /shrug

**Dwarf** · 06-17-2008

Hi ekleist,

Since your last post stated the onboard network controller worked with 32-bit but not 64-bit, this indicates that it is not a hardware fault but a software fault, possibly a driver issue. I have managed to source some 64-bit drivers for you directly from Marvell - you could try these to see if that helps. I strongly advise you to create a restore point prior to doing this, and remind you that there is no guarantee that it will work, but at least there is a good chance that this will help you. Note that when you click on the link, it will take you to the main search page. You will need to select 'Network Controller' under 'Step 1:...' and then 'Windows Vista x64 (64-bit)' under 'Step 2:...' and then click 'Submit'. This will then bring up a list of results. One of these results is 'Windows Vista and Server 2008 x64 Driver (64-bit) for Yukon Devices', dated 5/20/08, version 10.61.2.3. There are some other files here which might also help you, but this is the main driver and I provide a separate link for that as well.
Dwarf

Main Search Page
http://www.marvell.com/drivers/search.do

Driver
http://www.marvell.com/drivers/drive...o?driverId=154

06-16-2008	#2 (permalink)
sidney1st Ultimate SP1 x64 & x86 971 posts	Re: Can't Access Internet - Vista Only Hi ekleist and welcome to the Vista forums. First, reconfigure to get automatic IP, you can eventually change after ping resolution. Verify your ethernet cable. Then verify your "inboard" ethernet card. (64 bit driver, bios setup, etc...) Verify that it does not come from the AV software.
My System Specs

06-16-2008	#3 (permalink)
ekleist Vista x64 6 posts	Re: Can't Access Internet - Vista Only I reconfigured for automatic ip. I verified the ethernet cable, and then went ahead and tried a different cable in a different port on router, no luck. I double chekced the drivers and they are the most recent Marvell Yukon drivers for Vista x64. Since this is a fresh install, I have not installed any antivirus yet. I double checked to make sure windows firewall is disabled. Edit - I wanted to add that I also reverted my bios back to default after reading that it worked for someone. No luck. I saw two things in bios that seemed related to the network card. Onboard Marvell Lab [Enabled] Onboard Marvell Lan Boot ROM [Disabled] Last edited by ekleist; 06-16-2008 at 05:06 AM.. Reason: Additional Info
My System Specs

06-16-2008	#4 (permalink)
sidney1st Ultimate SP1 x64 & x86 971 posts	Re: Can't Access Internet - Vista Only In the device manager ( devmgmt.msc ) the inboard controller does not show any problems?
My System Specs

06-16-2008	#5 (permalink)
ekleist Vista x64 6 posts	Re: Can't Access Internet - Vista Only Correct - It says this device is working properly. I poked around the netgear website a bit and saw that they no longer offer updates for my version of router. I think tomorrow I am going to try buying a new router that has the "vista certified" logo on it to see if maybe the router just isnt compatible with vista
My System Specs

06-16-2008	#6 (permalink)
sidney1st Ultimate SP1 x64 & x86 971 posts	Re: Can't Access Internet - Vista Only Yep but strange, you should be able to ping the router via ethernet. Can you check the router configuration with the other computer (DHCP, allocated IP, etc...)
My System Specs

06-16-2008	#7 (permalink)
ekleist Vista x64 6 posts	Re: Can't Access Internet - Vista Only Yes, I am able to log in to the router fine from my laptop. I checked to make sure I have the most recent firmware installed. Today I went out and bought a new router, one that was labeled as supporting windows vista. I purchased a Netgear WGR614 v7. I set it up and have the same problems. I am able to access the internet from this laptop wired or wirelessly, but not on the desktop running vista x64. Its very strange, I believe the desktop connects to the router fine because ipconfig /all shows it having a proper IP and everything. But, when I ping the router or any website I get usually get request timed out, or sometimes it will ping correctly but the delay is like 2k. So it seems like it talks to the router fine but the response time is very very slow, causing it to time out.
My System Specs

06-16-2008	#9 (permalink)
ekleist Vista x64 6 posts	Re: Can't Access Internet - Vista Only Update - After purchasing the new router and having no luck I decided to purchase a new netowork card, one labeled as "vista compatible." Plugged it in and viola, internet access. Now, the onboard network worked prior to upgrading from xp x86 to vista x64. My board, p5nsli, is listed as vista compatible. This would indicate that the network /should/ work. Is it something to do with 64 bit? I would still like to indentify the problem with this onboard device. Now that I am connected ot the internet I am going to check for windows updates and make sure all drivers are up to date. Maybe then it will work /shrug
My System Specs

06-17-2008	#10 (permalink)
Dwarf Vista Home Premium 32-bit & Vista Ultimate 64-bit both Service Pack 2 W7 Pro RTM 7600 32 & 64 2,180 posts	Re: Can't Access Internet - Vista Only Hi ekleist, Since your last post stated the onboard network controller worked with 32-bit but not 64-bit, this indicates that it is not a hardware fault but a software fault, possibly a driver issue. I have managed to source some 64-bit drivers for you directly from Marvell - you could try these to see if that helps. I strongly advise you to create a restore point prior to doing this, and remind you that there is no guarantee that it will work, but at least there is a good chance that this will help you. Note that when you click on the link, it will take you to the main search page. You will need to select 'Network Controller' under 'Step 1:...' and then 'Windows Vista x64 (64-bit)' under 'Step 2:...' and then click 'Submit'. This will then bring up a list of results. One of these results is 'Windows Vista and Server 2008 x64 Driver (64-bit) for Yukon Devices', dated 5/20/08, version 10.61.2.3. There are some other files here which might also help you, but this is the main driver and I provide a separate link for that as well. Dwarf Main Search Page http://www.marvell.com/drivers/search.do Driver http://www.marvell.com/drivers/drive...o?driverId=154 Last edited by Dwarf; 06-17-2008 at 05:30 AM..
My System Specs

Similar Threads
Thread	Forum
Vista won't allow me to access the internet.	Network & Sharing
Vista w/ICS and VPN w/one nic and no internet access	Vista General
Wireless router - Local access OK but NO internet access - HELP!!	Vista networking & sharing
Vista - Limited Internet Access	Vista General
Exteamly slow internet access (not LAN access)...SPI on router??	Vista networking & sharing