Security Compliance

Unable to authenticate ARM username

The username is not authenticated when attempting to log in to ARM config / ARM Fat client.

First published date

3/29/2019 8:30 PM

Last published date

2/25/2025 7:25 PM

Overview

You have done a fresh installation of ARM and unable to login to either the ARM config or the thin client using an Active Director Domain account and you see the below error in windows logs and pnserver.log. Further, you can only login with local user account to the application.

[ 1980|SRV12-WSUS |pnServer |5176.1| 47|mydomain.com\SYSTEM |pn.helper.DomainHelper |190218|13:36:51.874|Error ] DomainHelper.ValidateCredentialLegacy(String userName, String fullQualifiedDomainName, String password): System.UnauthorizedAccessException: No credentials available for Impersonation 
--BEGIN-OF-EXCEPTION------------------------------------------------------------
System.UnauthorizedAccessException: No credentials available for Impersonation
bei pn.security.Impersonation..ctor(WindowsCredential credential, ImpersonationOption options)
bei pn.security.Impersonation..ctor(ICredential credential, ImpersonationOption options)
bei pn.helper.DomainHelper.ValidateCredentialLegacy(String userName, String fullQualifiedDomainName, String password)
--END-OF-EXCEPTION--------------------------------------------------------------

OR

The specified domain does not exist or cannot be contacted. 

The specified user cannot be authenticated in the domain.

Product section

Access Rights Manager

Cause

  • NetBios name contains a period so the user in the domain may not be identified. 
  • Wrong DNS Servers configured on ARM Server and hence the User account is not getting authentication request sent to correct AD server.
  • The password is wrong or the user is locked out.

Resolution

Scenario 1: NetBios Name contains a Period
  • Adjust setting of each ARM host:
  
-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

​​​​<activeDirectory.FqdnToNetBios.8man-demo.local>8man-demo.any</activeDirectory.FqdnToNetBios.8man-demo.local>
<activeDirectory.NetBiosToFqdn.8man-demo.any>8man-demo.local</activeDirectory.NetBiosToFqdn.8man-demo.dings>
  • Add the two lines above at the end and before </config> tag and replace the domain name below with the ones in your Environment.
    • FQDN = 8man-demo.local
    • NetBIOS = 8man-demo.any
  • Restart the ARM Service

You should be able to login now.

Scenario 2: Wrong DNS server configured on the NIC on ARM server
Symptoms in this case the domain user's name will not resolve rather it is show a SID and you are not able to browse to the AD to enumerate objects.

Solution:  Verify NIC properties and add correct DNS servers.

Scenario 3: The username is wrong or the user is locked in AD
Solution: Please contact SolarWinds Support to reset the password and unlock the user in AD.