xp client can't map or ping using server name, but can with server IP address

Try if the client can talk to your internal DNS, and if not, to an external one:

c:\>nslookup
> server = <ip internal dns server>
><servername>
> server = <ip external dns server>
>google.com

The 'server'-command changes the active nameserver which you query with nslookup.

Is the box xp pro or xp home?

cheers

Paul

Yes it's a DNS problem do an IPCONFIG /dnsflush, then IPCONFIG /release, then IPCONFIG /renew. This should clear all DNS records and then force the computer to try and re-pickup it's DNS from the Server. Of course you need to check and make sure that the DNS server is setup as the DNS server on the client.

when i do an nslookup - it comes back with:
can't find servername for address (IP) non-existant domain
default servers are not available
default server: unknown
address (IP)

I went to network connections and changed the DNS server to one at the remote site and nslookup worked fine, i could ping and map to the server in the remote location.  I changed it back to the server onsite and got the same message as above with nslookup, and couldn't ping or map by name.

The OS is XP Pro on the client and Windows 2003 on the remote server and the server here (where the primary DNS is).

Newsboy,
When you say do an ipconfig /dnsflush, is that on the client or the server.  I tried it on the client and it wouldn't do anything.

Thank you all for your help.

John

Add the server name and ip address to hosts file.

After doing what whermans and newsboy suggested, and tracking down the DNS problems, I realized it was a replication problem on the domain controller in the remote network.  The DC is running out of space and that was the problem.

Thanks again.

JoMar