Discussion Locked

Windows 2000 Pro logon to 2000 server

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

I have a 2000 server running AD, DNS etc. I want to use the DNS of my ISP for website name resolution but still need internal DNS because of AD's requirement. NT worksations logon to the domain without any problem.
However, if I try to logon to thedomain (AD)with a 2000 professional workstation, the process takes 15 minutes. If I logon using the local domain, no problem What's wrong?

5 replies

by wcraigmiles

Your ISP's name server is first in the list of DNS servers for the client. NT servers when logging into a server start with WINS.

by wcraigmiles

Install you DNS server. Set it up to support your domain. Set a secondary into that server and in your dhcp settings for your workstation set your DNS server first, the ISPs second. That way your server will resolve for your specific site, but the Internet will not know about it. For addresses and names not specific to your site, your DNS server becomes a caching server. Works very well.

This discussion is closed to new replies.