Failed logons
The Failed logons dialog reads the Security event log of a server and lists every failed logon (event ID 4625). Use it to spot brute-force attempts or to see why an account got locked out.

How to open it
- Right-click a server on the Servers list and choose Administration > Failed logons to see every failed logon on the server in the chosen period.
- Right-click a user on the User sessions list and choose Failed logons to see only that user's failures.
The dialog is titled Failed logons - <server>, or Failed logons - <user>@<server>.
Time range
The toolbar is the same as in Session history: a Period dropdown, From and To dates, and Fetch. This dialog opens on Today the first time and remembers your last choice.
Columns
- Event - Logon failed.
- Time Created - when the event was recorded.
- User - the account that failed to log on.
- Address - the source address, when the event has one.
- Failure Reason - a description built from the event's
StatusandSubStatuscodes, followed by the status code in hex. Examples: Unknown user name or bad password, User logon with account locked, User logon with expired account, User logon outside authorized hours, User logon from unauthorized workstation.
Filter by user
The User field (placeholder Filter by user (e.g. admin*)) filters the log when you press Enter or click Fetch. Without wildcards it matches the whole user name, with or without the domain: jsmith and CORP\jsmith find the same events. A * or ? turns the text into a pattern: admin* finds every user name that starts with admin, with or without a domain in front.
Export
- Export CSV writes the visible rows as comma-separated text.
- Report... opens a report dialog and writes an HTML report with counts per user, per source address, and per failure reason.
The context menu adds Copy selected, Copy all, and Refresh (F5).
What this is not
The dialog reads only the Security log of the target server. Network devices, Remote Desktop Gateway logs, and domain controller logs are not consulted. A brute-force attempt stopped at the gateway does not show up here.