When I try to discover Windows machine, I get a "Authentication failed. Kindly verify the user name and password provided" message, even though I provided valid authentication details.
Applications Manager is running in Windows and you are trying to discover another Windows machine without Admin access.
Solution:
It is important to note that user with any type of access can log in to
Linux, whereas Admin users only can log in to Windows when the server
is running in Windows machine.
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 ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...I get the message "Authentication failed. Kindly verify the username and password provided" while adding server/Microsoft .NET/Exchange server through WMI.
Solution: Enter the username as <DomainName>\<UserName>. Also refer to: https://desk.zoho.com/portal/manageengine/kb/articles/authentication-failed-or-access-denied-message-is-shown-when-trying-to-add-the-server-monitor-through-wmi-modeWhile trying to discover Oracle Database server, it fails and prompts some message.
1) Error: Failed. Oracle Server is down. Error Message: IO Error: The Network Adapter could not establish the connection Solution 1: The Oracle server is down, Please ensure whether the server is up and running fine. Solution 2: The Oracle server is ...LDAP - Unable to find valid SSL Certificate
If there is an error while adding LDAP Server Monitor with the message "Unable to find valid SSL Certificate", then please try the below steps to troubleshoot the issue. When the error occurs we can find the below traces in the "stderr.txt.*" log ...