Can't Access Internet - Vista Only

Question

ekleist 0 Newbie Poster

18 Years Ago

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

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

* (Router) :

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

* (Google):

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:

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.

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

* (Router) :

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

* (Google):

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

- www.google.com

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 , subnet mask to , gateway to , and dns to 192.168.0.1.

Ping results now:

* localhost: Successful

* 127.0.0.1: Successful

* (Router) :

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

* (Google):

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:

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

* www.google.com (second attempt):

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.

microsoft:windows-vista-7-8 router-proxy-firewall

3 Contributors
5 Replies
278 Views
1 Day Discussion Span
Latest Post 18 Years Ago Latest Post by submitqueen

Dani AI

Generated 9 Months Ago

Short expert summary and focused troubleshooting steps (adds to , , )

The symptoms described by — intermittent APIPA addressing, successful connectivity from the laptop, and a full fix after installing a different PCI NIC — point to a NIC driver or hardware/compatibility problem rather than the router itself. Seeing a 169.254.x.x address is Windows falling back to APIPA because DHCP negotiation failed; that is a useful diagnostic sign and explains “no Internet” even when the router is otherwise fine. (learn.microsoft.com)

Practical checklist to isolate and fix (do these as administrator)

Quick stack refresh and DHCP retry (run from an elevated command prompt):

ipconfig /release
ipconfig /flushdns
ipconfig /renew
netsh int ip reset resetlog.txt
netsh winsock reset

Reboot after the netsh commands. If a driver bug or Winsock/TCP-IP corruption is involved these steps often restore normal DHCP behavior. If renew still fails, uninstall the NIC in Device Manager (choose to remove driver files if prompted), reboot, then install the latest Vista x64 NIC driver from the motherboard/vendor or the NIC maker. (learn.microsoft.com)

If the problem persists

Test the onboard NIC outside Windows: boot a Linux live USB and check whether it obtains a DHCP lease. If Linux also fails, the hardware or PHY on the onboard port is suspect.
Update the motherboard BIOS and chipset drivers before re-testing.
As a known Vista-era interoperability cause, try the DHCP broadcast-flag toggle described in Microsoft guidance (add DhcpConnEnableBcastFlagToggle under the adapter GUID in the registry and reboot) if your DHCP server/router behaves oddly; back up the registry first. (support.microsoft.com)

Why this ties to the thread

’s router-compatibility note is relevant historically, but the fact that a new NIC immediately restored connectivity on the same LAN implicates the desktop NIC or its driver. The steps above let readers confirm hardware vs driver and apply safe fixes that won’t lose the original thread detail.

All 5 Replies

Laser 84 Posting Whiz

18 Years Ago

According to you need WGT624 v3 for compatibility with Vista.

submitqueen 0 Newbie Poster

18 Years Ago

The question is from where are you getting the IP address, DNS and DHCP. the series you mentioned is a private series, It also depends on if this is internet or intranet.

Reply to this topic

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

ekleist 0 Newbie Poster · Answer 1 · 2008-06-17T05:08:10+00:00

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 0 Newbie Poster · Answer 2 · 2008-06-17T05:42:20+00:00

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

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 0 Newbie Poster · Answer 3 · 2008-06-17T07:40:33+00:00

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

Can't Access Internet - Vista Only

Dani AI

Recommended Answers Collapse Answers

All 5 Replies

Recommended Answers