When trying to open the Manage a Radius server all we get is
There was a problem processing your request. Box and we can't do anything. The radius server is running but we want to setup a replica and we can't due to this problem.
Thanks
When trying to open the Manage a Radius server all we get is
There was a problem processing your request. Box and we can't do anything. The radius server is running but we want to setup a replica and we can't due to this problem.
Thanks
ims-2.0 SP4 P13 - 5/2/16 1:37:05 PM AKDT
cm-1.0 SP4 P13 - 5/2/16 1:37:05 PM AKDT
am-7.1 SP4 P13 - 5/2/16 1:37:05 PM AKDT
The Radius server works with current clients but I can’t get into the primary Radius Server config and make changes. More to the point the Replica stopped working and we need to set it up again.
This is all running on a Windows 2008 R2 server.
RSA has been running flawlessly for a couple years. Very little changes except for token maintenance.
Thanks
7.1 is a many layered onion in regards to radius and how it is integrated. So, there are no easy things
to throw out on this except one (which is likely not the problem), but the only easy thing to check.
Check the windows system local users and verify the [Radius_useraccount] is not set to expire or need a password change.
This is likely to require you to open an active support case where we need to send you some
debug code and extract all the system credentials radius is trying to use, and verify that
it is all set correctly in the correct locations, among other things to step through and debug.
Thanks. I realized that we are many, many, patch levels behind. Maybe getting up to the most current patch level will help. We are at P13 and the current patch is P37. For all I know there are/is fixes between the current OS patch level, which is constantly being patched, and the current running version of the software. It could be OS changes have caused the Radius Server to stop working correctly at the management level.
what version and patch level of RSA Auth Manager ?