I can ping a local PC by its IP, but not by its name

chillpenguin · 09-06-2008, 02:05 AM

From the command prompt, if I ping 192.168.2.2, then I get a reply from that IP. However, if I ping TELETRAN3, then I get a reply from 204.13.161.92.

Pinging TELETRAN3 should produce a reply from 192.168.2.2, not from a computer outside of my network.

I know what you are going to say: update the host file. Yes, that will stop this pinging problem, but updating the host file is just a band aid. There is a deeper issue here and I would like to solve it.

This issue affects all of my computers. If I attempt to ping any computer from any other computer by its name, it will always return that outside IP address.

Anyone have an idea?

**johnwill** · 09-06-2008, 01:59 PM

First off, some information about the network and what the name TELETRAN3 pertains to would be a big help here.

I've seen an effect like this using OpenDNS, and this sure sounds like a DNS issue if that name is local on your network.

jLadd · 02-12-2009, 03:39 PM

My home LAN PCs, I just discovered, are responding to name pings with the 204.13.161.92 address while responding properly to their IP pings. Looking into the problem I discovered this thread.

Has anyone solved this problem and if so, what is the cure?

Thanks

BTW: The LAN is Belkin N1 based and provides Internet and intranet access. The router also provides a DHCP server, NAT and firewall functions. There is nothing in the N1's configuration that is remotely related to 204 addresses.

chillpenguin · 02-13-2009, 08:00 AM

The only way I was able to deal with this problem was to buy another router, since I figured that was the cause of the problem.

I was using a Linksys wireless G router (one of the WRT ones, I forget the model number) when this problem cropped up. It persisted with a Belkin wireless N router.

However, my Vonage phone adapter (which doubles as a router) made the problem go away, as did the Linksys wireless N router that I eventually bought and am now using.

I can't guarantee that getting a new router will fix the problem for you, but that's what did the trick for me.

Oh, and to johnwill: sorry for not replying way back when. The new router fixed my issue shortly after posting, so I never responded. To answer your question though, TELETRAN3 refers to my desktop's name.

**bilbus** · 02-13-2009, 12:51 PM

I would first do a "ipconfig /displaydns"
Then check your cache (hosts and lmhosts files)
Then nbtstat -c

This is the reslution order
1. HOSTs file.
2. DNS - if you added a DNS server to the DNS Search Order option.
3. NetBIOS Name Cache - You can query the cache using the command 'nbtstat -c'.
4. WINS (NetBIOS name server) if configured via the TCP/IP WINS tab.
5. Broadcast - 3 broadcasts
6. LMHosts -If configured via TCP/IP WINS tab. This is on by default.
7. Failure

09-06-2008, 02:05 AM	#1 (permalink)
chillpenguin Registered User Join Date: Sep 2008 Posts: 2 OS: Vista Home Premium x64	I can ping a local PC by its IP, but not by its name From the command prompt, if I ping 192.168.2.2, then I get a reply from that IP. However, if I ping TELETRAN3, then I get a reply from 204.13.161.92. Pinging TELETRAN3 should produce a reply from 192.168.2.2, not from a computer outside of my network. I know what you are going to say: update the host file. Yes, that will stop this pinging problem, but updating the host file is just a band aid. There is a deeper issue here and I would like to solve it. This issue affects all of my computers. If I attempt to ping any computer from any other computer by its name, it will always return that outside IP address. Anyone have an idea?

09-06-2008, 01:59 PM	#2 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,940 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	Re: I can ping a local PC by its IP, but not by its name First off, some information about the network and what the name TELETRAN3 pertains to would be a big help here. I've seen an effect like this using OpenDNS, and this sure sounds like a DNS issue if that name is local on your network. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

02-12-2009, 03:39 PM	#3 (permalink)
jLadd Registered User Join Date: Feb 2009 Posts: 1 OS: XP Pro SP2	Re: I can ping a local PC by its IP, but not by its name My home LAN PCs, I just discovered, are responding to name pings with the 204.13.161.92 address while responding properly to their IP pings. Looking into the problem I discovered this thread. Has anyone solved this problem and if so, what is the cure? Thanks BTW: The LAN is Belkin N1 based and provides Internet and intranet access. The router also provides a DHCP server, NAT and firewall functions. There is nothing in the N1's configuration that is remotely related to 204 addresses.

02-13-2009, 08:00 AM	#4 (permalink)
chillpenguin Registered User Join Date: Sep 2008 Posts: 2 OS: Vista Home Premium x64	Re: I can ping a local PC by its IP, but not by its name The only way I was able to deal with this problem was to buy another router, since I figured that was the cause of the problem. I was using a Linksys wireless G router (one of the WRT ones, I forget the model number) when this problem cropped up. It persisted with a Belkin wireless N router. However, my Vonage phone adapter (which doubles as a router) made the problem go away, as did the Linksys wireless N router that I eventually bought and am now using. I can't guarantee that getting a new router will fix the problem for you, but that's what did the trick for me. Oh, and to johnwill: sorry for not replying way back when. The new router fixed my issue shortly after posting, so I never responded. To answer your question though, TELETRAN3 refers to my desktop's name.

02-13-2009, 12:51 PM	#5 (permalink)
bilbus TSF Enthusiast Join Date: Aug 2006 Posts: 967 OS: OS2 Warp	Re: I can ping a local PC by its IP, but not by its name I would first do a "ipconfig /displaydns" Then check your cache (hosts and lmhosts files) Then nbtstat -c This is the reslution order 1. HOSTs file. 2. DNS - if you added a DNS server to the DNS Search Order option. 3. NetBIOS Name Cache - You can query the cache using the command 'nbtstat -c'. 4. WINS (NetBIOS name server) if configured via the TCP/IP WINS tab. 5. Broadcast - 3 broadcasts 6. LMHosts -If configured via TCP/IP WINS tab. This is on by default. 7. Failure