I don't see where the info provided points to a DNS issue nor is there the
absolute requirement that this DC be a DNS server. Specifics you bring up
are all good but this doesn't mean this has anything to do with the problem
defined.
In the other post from Jorge brings up the running of debug info which could
help provide needed info.
I would do similar to what Jorge has defined:
Try running netdiag, repadmin and dcdiag. Look for fail, error and warning
errors.
If you don't have the tools installed load them from your install disk.
d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)
Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.
@echo off
c:
cd \
cd "program files\support tools"
del c:\dcdiag.log
dcdiag /e /c /v /s
C_Name /f:c:\dcdiag.log
start c:\dcdiag.log
netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log
repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
start c:\repl.txt
See for more details
http://www.microsoft.com/technet/pr...Ref/1d4ce93c-54f2-4069-a708-251509c38837.mspx
--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.