I have one DC in my domain that is complaining about once a day that it
can't find a DC in my counterpart's domain. In my domain it's just this one
domain controller that's complaining but I don't see why it is saying that.
I check and I can ping domain 2, and I can target domain 2 when opening any
of the snapins. Is there a way I can crank up the logging to see
specifically what it's complaining about?
Thanks!
"JPolicelli [MVP - Directory Services]"
<JPolicelliMVPDi...@discussions.microsoft.com> wrote in message
news:2A911B25-4C3E-4CDC...@microsoft.com...
"Adrian" <Adr...@discussions.microsoft.com> wrote in message
news:9B3489A5-E6D4-4D8A...@microsoft.com...
If you've already enabled NTDS logging as JPolicelli suggested, you should
be getting some events. If you have, are you seeing any errors?
Also, EventId 5719, depending on your operating system (2000) and service
pack level (?), can be caused by a host of issues, from simply something as
using an incorrect DNS server in IP properties that doesn't host the AD
zone, such as your ISP's DNS address. That can cause numerous other
problems, including RPC errors, authentication failures, etc. A Multihomed
DC (more than one NIC) can cause this as well. With Windows 2000, there was
a known issue that got fixed in SP3.
Take a look at the various comments and see which one applies to your
scenario:
http://eventid.net/display.asp?eventid=5719&eventno=104&source=NETLOGON&phase=1
Also, please post an unedited ipconfig /all from the DC. This will help get
a better understand of how the DC is configured.
Thanks,
--
Ace
This posting is a personal opinion based on experience, and is provided
"AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.