DNS resolver does not work

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Ib Tornøe <itk@xxxxxxxxxxxx>
Date: Thu, 7 Sep 2006 17:30:33 +0200

Hi
I have a W2K3SP1 server where the DNS resolver does not work.
Symptoms
- PING <IP address> .... This works
- PING name.domain.com ..... This does not work. I have installed WireShark on the server and nothing is coming out of the interface.
- Configure e.g. name.domain.com in the HOST file loads the name in cache, BUT still using PING name.domain.com does not work.. still nothing is coming out of the NIC
- Using NSLOOKUP... Everything works just fine.

It seems that the DNS Name resolution is disabled.

Any suggestions

TIA
Ib

.

Follow-Ups:
- Re: DNS resolver does not work
  - From: Robert L [MVP - Networking]

Prev by Date: Routing with WinXP
Next by Date: Re: IP Problem
Previous by thread: Routing with WinXP
Next by thread: Re: DNS resolver does not work
Index(es):
- Date
- Thread

Relevant Pages

Re: DNS resolver does not work
... We found the cause for this problem - it had to do with the way they install the server. ... I get the same answer as I do with a PING 10.1.1.1 - It does not do reverse ... It seems that the whole DNS resolver is just disabled. ... Stopping the DNS Client just disables the caching. ...
(microsoft.public.windows.server.networking)
Re: RDP can not logon error
... Tracert & Ping to dc on the same subnet as the server that is having trouble. ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
(microsoft.public.windows.server.general)
Re: Cannot connect to Server
... Test 1 - the clients can ping one anotehr ... gpupdate/force - reboot both client and server - ping to server from client ... Suggestion 2 - ping to server works when running safe mode with networking ...
(microsoft.public.windows.server.sbs)
Re: The specified network name is nolonger available
... My server is named FS1. ... > ping \\fs1 and I will get a successful return. ... I still can access the drives marked ... What is the point in these permissions as they can be bypassed by mapping ...
(microsoft.public.win2000.networking)
Re: RDP can not logon error
... ping and tracert to the dc in that remote site (where this system ... Tracert & Ping to dc on the same subnet as the server that is having ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
(microsoft.public.windows.server.general)