DNS on AD-server refuse one single client

[Martin Rådbo]

I've got a strange problem for one of our customers. It is a very small
network with one single Win2k-server (domain controller and DNS-server as it
should be).
8 clients with different operating systems use the server, some of the
clients are member of the domain, som are not.

The dns resolving works great for all of them. But one client (its a
TabletPC) has problem. When using the server as dns-server no dns-resolving
is made, it is like the dns server would be down (it is not since all other
clients works fine).
Changing the TablePC-client to use an external dns (for example at the ISP)
works fine.

Any idéa?

Thanks in advance.

// Martin Rådbo
Teknologia

 

[Herb Martin]

I've got a strange problem for one of our customers. It is a very small
network with one single Win2k-server (domain controller and DNS-server as it
should be).
8 clients with different operating systems use the server, some of the
clients are member of the domain, som are not.

DNS is not domain or operating system specific (except
for secure dynamic UPDATES).

Have you tried explicit resolution from the command line
using the IP of the "problem" DNS server?

(I assume that the table has NSLookup and a command
line <grin> -- you can also download tools like nslookup
or dig.)

nslookup SOME_RECORD IP.of.DNS.Server

Try this against the problem DNS and a known
working one (like the ISP).

If there is a difference, then try "pinging" the
problem DC (or tracert) to check routing
between the two machines.

If that doesn't work try posting the "IPconfig /all"
from both the problem client and the DNS server.