Retrying Netlogon logon on a new connection

Logged when a netlogon backend could not send a logon request to the domain controller at endpoint, so it retries the request once on a new connection. This happens when a pooled connection was already closed, for example by a firewall or NAT device after a period without traffic, after the domain controller restarted, or after TCP keepalive found that the domain controller stopped answering. It also happens when another request set up a new secure channel while this request waited. The error field shows the cause.

A request that was sent is never retried, even if the connection closes before the response arrives, because the domain controller may already have processed the logon. Such a request fails with an error.

No action when this happens occasionally. If it repeats often, check idle timeouts on firewalls and NAT devices between Radiator and the domain controller, and the backend keepalive settings.