Windows Forum

Ask something
Discussion Locked

Can't see 2nd D.C. in Active Directory

0 helpful
5 replies

by hungurr

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Hi, everyone!!! I have this nagging issue. I'm planning to migrate users from one Windows 2000 domain controller to another Windows 2000 domain controller. I have one Windows 2000 domain called ABC with two Windows 2000 domain controllers, X and Y, separated by a WAN link. I have Active Directoy and DNS set-up on both domain controllers. The problem is that I can find the other domain controller if I am at either location using 'Find Computers', but I can't see the other domain controller(if I'm at one location), or its workstations, in either My Network Places or Active Directory Users and Computers. I can ping either domain controller using an IP address, but I can't ping its DNS name. Using 'Find Computers', I can input either domain controller's IP address, or its DNS name, and it is found. I suspect that this is somehow a DNS problem. What do I need to set-up in DNS(additional records,etc.) to allow both domain controllers to see each other? By the way, I used the automatic DNS wizard when I set up Active Directory on each domain controller. Is there more I need to configure? Any help is greatly appreciated.

5 replies

by quintar51

It's definitely a DNS issue when you can ping by IP, but not by name. What kind of zones are you running on the Domain Controllers? Standard Primary or AD Integrated? If you right-click on a zone and go to properties, you can determined what zonetype it is. I would make both zones AD Integrated and allow secure dynamic updates. Make sure the record for the DC in question appears in both records.

good luck,

by henrywi

You have a pure Windows 2000 network and are certain that all computers and applications on your network can function using another naming service, such as DNS. Network naming is a vital service for locating computers and resources throughout your network, even where NetBIOS names are not required.
The Windows 2000 WINS client caches resolved names locally and uses a component called the Caching Resolver to look in the cache before submitting a query to DNS. The HOST file is cached as soon asthe client starts running, and any updates to the HOST file are reflected immediately in the cache. The name resolution sequence is as follows:

Client attempts name resolution from the client cache.
If resolution from the client cache fails, the client attempts name resolution through DNS.
If DNS name resolution fails, the client attempts resolution through WINS

by hungurr

Thanks for the answers. Since I installed Active Directory on each server individually in the lab first, Active Directory, I guess, configured each machine as the only domain controller in the domain. So, I re-installed Active Directory on one of the domain controllers at its permanent location and everything was proprogated between the two domain controllers. Everything is fine now.

This discussion is closed to new replies.