Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hello,
Long time lurker... finally have a problem I can't solve through Google.
I have my PC wired behind a Linksys WRT54G wireless router. This morning I could not access the Internet via Firefox or IE7. My laptop could access the Internet via wireless connection and wired connection. I ran the network diagnostic and received the following output:
Last diagnostic run time: 10/10/07 10:55:26 DNS Client Diagnostic
DNS - Not a home user scenarioinfo Using Web Proxy: no
info Resolving name ok for (www.microsoft.com): no
warn Unrecognized WinSock NSP: NWLink IPX/SPX/NetBIOS Compatible Transport Protocol
No DNS serversDNS failure
info Query [www.microsoft.com] against DNS Server 192.168.1.2, (Type = 0x1, Options = 0x10e8) returns 0x5b4
action Automated repair: Renew IP address
action Releasing the current IP address...
error Error releasing the current IP address: The system cannot find the file specified.
info Query [www.microsoft.com] against DNS Server 192.168.1.2, (Type = 0x1, Options = 0x10e8) returns 0x5b4
info Redirecting user to support call
Gateway Diagnostic
Gatewayinfo The following proxy configuration is being used by IE: Automatically Detect Settings:Enabled Automatic Configuration Script: Proxy Server: Proxy Bypass list:
info Could not get proxy settings via the Automatic Proxy Configuration mechanism
info This computer has the following default gateway entry(ies): 192.168.1.2
info This computer has the following IP address(es): 192.168.1.22
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc). Could be either gateway or DNS issue
action Automated repair: Reset network connection
action Disabling the network adapter
action Enabling the network adapter
info Network adapter successfully enabled
error Unexpected error from iphlpapi: The pipe is being closed.
error Unexpected error from iphlpapi: The pipe is being closed.
error Unexpected error from iphlpapi: The pipe is being closed.
info This computer has the following default gateway entry(ies): 192.168.1.2
info This computer has the following IP address(es): 192.168.1.22
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc). Could be either gateway or DNS issue
action Manual repair: Reboot modem
info This computer has the following default gateway entry(ies): 192.168.1.2
info This computer has the following IP address(es): 192.168.1.22
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc). Could be either gateway or DNS issue
info Waiting some time for the modem/router to stabilize
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc). Could be either gateway or DNS issue
IP Layer Diagnostic
Corrupted IP routing tableinfo The default route is valid
info The loopback route is valid
info The local host route is valid
info The local subnet route is valid
Invalid ARP cache entriesaction The ARP cache has been flushed
IP Configuration Diagnostic
Invalid IP addressinfo Valid IP address detected: 192.168.1.22
Wireless Diagnostic
Wireless - Service disabledWireless - User SSID
Wireless - First time setup
Wireless - Radio off
Wireless - Out of range
Wireless - Hardware issue
Wireless - Novice user
Wireless - Ad-hoc network
Wireless - Less preferred
Wireless - 802.1x enabled
Wireless - Configuration mismatch
Wireless - Low SNR
WinSock Diagnostic
WinSock statusinfo All base service provider entries are present in the Winsock catalog.
info The Winsock Service provider chains are valid.
info Provider entry MSAFD Tcpip [TCP/IP] passed the loopback communication test.
info Provider entry MSAFD Tcpip [UDP/IP] passed the loopback communication test.
info Provider entry RSVP UDP Service Provider passed the loopback communication test.
info Provider entry RSVP TCP Service Provider passed the loopback communication test.
info Connectivity is valid for all Winsock service providers.
Network Adapter Diagnostic
Network location detectioninfo Using home Internet connection
Network adapter identificationinfo Network connection: Name=Local Area Connection, Device=Intel(R) PRO/100 VE Network Connection, MediaType=LAN, SubMediaType=LAN
info Network connection: Name=Internet Connection, Device=Internet Connection, MediaType=SHARED ACCESS HOST LAN, SubMediaType=NONE
info Ethernet connection selected
Network adapter statusinfo Network connection status: Connected
HTTP, HTTPS, FTP Diagnostic
HTTP, HTTPS, FTP connectivitywarn HTTP: Error 12007 connecting to www.microsoft.com: The server name or address could not be resolved
warn HTTPS: Error 12007 connecting to www.microsoft.com: The server name or address could not be resolved
warn FTP (Passive): Error 12007 connecting to ftp.microsoft.com: The server name or address could not be resolved
warn HTTP: Error 12007 connecting to www.hotmail.com: The server name or address could not be resolved
warn HTTPS: Error 12007 connecting to www.passport.net: The server name or address could not be resolved
error Could not make an HTTP connection.
error Could not make an HTTPS connection.
error Could not make an FTP connection.
It appears I am having DNS problems. I went into Network Connections and changed from a static IP/ DNS server to a dynamic one and I can now access the Internet. My problem is that I would rather have the static IP/DNS address. Any idea what my problem may be? Let me know if you need any more information. Thanks

Yes. The original problem occured when the ip address for the router was 192.168.1.1. I read that sometimes a change from that original number may fix the problem but it didn't.

I'm a little confused here as to what you have, could do - and can do now...
How many PC/laptops involved; what can connect to the www; what can see/connect to other PC/laptops?

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |