Netlogon Event ID 5719: This Computer Was Not Able to Set Up a Secure Session with a Domain Controller

Netlogon event 5719 explained: when it is safe to ignore (startup, Windows Server 2025 restarts), and how to fix DC discovery with nltest /dsgetdc, DNS and port checks, Netlogon service and RPC backlog fixes.

Home › Guides › Netlogon event 5719

Last updated 18 November 2026

Quick answer

Event 5719 (source NETLOGON, System log) means the computer could not set up its secure channel to a domain controller. The text after due to the following: tells you why. Microsoft documents two harmless cases; everything else needs fixing:

nltest /dsgetdc:<DomainName> /force /kdc

If it fails, check firewalls for UDP 389 (LDAP) and UDP 53 (DNS), then the computer's DNS settings, as described below.

The reasons you'll see in the event

The event reads This computer was not able to set up a secure session with a domain controller in domain <Domain Name> due to the following: followed by one of these (all from Microsoft Learn examples):

Reason textWhere Microsoft documents it
The remote procedure call failed and did not execute.The Netlogon RPC backlog article (with event 3210 and Kerberos event 7).
The remote procedure call was cancelled.The SQL Server login failed (18456) article, where the DC couldn't be contacted.
We can't sign you in with this credential because your domain isn't available.Netlogon service startup failures, when all reachable DCs have their Netlogon services stopped.
An internal error occurred. (0xC00000E5)Windows Server 2025 members talking to older DCs when NetLogon restarts.

In netlogon.log the startup case shows up as Eventlog: 5719 (1)"<domain>" 0xc000005e. 0xC000005E is STATUS_NO_LOGON_SERVERS, which [MS-ERREF] describes as No logon servers are currently available to service the logon request. Look up 5719, 3210 and the other IDs here in the Windows Event ID Lookup.

Which DC the computer talks to: Microsoft notes that a domain controller sets up its secure session with the PDC emulator of the specified domain; any other computer sets it up with any DC in the domain.

Case 1: 5719 at startup (network not ready)

On Windows 8.1 and earlier the event is logged at startup. In Windows 10 and later, Microsoft says event 5719 is no longer logged in this situation; netlogon.log records it instead:

[CRITICAL] [960] CONTOSO: NlSessionSetup: Session setup: cannot pick trusted DC
[SESSION] [960] No IP addresses present, skipping No DC event log

On those versions you see the failure in components that need a DC at startup, such as Group Policy (event 1129). Microsoft's causes:

Microsoft's fixes, first one first:

  1. Install the current driver for the Gigabit network adapter, or enable PortFast on the switch ports. ipconfig /all shows the adapter's Physical Address; the MAC Vendor Lookup tells you which vendor's driver to look for.
  2. Adjust firewall or IPsec policies so DC traffic is allowed as soon as the client has an address (for example after Cisco NAC or Microsoft NPS checks).
  3. ExpectedDialupDelay (REG_DWORD, seconds, default 0, range 0 to 600) under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters. Only effective if the machine already has an IP address.
  4. ArpRetryCount set to 1 under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TcpIp\Parameters\ (range 0 to 3, default 3) to shorten the address uniqueness wait.
  5. Lower NegativeCachePeriod under the Netlogon Parameters key so Netlogon doesn't treat the DCs as offline for 45 seconds. Microsoft suggests a low value such as three seconds, or 0 on a LAN to turn the negative cache off. Event 5719 is still logged, but without other significant problems.
  6. Group Policy settings under Computer Configuration\Administrative Templates\System\Group Policy: Specify startup policy processing wait time (corporate LAN or WLAN) or Specify workplace connectivity wait time for policy processing (external).
  7. Or the GpNetworkStartTimeoutPolicyValue DWORD (decimal 60) under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon; increase it if the startup script still doesn't run.

Back up the registry before you change it; Microsoft warns that incorrect changes can cause serious problems.

Case 2: Windows Server 2025 and 0xC00000E5

Member serverAuthenticating DCResult (Microsoft)
Windows Server 2025Windows Server 2025No event 5719
Windows Server 2025Windows Server 2022Event 5719, 0xC00000E5
Windows Server 2025Windows Server 2019Event 5719, 0xC00000E5

The 2025 member tries the new Kerberos-based secure channel first, the older DC doesn't support that RPC call, and Windows falls back to NetLogon. The Security-NetLogon Operational log shows event 9005: Secure channel setup has failed with Kerberos: An internal error occurred. Falling back to NetLogon. Microsoft says not to remediate unless you see persistent authentication or secure channel problems. As an optional, temporary workaround until enough Kerberos-capable DCs are deployed, it documents:

reg add "HKLM\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters" /v UseKerberosForSecureChannels /t REG_DWORD /d 0 /f

Remove it once the domain is updated.

Case 3: the computer can't find a domain controller

Microsoft's usual causes are blocked ports between the client and the DC, a wrong DNS configuration on the client, or a wrong DNS server configuration on the DC. Its steps:

  1. Check every firewall between the client, the DC and the target server (including Windows Firewall) for UDP 389 and UDP 53.
  2. Run nltest /dsgetdc:<DomainName> /force /kdc. It returns one or more available DCs, or an error if none can be contacted.
  3. Run nslookup <TargetName>. If it fails, run ipconfig /all and check the client IP address, subnet mask, default gateway, connection-specific DNS suffix and DNS server addresses. Check the client's address and mask against the DC subnet with the IPv4 Subnet Calculator (or the IPv6 Subnet Calculator).
  4. Fix what's wrong and run nltest again. If it still finds no DC, Microsoft points to a larger network or Active Directory issue.

Microsoft's Netlogon service startup article lists what fails when the Netlogon service isn't started: nltest /sc_query:litware.com returns I_NetLogonControl failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE, net use returns System error 1792 has occurred, the DC locator fails with error 1355, and if all reachable DCs have Netlogon stopped, members log 5719 with your domain isn't available. Check the service and its dependencies with sc qc netlogon; Netlogon depends on the Workstation service (and on DCs also the Server service). A DC whose Netlogon service is paused doesn't answer DC locator requests on UDP 389; one cause Microsoft lists is SysVol not ready in netlogon.log, when DFSR initial replication of SYSVOL hasn't completed.

Case 4: busy DCs and the RPC backlog

When 5719 says The remote procedure call failed and did not execute together with frequent TCP resets, intermittent 401 errors from Exchange or repeated Outlook credential prompts, Microsoft points to the RPC backlog limit on the DC. The default is 10; when it is exceeded the RPC layer resets TCP SYN packets. Microsoft's Netlogon value is DcTcpipBacklogLimit (REG_DWORD, 10 to 100) under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters; restart Netlogon (and possibly the DC). Large values use more non-paged pool memory. After the June 2022 preview updates Netlogon logs event 5836 when it binds with the configured backlog size and 5837 when that fails.

Collect the data

wevtutil qe System "/q:*[System[(EventID=5719)]]" /f:text /c:50
nltest /dbflag:0x2080ffff
nltest /dbflag:0x0

The first command lists the last 5719 events; the second turns on Netlogon debug logging to %systemroot%\debug\NetLogon.log; the third turns it off. In PowerShell: Get-WinEvent -FilterHashtable @{LogName='System'; Id=5719} -MaxEvents 50. To see or switch the DC a computer uses, Microsoft's SQL Server article uses NLTEST /SC_QUERY:CONTOSO and NLTEST /SC_RESET:CONTOSO\DC03. Search a long NetLogon.log for NlSessionSetup or NlDiscoverDc lines with a pattern from the Regex Tester.

Related tools and guides

Look up 5719, 3210, 1129 and 9005 in the Windows Event ID Lookup, keep the Get-WinEvent query in the PowerShell Cheat Sheet, check a client address against the DC subnet with the IPv4 Subnet Calculator and test NetLogon.log search patterns in the Regex Tester. Related guides: the trust relationship between this workstation and the primary domain failed, Group Policy events 1058 and 1030 and KRB_AP_ERR_MODIFIED.

FAQ

What does Netlogon event 5719 mean?

The computer could not set up its secure channel to a domain controller in its domain. The text after due to the following gives the reason, such as the remote procedure call failed, the domain isn't available, or an internal error (0xC00000E5).

Can I ignore event 5719 at startup?

Microsoft says yes if you can sign in to the domain without a problem. Netlogon may start before the network is ready, logs 5719, and then finds a DC once the network is up. On Windows 10 and later this startup case is written to netlogon.log instead of the System log.

Why does Windows Server 2025 log 5719 with 0xC00000E5?

A Windows Server 2025 member first tries the new Kerberos-based secure channel. Windows Server 2022 and 2019 DCs don't support it, so it fails once and falls back to NetLogon. Microsoft calls this expected and harmless when it happens only at NetLogon restarts.

How do I test whether a computer can find a domain controller?

Run nltest /dsgetdc:DomainName /force /kdc from an elevated prompt. If it returns no DC, check firewalls for UDP 389 and UDP 53, run nslookup for the target server and check the DNS servers in ipconfig /all.

How do I turn on Netlogon debug logging?

Run nltest /dbflag:0x2080ffff. Windows writes the log to %systemroot%\debug\NetLogon.log. Run nltest /dbflag:0x0 to turn it off again.

Want the full kit?

Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.