• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 254
  • Last Modified:

Dns Issue

Hello,

I am having a DNS issue on 1 single computer. I have about 150 other computes hooked up the same way and nothing is wrong with them.

I am trying to map some drives. The server I am trying to connect to is "Server2003"
If I go \\server2003  it does not find anything "retype the name of the server, check spelling, blah,blah"

If I go 192.168.1.24 it connects and shows all the shared folders and such.

All the network ips and dns ip, and default gateways are the same.

Any help would be great. Thanks

His OS is Windows XP
0
MattBamm
Asked:
MattBamm
1 Solution
 
MattBammAuthor Commented:
All the netowkr IPs, DNS IPs and Default Gateways are correct.. i ment to say.
0
 
MattBammAuthor Commented:
Also forgot to say:

If i ping www.google.com it works fine.  It's just this one server it cannot ping or find anything on.
0
 
MarcusPfeifferCommented:
Perhaps you have a WINS issue. If you check the advanced settings of the IP, you will find a setting for WINS servers. If it is defined to an incorrect or obsolete address, it may have this effect.
0
 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.

 
valheru_mCommented:
Ping server2003 by name.  Does it respond with the proper IP address, incorrect IP address, or no address at all?

Since this is a problem, I'm going to guess it's not the correct IP.  If it resolves to the wrong IP, I would check the machine's hosts file (c:\windows\system32\drivers\etc\hosts) and make sure there isn't an errant entry in the hosts file for server2003.

If you get no DNS resolution at all, you might also try to ping it by the fully qualified name(i.e. server2003.yourdomain.com or whatever) and see if it works that way.  If it works that way and not with just the name alone, you'll just need to set the primary DNS suffix of the workstation.
0
 
enriquecadalsoCommented:
To test DNS function run nslookup and write server2003 [enter].

The DNS server should return you the IP 192.168.1.24. If not paste the message here.
0
 
MattBammAuthor Commented:
Wins ip is correct. (there isnt one) like all the other computers.
-Thanks for the suggestion

If I ping server2003 I get nothing, Please check name and try again.

Everything looks fine in the folder.

If I ping server2003.smdomain.local  I still get nothing.    

0
 
MattBammAuthor Commented:
weird. This is what I am getting

good.JPG
0
 
valheru_mCommented:
I'm assuming that 192.168.1.3 is your correct DNS server, yes?

try nslookup server2003.smdomain.local
0
 
MattBammAuthor Commented:
yes, that is correct.
0
 
valheru_mCommented:
what is the result of that nslookup?
0
 
MattBammAuthor Commented:
this
good1.JPG
0
 
MattBammAuthor Commented:
The domain that they use is "apc.local"

We have a second domain "smdomain.local"

we never had any issue on being connected to both domains.

0
 
valheru_mCommented:
and those same nslookup commands return positive results on other workstations with the same settings?
0
 
MattBammAuthor Commented:
Getting same message, but they can actully connect to the folders, and the drives, and able to map their drive letters to their machine.
0
 
valheru_mCommented:
If you're getting the same message on other machines, it means that the internal DNS structure isn't responding correctly to DNS requests for server2003.smdomain.local.  As a permanent solution you may want to check out the DNS server and figure out if the correct DNS records exist for that server in that domain.

Windows machines have several ways to resolve names to IPs, one of which is just a netbios broadcast.  Since you dont use WINS and DNS isn't working, I'm guessing that this is probably how the other machines are resolving the name, and that there may be a netbios problem on this workstation preventing it from doing the same.

The permanent solution to this problem is figuring out why your DNS servers aren't responding. For a quick temporary solution while you're working that problem out, you can add a hosts entry on that workstation. Open c:\windows\system32\drivers\etc\hosts and add an entry like this:

192.168.1.24    server2003

save the file and then try the ping/map drives by name, etc.
0
 
valheru_mCommented:
just make sure that you remove that hosts entry after you figure out your DNS issues. Hosts entries can cause you problems later down the road if you decide to change the Ip address of a server and still have old hosts entries on your workstations that point to the old IP address.
0
 
MattBammAuthor Commented:
Ill give this a try, I will have to do it in an hour or so, heading into a meeting.
I will keep you updated.

THANK YOU SO MUCH FOR YOUR HELP!

0
 
valheru_mCommented:
Also, I just saw your post above about also using apc.local.  Try:

ping server2003.apc.local

Does that work?
0
 
MattBammAuthor Commented:
no, it would'nt because server2003 is on the smdomain.

should be server2003.smdomain.local
0
 
valheru_mCommented:
k, just making sure other workstations weren't resolving it via that domain.
0
 
MattBammAuthor Commented:
The guy comes back tomorrow from out of town, ill get you updated on this hopefully soon.

-Matt
0
 
valheru_mCommented:
Any progress on this?
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

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