Netlogon 5719 and the Disappearing Domain [Controller]

re: Netlogon 5719 and the Disappearing Domain [Controller]

Ingolfur Arnar Stangeland — Thu, 03 Dec 2009 07:40:36 GMT

Another typical error message which is usually network-related (DNS or transport):

"The specified domain either does not exist or could not be contacted."

re: Netlogon 5719 and the Disappearing Domain [Controller]

Ingolfur Arnar Stangeland — Mon, 22 Jun 2009 11:56:18 GMT

See the following for a W2k8 hotfix concerning port exhaustion (which generates a Netlogon 5719 event)

http://support.microsoft.com/?id=959816

re: Netlogon 5719 and the Disappearing Domain [Controller]

Ingolfur Arnar Stangeland — Tue, 09 Dec 2008 13:11:05 GMT

The laptops are telling you they can't reach a DC to authenticate against which points to the network they're using not being ready at the time when it is logged.

In general, isolating a common factor between the affected machines should help. A second recommended factor is to simplify the troubleshooting scenario as much as possible (uninstall anything non-critical from one of the machines that you use to test).

You have identified the laptops as having the problem while wired clients do not so you need to figure out the common factor between the laptops.

An interesting test would be to disable the WLAN card on the laptops, connect them to the LAN and see if you have the same event being logged.

Another factor to identify is *when* you're seeing the event, if it's only at startup or resume then it's not uncommon as the network switch may not be ready when you enter your credentials.

The important bit is that the event is not a problem in itself....it's just an indicator that you don't have network connectivity when it is logged. That in turn may cause other problems.

You should however not look at Netlogon 5719 and try to find problems related to it, you should look at any problem you have and Netlogon 5719 might be an additional symptom of it.

re: Netlogon 5719 and the Disappearing Domain [Controller]

daniel danhäuser — Thu, 27 Nov 2008 23:37:54 GMT

hi,

we have similar events in our network environment. the interessting thing is that only laptop users are affected and getting event 5179 or 40960 or 40961. desktop users have no problems.

your links are very helpful.