pinging a workstation in domain responds with "outside" IP addess

[czarcoma]

--- we have a Domain-based LAN with ip pool of 10.xx.xx.xx
--- we encounter on occasions that some workstations are not able to connect to a server or a workstation.
--- when we try to check cnnectivty by pinging a server or workstation name, it replies as 66.xx.xx.xx (outside,in the internt), instead of the DNS entry 10.xx.xx.xx.
--- we already scanned the workstation using our AV with latest updates.no infectons found.
--- we found no strange processes running (unless we missed something).

 

[NoCalAdmin]

can you release and renew the IP address establishing connectivity to your domain? Or does it continue to boubce to the odd address scheme?

Tom

 

[czarcoma]

--- we're not using DHCP.
--- 10.xx.xx.xx is statically configured on the workstation.
--- seems, being redirected to an outside IP. its weird.
--- also, it's isolated to the said workstation.
--- i dnt want to have to do a clean install, "again".
--- have you hear of malware that produces these kinds of symptoms?

 

[NoCalAdmin]

try changing the nic and re-associate the MAC address with your private ip scheme

other than that....

I'll be monitoring this thread.. the guru's will awake this week and come back to reality now new years is gone
bound to learn something new again...

Tom

 

[czarcoma]

--- changing the NIC aint an potion for me though...
--- all of our workstations have built-in LAN adapters, and we dont keep space NICs around (kind of hard to justify the extra cost until i get the root cause).
--- anyway, might try to disable/enable the adapter on
device manager,and see what happens.
--- thanks.

***

--- ahh, the geat ones should be about in a few hours after a recharge of their mysTECH powers... ;-)

 

[mobyduck]

First up, I'd check the forward and reverse zone entries in the domain DNS for invalid or inappropriate values. If these are ok, check the client machine hosts files, again for invalid entries.

It also might be worth running a tracert to the server name to see where the misdirection is happening.

I am puzzled though as to why you would want to connect workstation to workstation on a domain based LAN...

HTH

MD

 

[wolluf]

You say you get 66. address when pinging the name - but what do you get when pinging the actual IP address?

Have you tried running tracert on the name (and the IP address)?

 

[czarcoma]

mobyduck/wolluf,

--- actualy, already checked the foward and reverse zones first before starting the thread.
-- found no errant entries there.

--- direct ping to ip address is ok.
--- did a trace on the weird ip.
-- 1st hop is our default gateway and out it goes into the internet.

--- also, i observed that the issue occurs after all the computers are logged on.
-- early in the morning, no redirection is occuring.

 

[linney]

Have you got a 66. entry in the errant machines Host file?

Does fixing the Winsock entries as per this FAQ help?
WinXP Connectivity Issues
faq779-4625

 

[czarcoma]

--- nope. no entry on the any of the hots file. checked that earler also.

--- as i mentioned, it is hapening "dynamically".
-- early this morning,was able to receive reply from correct IP.
-- but after the rest of the workstations have logged on for the day, it's when this occurs.

 

[linney]

What happens if you block this 66. address temporarily via a firewall or similar? Who is the 66. site anyway, have you checked that out?