internet Not working, no hostname resolution

Gotta interesting problem here for ya alls.

My father-in-law's computer is running XP Pro and it has suddenly stopped doing anything on the Internet. All adware and unnecessary programs have been stopped from running(by me). I set up the two Primary and Secondary DNS Servers manually as well. No luck there. When pinging it displays "junk" characters such as this :
C:\DOCUME~1\PETER>ping 168.45.71.154

Pinging ► with 32 bytes of data:

Reply from 192.168.0.1: TTL expired in transit.
Reply from 192.168.0.1: TTL expired in transit.
Reply from 192.168.0.1: TTL expired in transit.
Reply from 192.168.0.1: TTL expired in transit.

Ping statistics for ↓:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

By the way am aware of the 192.168.0.1(network Ip address for his computer) and am looking at it as I type this message but would like to know what other people think. Naturally no webpages will open. I did a quick upgrade/repair of XP and it appeared to fix it but quickly degenerated again. Done a virus scan from my computer over the network and didn't find anything. And doing another one as I type. Umm. What else is there? If you can think of anything else shoot ahead with it
by the way that is not the normal Ping response I get, Usually I get "Request Timed Out" which is expected generally as I'm just shooting off random IP addresses. Just tested pinging Yahoo.com using IP address and it worked fine. So hostname resolution appears to be the main concern. ANother thing on the same note. Just before when he was connected I noticed that the modem was going overboard. Checked the stats in Windows XP and it claimed that 3mb had been downloaded in the last 5 mins on a 56k connection. Which has actual speeds of a 28.8k(tested).

Any ideas would be much appreciated. Thank you

Alkatr0z

Screeeewy! (but you probably guessed that already! )

Sounds to me like either a virus (but you've checked that), the NIC driver has gone bad or the TCP/IP stack is corrupt.

Couple of things to try:

a tracert at the cmd prompt to a known outside IP address (66.102.9.104 for Google or 216.109.118.66 is one of Yahoo's) its just tracert 66.102.9.104 if you don't know.

Try and ping 127.0.0.1 from his machine and see what you get. Does he ping you ok?

Also at the command prompt do a route print and a ipconfig /all and paste that here too. Check he has the correct default gateway set (although that should not give you the junk chars on ping).

You've said your father-in-laws machine is on the 192 subnet. This means its a private address and safe to post IP info.

S

hmm, sounds interesting, TTL stands for "Time-to-live" - TCP/IP packets have a set number of times the packet can be forwarded before it is dropped (deleted). The purpose is to prevent packets from looping indefinitely in the network taking up bandwidth if there is some routing problem. It could be anything, from routing problems from your ISP to a DOS attack of someone.

As DuckIt said post more info, especially ipconfig /all to see what we can find.

Regards

Larz*

My WinXP PC is doing exactly the same thing! Trying Stephen's suggestions:



tracert 66.102.9.104 gives:

Tracing route to over a maximum of 30 hops

1 <1 ms <1 ms <1 ms No resources.



ping 127.0.0.1 gives:

Pinging ► with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 0ú♠:
Packets: Set = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms



route print gives:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 e0 18 fe 49 fd ...... Broadcom NetXtreme Gigabit Ethernet
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.27.2 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.0.0 192.168.27.2 192.168.27.2 20
192.168.27.2 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.27.255 255.255.255.255 192.168.27.2 192.168.27.2 20
224.0.0.0 240.0.0.0 192.168.27.2 192.168.27.2 20
255.255.255.255 255.255.255.255 192.168.27.2 192.168.27.2 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None



ipconfig /all gives:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Greg2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-E0-18-FE-49-FD
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.27.2
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1

Any ideas? Any more suggestions?

Thanks!
Greg Kiser

Go to control pannel > network connections. then right click on Local Area Connection 2. click on internet protocl (tcp/ip) click properties, then make sure obtain an ip address automatically and obtain dns server address automatically are both selected. Also click on the advanced tab at the top of the first window and make sure that the Internet Connection Firewall box is unchecked.

Also if you have a firewall running, try stopping it/shutting it down and see if that fixes your problem. I had a problem with that a few years ago, it was blocking the wrong ports.

Thanks ShEDeViL for the response.



I have configured it both ways (DNS Server or manually) with the same results. I have a PC next to this one on the same network that I can configure both ways and it works either way.



Firewall is unchecked.

The weird thing is the strange characters in the PING command as you can see above. Secondly when I do NSLOOKUP it doesn't find my default server even though I can PING it! It is like everything that has to do with TCP/IP doesn't work. IPX stuff works fine.

Further ideas? Suggestions?

Thanks!
Greg Kiser

Greg. Obtain the IP addresses for your Internet Provider's DNS servers. Add those manually to the DNS settings in Network Neighborhood. By default, your computer is looking to your router for a DNS server the way you have it set. If indeed you do have a DNS server in your router, it will not have the External DNS info that the external servers on the web would have. By adding your IP's DNS servers, if the web address cannot be resolved at your router, it will then look to the external name servers in the order you list them. Personally, I would never have a router as a DNS server. I'd simply remove it and add your IP's servers.

That should solve your problem.

Hi ATNO/TW,

Thanks for the reply, but I have already done that. I have PC2 right beside PC1 that I can configure manually like you are saying and automatically. PC2 works fine either way. But the exact same settings on PC1 do not work. PC1 worked fine for months and was working fine Friday when I shut it down. Powering up on Tuesday, June 1, nothing Internet-ly worked at all. No changes were made to the Network Settings. Since then I've tried:

PC1 = Fails
PC2 = Good

1. Rebooting.
2. Configuring Network with ISP's DNS Server address manually (this works on PC2).
3. Configuring Network to obtain address automatically (this also works on PC2).
4. Uninstalling and reinstalling NIC on PC1.
5. Tried to uninstall TCP/IP protocol, but you can't uninstall it on WinXP Pro. You can only disable it.
6. Installed a second NIC in PC1, but it acts the same way; so I uninstalled it.
7. Installed the same NIC in PC2, it worked fine.
8. Temporarily installed a 2nd hard drive in PC1; and installed WinXP Pro on 2nd hard drive; booted to that new System and Internet works!

Meanwhile PC1 with original WinXP Pro on it will not do anything TCP/IP related. I can't repair it with the "recovery disk" because it will wipe out my registry and I'll have to reinstall all my applications.

Again, symptoms are:

1. PC1 will not do anything TCP/IP related.
2. PC1 gets strange characters in PING command.
3. PC1 gets Winsock Error 10106 when I try to use TCP/IP.
4. PC1's IPX protocol works great.

I have the latest Symantec Antivirus stuff with latest virus files, but <sheesh> it sounds like a virus to me.

Ideas? Suggestions?

Could it be a corrupt Registry entry? Could it be a corrupt DLL? I have found 3 other people on the Internet that have experienced the exact same thing, but still no solutions.

Thanks!
Greg Kiser

I'm starting to think bad hardware. Swap cards between the two machines and install the drivers. If the problem reverses itself, you'll know you have a bad card.

Not sure if this will help, but I had a similar problem with a couple of 98 machines. What fixed it was doing a repair on the winsock.

There is a repair tool for XP called winsockxpfix.exe. (Sorry no link) but you should be able to google it and find it with no problems.

Hope it helps.

I have fixxed this problem twice. Once a simple Interenet Explorer unistall updates and reinstall updates and the other time by using system restore.

It is most likely spy/adware taking over your routing and you have possibly deleted a part of the spyware. This was definately the case on a friends PC and he had KAZAA and attempted to remove it.

LOL

Ken

I made a post here about how to repair the winsock files if you want to look at it.

ATNO, correct me if I am wrong, but this caught my attention:

IP Address. . . . . . . . . . . . : 192.168.27.2
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . : 192.168.0.1 <--

Even though Greg said he manually configured DNS servers, ipconfig shows another thing, it is trying to resolve trough 192.168.0.1 not his ISP servers.

Here's something I found on internet about Winsock error 10106:



Another one:

I noticed that. That was what was puzzling.