Pinging 192.168.1.x IP address returns wrong IP

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




.

Relevant Pages

  • Cant map to VPN machines outside home router with z2PocketLan
    ... I downloaded PocketLan shortly after purchasing the Starcom and am so ... With VPN on I can use map folders on all my home machines (behind the ...
    (microsoft.public.pocketpc)
  • Can not access local resources over VPN
    ... I am connecting to my office via the VPN connection on a Windows XP SP2 ... The local network at work is using ... - I can access machines on my office domain via http ...
    (microsoft.public.windows.server.networking)
  • Pinging 192.168.1.x IP address returns wrong IP
    ... I have a couple Windows XP Pro machines with most of the updates. ... I have 12 of them at remote locations. ... I noticed this on two machines after installing the VPN client. ...
    (microsoft.public.windowsxp.general)
  • RE: Integrating Domain and VPN Login
    ... More than likely I was misinformed and these machines are not actually ... Integrating Domain and VPN Login ... dial-up connection' at the logon screen. ...
    (Focus-Microsoft)
  • Re: Mapping a Networked drive letter over VPN
    ... Are these roaming / individual remote machines, or is there a remote office with several machines at the same remote location? ... If you have a remote office, the best solution is most likely going to be a persistent router-to-router VPN. ... Group Policy Preferences execute during login, so if you have these configured to map drives automatically, the drive will be mapped during login as long as the VPN connection is already established. ...
    (microsoft.public.windows.server.sbs)