Windows 2008 R2 Server logon failure check

[dlukinski]

Hello XI support

How to monitor Windows 2008 R2 for "no logon servers available" condition?
- what is the best way?
- is there check or plug for that?

Thank you

[rkennedy]

Would a ping check suffice? When you try to login to a domain, and if it can't reach an AD server - it'll say "no logon servers available".

Otherwise, what port do your client computers use to authenticate to your AD server?

[dlukinski]

Would a ping check suffice? When you try to login to a domain, and if it can't reach an AD server - it'll say "no logon servers available".

Otherwise, what port do your client computers use to authenticate to your AD server?

PING would not be something to possibly consider.

This is the circumstance where remote desktop servers (Citrix or Otherwise) are unable to login clients.
Not because DC is unavailable on a network, but rather due to some event or service/process issues I was hoping you dealt with in the past

[rkennedy]

I think ping would work fine, as this error in particular is relating to a network error.

Alternatively, we can check the port that the clients are using to connect to the server. What port do client computers use to authenticate to your AD server?

[dlukinski]

I think ping would work fine, as this error in particular is relating to a network error.

Alternatively, we can check the port that the clients are using to connect to the server. What port do client computers use to authenticate to your AD server?

Nope (this is not the ping), this is strictly a "microsoft thing" around "terminal/desktop sessions on Windows 2003/2008/2012". Not related to AD or netlogon failures on domain controllers.
Again was wondering if there were people before me asking about the same thing

Not ping, not netlogon (or workstation) services running on the affected server, not terminal/RDs/citrix service either (none of them are hanging during this problem)
- somehow MS is unable to pinpoint the root condition so that we could easily monitor for that. Questionable EventIDs is one of the last resorts if nothing else.

[Box293]

I suggest Nagios Log Server.

Have a look at this guide, it shows you how you can receive Windows Event Logs and then alert based on specific text:

https://labs.nagios.com/2015/08/10/moni ... ver-final/

[dlukinski]

Thank you Troy

Was hoping for the quick hack, but if none, we'll settle for Windows Events

Please close this thread