Skip to main content

win xp unable to resolve ip to host name

More
19 years 7 months ago #5346 by steveb12
Hoping someone can help me with a Windows XP issue. I have a mixed Windows NT 4/2000/XP domain. The domain controllers are Windows NT 4. I have a few XP client machines that cannot resolve host names from doing a ping -a command. Some of these XP clients are DHCP and some have static ips set. Neither configuration can resolve a host name.

Anyone have any ideas?

Thanks!
More
19 years 7 months ago #5349 by FallenZer0

-There Is A Foolish Corner In The Brain Of The Wisest Man- Aristotle
More
19 years 7 months ago #5350 by drizzle
Are you using WINS? DNS? LMHOST?

In an NT4 domain, name resolution problems can be the cause of a lot of things.

You said XP clients can't resolve a host name. Can 2000 or NT4 Clients resolve hostnames?
More
19 years 7 months ago #5353 by steveb12
FallenZer0 - thanks for the link, but it did not apply. My XP machines can perform pings just fine, it is only name resolution that is not working.

drizzle - yes, clients get their WINS and DNS server information through DHCP. LMHOSTS files are not used. Yes W2K and NT4 clients are able to perform a ping -a and resolve a name just fine.

Any other thoughts? I only have a few XP machines and this is something I can live with. It's just driving me crazy that I can't figure it out.

Thanks all.
More
19 years 7 months ago #5354 by drizzle
Can you post the output of your ping -a xxx.xxx.xxx.xxx? I have tried to recreate your problem with no success. Are you getting an error? Any odd entries in your XP event logs?
More
19 years 7 months ago #5357 by steveb12
Sure thing, but I think it will only serve to frustrate you. Here is the output from an XP machine:

C:\Windows>ping -a 141.158.40.14

Pinging 141.158.40.14 with 32 bytes of data:

Reply from 141.158.40.14: bytes=32 time<1ms TTL=127
Reply from 141.158.40.14: bytes=32 time<1ms TTL=127
Reply from 141.158.40.14: bytes=32 time<1ms TTL=127
Reply from 141.158.40.14: bytes=32 time<1ms TTL=127

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

and here is the output from a machine running W2K:

C:\Windows>ping -a 141.158.40.14

Pinging BAHSPDC [141.158.40.14] with 32 bytes of data:

Reply from 141.158.40.14: bytes=32 time<10ms TTL=127
Reply from 141.158.40.14: bytes=32 time<10ms TTL=127
Reply from 141.158.40.14: bytes=32 time<10ms TTL=127
Reply from 141.158.40.14: bytes=32 time<10ms TTL=127

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

As you can see the name resolves using a W2K machine. I REALLY hope this helps - and thanks.
Time to create page: 0.152 seconds