Discussion Locked

2000 can't resolve internal DNS names

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have 65 Windows 2000 client machines. Occassionally they can't resolve internal DNS names. It happens on some machines more than others. For the desktops I use a host file. What can I do for my laptop users?

5 replies

by masteraaron

If you have traveling users and need access to Files on the inside. I recomend a Wins Server and Firewall hardware to provide protection so remote users can VPN into the network. DNS is great if setup properly, but if not a WINS Server does a betterjob.

by tbragsda

I have seen the same thing with my internal NT DNS server, and 2k clients. Dont know what it is yet, but I would love to get any info anyone has.

by abersade

What are your DHCP settings? It sounds like your scope of IP address's might not be big enough for the amount of people signing on at once. Are you Dynamically assigning Ip address's or are they static?

by djent

Have you entered the DNS names in the search order under TCP/IP properties?

This discussion is closed to new replies.