General discussion

Locked

Windows 2000 Pro logon to 2000 server

By pokarma ·
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?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Windows 2000 Pro logon to 2000 server

by wcraigmiles In reply to Windows 2000 Pro logon to ...

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.

Collapse -

Windows 2000 Pro logon to 2000 server

by pokarma In reply to Windows 2000 Pro logon to ...

Poster rated this answer

Collapse -

Windows 2000 Pro logon to 2000 server

by wcraigmiles In reply to Windows 2000 Pro logon to ...

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.

Collapse -

Windows 2000 Pro logon to 2000 server

by pokarma In reply to Windows 2000 Pro logon to ...

Poster rated this answer

Collapse -

Windows 2000 Pro logon to 2000 server

by pokarma In reply to Windows 2000 Pro logon to ...

This question was closed by the author

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums