jfilmore3
asked on
DNS not working on 2003 server
I came in this morning and noticed our windows 2003 server isn't working correctly. All clients are windows XP Pro. When trying to ping server or workstations by name, it hangs about 10 seconds, then get ping reply. When connecting to server and other PC's via IP, there is no issue. I think maybe the server powered down improperly due to a power related issue. I tried typical things (rebooting server, restarting DNS, etc)
Please Help
Please Help
Is the W2003 server running the internal DNS service, too?
Is this a Domain ?
Have you tried te support tools
netdiag
and DCDIAG ( if a Domian controller )
I hope this helps !
Have you tried te support tools
netdiag
and DCDIAG ( if a Domian controller )
I hope this helps !
Ensure that the internal clients and server *only* use the internal DNS server for direct DNS resolving. Never use external/ISP DNS server for direct resolving, instead configure internal DNS server to use forwarders to forward unresolved queries to ISP's DNS server.
Let me get this straight:
You pinged by servername:
Ping servername
Ping is a multi-communications protocol diagnostic utility. If you pinged by servername, you are actually doing a netbios ping, not a DNS ping. This often deceives folks into troubleshooting DNS
Try this:
Ping Servername.fully.qualified .domain.na me
Or
NSlookup Servername.domain.name
If you have no problems with the fully qualified domain name, we might consider troubleshooting Netbios rather than DNS.
You pinged by servername:
Ping servername
Ping is a multi-communications protocol diagnostic utility. If you pinged by servername, you are actually doing a netbios ping, not a DNS ping. This often deceives folks into troubleshooting DNS
Try this:
Ping Servername.fully.qualified
Or
NSlookup Servername.domain.name
If you have no problems with the fully qualified domain name, we might consider troubleshooting Netbios rather than DNS.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.