000015450 - Symptom: 'Connection to RADIUS server failed due to incorrect credentials. Verify your username and password are correct.'

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000015450
Applies ToRSA Authentication Manager 7.1 SP4
IssueSymptom: "Connection to RADIUS server failed due to incorrect credentials. Verify your username and password are correct. "
Symptom: when editing radius server from security console error "unable to connect to radius server"
Symptom : Group Policies are set to only allow NTLMv2 for the system under windows Platform, and will reject LM and NTLM. Changing this setting, will configure and manage RADIUS on a repeatable basis without having to restart the RADIUS_OC Service.
Symptom : Radius account under Local users and groups will be locked every time you try editing the radius server from security console or restarting the Radius service.
RADIUS configuration fails on Replica server. RADIUS is already configured on Primary server. In this case, Replica server was added in different domain and that domain controller has a different policy.
 
ResolutionLog on to domain controller: Start -- > Administrative Tools -- > Local Security Policy -- > Security Settings -- > Local Policies -- > Security Options -- > Network security : LAN Manager authentication level -- > Right Click  properties -- > select "Send LM & NTLM" instead of only allow NTLMv2 from the list.
Log on to domain controller: Start --> Run --> gpedit.msc --> Windows settings --> Security Settings --> Local Policies --> Security Options -- > Network security : LAN Manager authentication level -- > Right Click  properties -- > select "Send LM & NTLM"
See also Configuring Radius: Unknown error
See also RSA RADIUS fails to configure on Microsoft Windows 2008 R2
Legacy Article IDa59240

Attachments

    Outcomes