Windows Forum

Ask something
Discussion Locked

W2K and DNS

0 helpful
4 replies

by ratherbfishing 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a mixed network including NT 4.0 Domain, and some UNIX and LINUX servers. We are running an internal DNS server (BIND 8.1.2) on a LINUX box to resolve internal hosts. We also run WINS for the NT domain.

I recently added some W2K Pro machines, and for some reason they are unable to resolve names via DNS. FOr example, I cannot ping by name any of the UNIX or LINUX boxes. I can do this with the Win 4.0 workstations just fine. Even more interesting, if I run nslookup from the W2K box, itdoes find the DNS server and resolve the names.

THis is a pain because I am having to tell our W2K users to use IP addresses instead of names for our UNIX host connectivity, sendmail connections, and Intranet server http addresses.

Does anyonewhy Win 2000 is not resolving names via our DNS server, when NT 4.0 uses it just fine?

THanks!

4 replies

by calves

I wonder if the DNS servers are given to the Win2K by DHCP or if they are inserted into the TCPIP settings for the Win2K.
To insert it manually, right click on My network places (desktop), right click on the LAN icon, TCPIP properties, DNS, and there is a whole bunch of configurations you can play with.
That could resolve it for you.

Good luck!

by soren.albeck

You probably set the domain-name (DNS-suffix) using DHCP. Win2K appears to not use that. Either add it manually as answer 1 suggested or edit the local group policy (open Run, type gpedit.msc) and go to Computer configuration, Admin. templates, System, DNS settings and enable the policy 'primary DNS suffix' and enter the appropriate domain-name and you should be good to go. Reboot to make the policy take hold immediately.

by ratherbfishing

DNS added Manually. Your suggestion about hte DNS suffix did not work, but led me in the right direction.

Apparently W2K handles DNS suffixes differently then NT 4 clients. To fix the problem I went into DNS advanced properties, selected "Append these DNS suffixes" and added our internal domain name suffix, e.g., ourdomain.org. I also added the "DNS suffix for this connection."

This discussion is closed to new replies.