This problem first came to my attention when attempting to add a new user to our domain. Ours is a single domain consisting of 4 2003 servers (domain controller/file/print, SQL, Exchange 2003, and a Terminal Server). When creating the user a dialogue box indicates that the GC is un-contactable.
After some research I attempted to manually set the GC in exchange, the process started a search with the default location of "Entire Directory" (no option at this point for just the domain)which failed to locate our DC/GC. Following up, I attempted to find objects using the ADUC console (any of the servers other than the DC). Using the domain in the locations field of the Find utility works for all objects, using the Entire Directory location option fails for all objects. On my XP pro workstation using the following run command "rundll32.exe dsquery,OpenQueryWindow" or in ADUC on the DC I have no problems locating objects at all.
We have had recent DNS problems with the local forward lookup zone recreated - not using active directory and set as primary. If as I suspect it is a DNS related issue what is my next step to resolve?
DNS Setup - primary, not using active directory, set to use the ISP DNS for Internet access. Servers are manually set with IP address, gateway and DNS (Local DC). Workstations are using DHCP with an additional secondary DNS included – the ISP DNS server. This secondary was configured temporarily resolve a DNS/Browsing issue several weeks ago and not as yet reversed. To resolve that problem the Forward lookup zone was deleted and recreated.