Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Microsoft NPS Error RADIUS Client Authentication Attribute not Valid (ID 18) appearing in our logs. What is causing this?

April 26, 2017authentication client Error Id Microsoft NPS radius valid

0

Posted

Microsoft NPS Error RADIUS Client Authentication Attribute not Valid (ID 18) appearing in our logs. What is causing this?

1 Answer

0

Posted

This error message indicates an incorrect shared secret. To fix this look at which RADIUS client (AP / Controller / RADIUS Proxy etc) is causing the error and check the match of the shared secret. Remember that, unless specifically requested otherwise, there is a different shared secret for each ORPS-NRPS combination. Also, the RADIUS client related to the issue may be one of your own RADIUS clients on your network – if you only have one ORPS and the automated JRS authentication monitor shows access-accept for the test account at your realm via all three NRPS, this indicates the shared secrets with the NRPS are fine. Microsoft TechNet article on this: Access-request message received with authenticator attribute not valid.