5719 error, but I check and everything's ok

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Greetings,

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!
 
Have you run the normal diagnostic tools (DCDIAG, NETDIAG, etc.) to see if
they report any issues? When running these tools, ensure you use the verbose
option. One of your challenges may be running the tool when the issue occurs.
If you cannot predict the next occurrence of the issue, you may want to
TEMPORARILY turn on extended logging for NTDS. Remember that this is
something you only want to do on a temporary basis because it will add load
to your servers.
I suggest you turn it on on both servers which are involved in this issue.
Here’s a link to the KB that explains how to turn it on:
http://support.microsoft.com/kb/314980.
 
Just did NET/DC diag, both passed. There was a failure on the modem TAPI
and some print drivers in the system log, but since we turned off the
spooler service and the TAPI stuff that is to be expected. I'm thinking
I'll probably crank up the logging as per the article. I'll need it upped
for about a day. This DC is not a GC so it doesn't get hammered like its
partner, but I still worry about the load on the server for 24 hours.


"JPolicelli [MVP - Directory Services]"
 
I am assuming you talking about NETLOGON EventID 5719 Errors , if you using
W2k3 SP2 have a look at this link http://support.microsoft.com/kb/948496/

- said:
Just did NET/DC diag, both passed. There was a failure on the modem TAPI
and some print drivers in the system log, but since we turned off the
spooler service and the TAPI stuff that is to be expected. I'm thinking
I'll probably crank up the logging as per the article. I'll need it upped
for about a day. This DC is not a GC so it doesn't get hammered like its
partner, but I still worry about the load on the server for 24 hours.


"JPolicelli [MVP - Directory Services]"
Have you run the normal diagnostic tools (DCDIAG, NETDIAG, etc.) to see if
they report any issues? When running these tools, ensure you use the
verbose
option. One of your challenges may be running the tool when the issue
occurs.
If you cannot predict the next occurrence of the issue, you may want to
TEMPORARILY turn on extended logging for NTDS. Remember that this is
something you only want to do on a temporary basis because it will add
load
to your servers.
I suggest you turn it on on both servers which are involved in this issue.
Here's a link to the KB that explains how to turn it on:
http://support.microsoft.com/kb/314980.
Click to expand...
Click to expand...
 
Sorry, I should have clarified, it is 2000

Adrian said:
I am assuming you talking about NETLOGON EventID 5719 Errors , if you using
W2k3 SP2 have a look at this link http://support.microsoft.com/kb/948496/

- said:
Just did NET/DC diag, both passed. There was a failure on the modem TAPI
and some print drivers in the system log, but since we turned off the
spooler service and the TAPI stuff that is to be expected. I'm thinking
I'll probably crank up the logging as per the article. I'll need it
upped
for about a day. This DC is not a GC so it doesn't get hammered like its
partner, but I still worry about the load on the server for 24 hours.


"JPolicelli [MVP - Directory Services]"
message
Have you run the normal diagnostic tools (DCDIAG, NETDIAG, etc.) to see
if
they report any issues? When running these tools, ensure you use the
verbose
option. One of your challenges may be running the tool when the issue
occurs.
If you cannot predict the next occurrence of the issue, you may want to
TEMPORARILY turn on extended logging for NTDS. Remember that this is
something you only want to do on a temporary basis because it will add
load
to your servers.
I suggest you turn it on on both servers which are involved in this
issue.
Here's a link to the KB that explains how to turn it on:
http://support.microsoft.com/kb/314980.


:

Greetings,

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!
Click to expand...
Click to expand...
Click to expand...
 
Sorry, I should have clarified, it is 2000
Click to expand...

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.
 
Back
Top