Event ID - 5783

Event Id5783
SourceNetlogon
DescriptionThe session setup to the Windows NT or Windows 2000 domain controller <DCName.domain_name.com> for the domain <Domain> is not responsive. The current RPC call from Netlogon on <Workstation> to <DCName> has been cancelled.
Event InformationAccording to Microsoft:
If the source server could not locate the server in DNS, troubleshoot Active Directory replication failure due to incorrect DNS configuration. If this is not a DNS problem, troubleshoot RPC problems. For more information see the below given link "Active Directory Operations Overview".

Following information from newsgroup post may help:
"The problem has been resolved by installing service pack 3"
----------------
"DC was not reachable from another DC to which a trust was configured. The real problem was with DNS server due to replication problem with another DNS. From each DC run "nslookup" to check the name resolution is doing well. Corrected replication issue then trust was in place and the problem has resolved"
----------------
"In our case this event appeared in a client system whenever it fails to establish a session with remote server. If the event logs very rarely, you can safely ignore it."
----------------
"This may occur if you have several persistent network connections and you have intermittent network connectivity.
It can also occur if you have a trust between two domains and have network connectivity trouble."
----------------
"It looks like you have an unreliable connection to the DC and this is what you should trouble shoot first, this issue is not different from if you had a stand alone server instead of a cluster node. There is a tool called nltest.exe in the reskit which might help troubleshoot this."
----------------
"Make sure you have; Enabled "NetBIOS over TCP/IP" in the TCP/IP Advanced Settings. Also, If More then one Domain exists, check the Trust relationship between the Domains."
----------------
"Make sure you can ping everything from the exchange server, and use nslookup to check the names and ip address of the DC and globa
Reference LinksResolution
Clients Cannot Join a Domain with Norton Internet Security 2002

Active Directory Operations Overview

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.