Failed login alerts for some domains

Failed login alerts for some domains

Error: Failed Login alerts are received for some specific domains.

Solution:
For Windows WMI monitoring, failed login alerts are received for some domains because Kerberos authentication is done first, followed by NTLM.
This can be avoided by providing the server name within the username field as shown in the below screenshot:

                  New to ADSelfService Plus?

                    • Related Articles

                    • Troubleshooting Authentication Failed error

                      Authentication Failure Authentication failure occurs when the request to a resource is missing or has invalid credentials. Check if URL requires authentication Access the URL in an incognito/private window and check if any pop up asking for ...
                    • Troubleshooting 'Failed to Negotiate Algorithms' Alerts in SSH Monitoring

                      Failed to Negotiate Algorithms – Critical Alerts in SSH Mode The "failed to negotiate algorithms" exception occurs when an SSH client and server cannot agree on a common cryptographic algorithm for secure communication. This prevents the SSH ...
                    • "Prompt not matching the target server" alerts in Servers

                      Critical Alert: Prompt not matching the target server. Kindly check whether the given Command Prompt is correct. This alert is generated when the target server's prompt does not match the prompt value configured during monitor addition. Possible ...
                    • Troubleshooting MS SQL login failure

                      Problem:  The following error message appears in MS SQL monitor during login: "Login Failed. The login is from an untrusted domain and cannot be used with Windows authentication"  Solution: Verify if the password of the SQL account (domain\username) ...
                    • SAP Alerts displaying incorrect time

                      Problem :The time shown for SAP Alerts under Alarms tab in SAP monitor is incorrect. Solution : Enter the time difference (in hours) in <AppManager_Home>\conf\SAP.properties file am.sap.alerttime.offset key. For example, in the above screenshot the ...