Best Way To Resolve Exchange 2010 Netlogon Event ID 5783
August 26, 2021
Table of Contents
This blog post describes some of the possible causes that might trigger event ID 5783 of the netlogon exchange 2010 event, and then presents possible fixes that you can try to resolve the issue.
Recommended: ASR Pro
Question
We have the best homestead, one forest and a great location. I recently upgraded my domain controllers to Server 2008 R2. This year we also only have one standard Exchange server on R2.
DC1 – 192.168.0.2
DC2 – 192.168.0.3
Exchange – 192.168.0.4I got one of the following Exchange errors over the weekend:
Protocol name: Â Â Â Â Â System
Source: NETLOGON
Date: 08/10/2012 13:54:15 PMEvent ID: 5783
Task category: none
Level: Â Â Â Â Â Â Â Â Error
Keywords: classic
User: Â Â Â Â Â Â Â EXCHANGE N / A
Computer: .Fellowship.local
Description:
Session configuration for Windows NT or Windows 2000 domain DC1 controller.Domain.local actual for DOMAIN domain is not responding. The current RPC calls everything from On netlogon EXCHANGE to DC1.Domain.local. the offer was canceled.
XML events:
Â
   Name = “NETLOGON” />
  Â5783
  Â2
  Â0
  Â0x800000000000000
  Â
  Â63761
 ÂSystem
  ÂEXCHANGE.Fellowship.local
  Â
Â
  Â
 FCDC1.Fellowship. COOPERATION
  local
   EXCHANGE
ÂRecommended: ASR Pro
Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for ASR Pro is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download ASR Pro today!
- 1. Download and install ASR Pro
- 2. Open the program and click "Scan"
- 3. Click "Repair" to start the repair process
I’m not allowed to see anything affected by this issue yet. There is some doubt, however, as setting it up correctly seems like a huge mistake. Is there anything I can check or will it cause other problems in the future?
Thank you in advance.
The Answers
Hello
This is a DNS type problem for me. More information on individual error messages: http://technet.microsoft.com/en-us/library/bb727055.You aspx
Now that there are two domain controllers, do the following:
- Make sure both domain controllers are DNS with GC servers.
- Make sure both domain controllers are using ONLY the same IP address and ONLY ONE specific network is enabled Your adapter (all others must be disabled)
- Make the DC the most valuable DNS server at any time, using its private IP address as secondary and 127.0.0.1 as the third.
- Add the public DNS server as a PASSENGER both to the DC and NOT in the IP settings
When done, try ipconfig / registerdns and restart netlogon on the same domain controller you have. Also check your entire DNS system and remove ALL old DNS records for domain controllers.
For Exchange sites, ensure that the primary domain controller and secondary DNS server are down. Publication
this is provided “AS IS” and does not contain any warranties or rights. Â Â Â
Microsoft Student Partner 2010/2011
Microsoft Certified Professional
Microsoft Certified System Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2010 Active Directory Configuring
Microsoft Certified Technology Specialist: Windows Server 2008 Networking Infrastructure,customization
Microsoft Certified Technology Specialist: Infrastructure and Configuring Windows Server Applications
Microsoft Certified Technology Specialist: Windows 7 Customization
Microsoft Certified Technology Specialist: Design and Deploy Volume Licensing Solutions for Large Enterprises
Microsoft Certified Information Technology Specialist: Company Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Instructor- Proposed As Answer VenkatSP Sunday, August 12, 2012 2:45 PM
- Marked as Formula by User Laurent, August 27, 2012 3:14 am
You can accept this error (event id 5783) if probing usually occurslema with a network connection, or if this DNS server cannot access, this firewall sees and blocks DNS requests. Department, if an error occurs, please Check the DNS settings on the Exchange server and also check if replication between domain controllers is working properly besides publishing the same.
For more information on event tips, follow the link below.
Event ID: 5783 Source: NETLOGON
http://www.eventid.net/display.asp?eventid=5783&eventno=1024&source=NETLOGON&phase=1
http://www.chicagotech.net/troubleshooting/evenid5783.htmYou can see from your comment that the error is gone, so everyone can ignore it as it might be due to a network connectivity issue. This
Hope helps
Sincerely
Sandesh Dubey.
MCSE | MCSA: Messaging | MCTS | MCITP: Company Administrator | Ereignis Id 5783 Netlogon Austausch 2010
Id Evento 5783 Scambio Netlogon 2010
Evenement Id 5783 Netlogon Exchange 2010
Id D Evenement 5783 Echange Netlogon 2010
Handelse Id 5783 Netlogon Utbyte 2010
Sobytie S Identifikatorom 5783 Netlogon Exchange 2010
Id Do Evento 5783 Netlogon Exchange 2010
Id De Evento 5783 Netlogon Exchange 2010
이벤트 Id 5783 Netlogon Exchange 2010
Id Zdarzenia 5783 Wymiana Netlogon 2010
