Re: Pinging 192.168.1.x IP address returns wrong IP
- From: "Robert L. \(MS-MVP\)" <blinNoEmailPlease@xxxxxxxx>
- Date: Tue, 8 Apr 2008 20:45:55 -0500
In most cases, this is DNS suffix issue. Use ipconfig /all to check the settings or check this search result for more details.
troubleshooting ping issuesPing lists a public IP instead of private IP. Symptom: when you ping a LAN computer like ping chicagotechpc1, you may receive a public ip 64.176.153.103 ...
www.chicagotech.net/troubleshootingping.htm
--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Gary" <tuffboystl@xxxxxxxxxxx> wrote in message news:%23KRVSOdmIHA.4536@xxxxxxxxxxxxxxxxxxxxxxx
I have a couple Windows XP Pro machines with most of the updates.
I have 12 of them at remote locations. I am using Netgear's VPN client to
connect to the main office for the remote locations to enter their
accounting data.
This has worked pretty well on several PCs. However, on a few of them, when
I ping any address at 192.168.1.x, it will return ping results for
10.44.something. I don't remember the exact IP address. I did google the
IP address just in case but I didn't come up with anything good.
I noticed this on two machines after installing the VPN client.
Interestingly enough, it happens both when connected and disconnected from
the VPN.
My first thought was spyware. I used ad aware and spybot on the machines
with caught a little..nothing significant. But didn't fix anything. I used
this WinXP TCP/IP fix program that I found on the web. I like using it for
certain spyware that screws up the protocol in some way. But that did
nothing. I'm pretty good at eradicating most destructive spyware. Somehow
though, I still think it's spyware...but I almost want to blame the VPN
software. I actually uninstalled the VPN software on one of the machines to make sure
the problem would still exist. It still returned the wrong address.
So, I'm stuck. I'm not sure what troubleshooting there is left to do.
Pinging an IP address to me seems like the most basic test to see if TCP/IP
is working. I would assume it's not DNS...since pinging an IP address
shouldn't query a DNS server.
Does anyone have any suggestions on what to do next?
Thank you!
Gary
.
- References:
- Prev by Date: Re: Slow Network Browsing - MS Office
- Next by Date: Re: Home network and file sharing
- Previous by thread: Pinging 192.168.1.x IP address returns wrong IP
- Index(es):
Relevant Pages
|
