Can't Access Internet - Vista Only

ekleist

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

My Computer

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 Computer

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:

My Computer

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 Computer

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 Computer

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 Computer

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.
 

My Computer

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 Computer

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/driverDisplay.do?driverId=154
 
Last edited:

My Computer

System One

  • Manufacturer/Model
    Dwarf Dwf/11/2012 r09/2013
    CPU
    Intel Core-i5-3570K 4-core @ 3.4GHz (Ivy Bridge) (OC 4.2GHz)
    Motherboard
    ASRock Z77 Extreme4-M
    Memory
    4 x 4GB DDR3-1600 Corsair Vengeance CMZ8GX3M2A1600C9B (16GB)
    Graphics Card(s)
    MSI GeForce GTX770 Gaming OC 2GB
    Sound Card
    Realtek High Definition on board solution (ALC 898)
    Monitor(s) Displays
    ViewSonic VA1912w Widescreen
    Screen Resolution
    1440x900
    Hard Drives
    OCZ Agility 3 120GB SATA III x2 (RAID 0)
    Samsung HD501LJ 500GB SATA II x2
    Hitachi HDS721010CLA332 1TB SATA II
    Iomega 1.5TB Ext USB 2.0
    WD 2.0TB Ext USB 3.0
    PSU
    XFX Pro Series 850W Semi-Modular
    Case
    Gigabyte IF233
    Cooling
    1 x 120mm Front Inlet 1 x 120mm Rear Exhaust
    Keyboard
    Microsoft Comfort Curve Keyboard 3000 (USB)
    Mouse
    Microsoft Comfort Mouse 3000 for Business (USB)
    Internet Speed
    NetGear DG834Gv3 ADSL Modem/Router (Ethernet) ~4.0 Mb/s (O2)
    Other Info
    Optical Drive: HL-DT-ST BD-RE BH10LS30 SATA Bluray
    Lexmark S305 Printer/Scanner/Copier (USB)
    WEI Score: 8.1/8.1/8.5/8.5/8.25
    Asus Eee PC 1011PX Netbook (Windows 7 x86 Starter)
Are you on a IPv6 network? You DNS settings IPv6? Did you try disabling IPv6 and only using IPv4.
 

My Computer

System One

  • CPU
    pair of Intel E5430 quad core 2.66 GHz Xeons
    Motherboard
    Supermicro X7DWA-N server board
    Memory
    16GB DDR667
    Graphics Card(s)
    eVGA 8800 GTS 640 MB video card
    Hard Drives
    SAS RAID

My Computers

System One System Two

  • Operating System
    Windows 10 Pro X64 Insider Preview (Skip Ahead) latest build
    Manufacturer/Model
    The Beast Model V (homebrew)
    CPU
    Intel Core i7 965 EE @ 3.6 GHz
    Motherboard
    eVGA X58 Classified 3 (141-GT-E770-A1)
    Memory
    3 * Mushkin 998981 Redline Enhanced triple channel DDR3 4 GB CL7 DDR3 1600 MHz (PC3-12800)
    Graphics Card(s)
    eVGA GeForce GTX 970 SSC ACX 2.0 (04G-P4-3979-KB)
    Sound Card
    Realtek HD Audio (onboard)
    Monitor(s) Displays
    2 * Lenovo LT2323pwA Widescreeen
    Screen Resolution
    2 * 1920 x 1080
    Hard Drives
    SanDisk Ultra SDSSDHII-960G-G25 960 GB SATA III SSD (System)
    Crucial MX100 CT256MX100SSD1 256GB SATA III SSD (User Tree)
    2 * Seagate Barracuda 7200.12 ST31000528AS 1TB 7200 RPM SATA II Mech. HD
    Seagate ST1500DL001-9VT15L Barracuda 7200.12 1.5 TB S
    PSU
    Thermaltake Black Widow TX TR2 850W 80+ Bronze Semi-Mod ATX
    Case
    ThermalTake Level 10 GT (Black)
    Cooling
    Corsair H100 (CPU, dual 140 mm fans on radiator) + Air (2 *
    Keyboard
    Logitech G15 (gen 2)
    Mouse
    Logitech MX Master (shared)
    Internet Speed
    AT&T Lightspeed Gigabit duplex
  • Operating System
    Sabayon Linux (current, weekly updates, 5.1.x kernel)
    Manufacturer/Model
    Lenovo ThinkPad E545
    CPU
    AMD A6-5350M APU
    Motherboard
    Lenovo
    Memory
    8 GB
    Graphics card(s)
    Radeon HD (Embedded)
    Sound Card
    Conextant 20671 SmartAudio HD
    Monitor(s) Displays
    Lenovo 15" Matte
    Screen Resolution
    1680 * 1050
    Hard Drives
    INTEL Cherryvill 520 Series SSDSC2CW180A 180 GB SSD
    PSU
    Lenovo
    Case
    Lenovo
    Cooling
    Lenovo
    Mouse
    Logitech MX Master (shared) | Synaptics TouchPad
    Keyboard
    Lenovo
    Internet Speed
    AT&T LightSpeed Gigabit Duplex
Back
Top