Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 701
  • Last Modified:

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

I have a user on an XP box who lost his mapping to a drive on a remote server (windows 2000).  I cannot ping or map using the server name, but I can ping and map using the IP address.  Could this be a DNS problem?  The DNS server is at our site.
0
JoMar
Asked:
JoMar
  • 2
  • 2
  • 2
  • +2
2 Solutions
 
whermansCommented:
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.
0
 
pab006Commented:
Is the box xp pro or xp home?

cheers

Paul
0
 
NewsboyCommented:
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.
0
New Tabletop Appliances Blow Competitors Away!

WatchGuard’s new T15, T35 and T55 tabletop UTMs provide the highest-performing security inspection in their class, allowing users at small offices, home offices and distributed enterprises to experience blazing-fast Internet speeds without sacrificing enterprise-grade security.

 
JoMarAuthor Commented:
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
0
 
NewsboyCommented:
Sorry the command is IPCONFIG /flushdns my bad, that's what happens when you go off of memory. Is this a domain? Is the Remote server a member server or another DC? It sounds as though your DNS isn't synchronizing between servers. You could set up a forwarder from your local server to the remote server. Have you tried nslookup from your local server to the remote server? If it works then your local server isn't forwarding on DNS requests.
0
 
knightrider2k2Commented:
Add the server name and ip address to hosts file.
0
 
whermansCommented:
JoMar,

Go to another client machine, do ipconfig /flushdns in a dos box and try nslookup again.  If you get a reply from your own server, the problem is on that client only.  If you get an error on that other client too, suspect your DNS server.

Can you do a ipconfig /all on the not-working client and a working client and paste both outputs here?
0
 
JoMarAuthor Commented:
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
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 2
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now