JornadaRange
asked on
Netware 6.5 SP6 breaks Radius service
After applying service pack 6 for Netware 6.5 our Radius service no longer works. When connecting, using Cisco VPN client, we get prompted for login and enter the password and after awhile we get the following error.
Secure VPN Connection terminated locally by the Client. Reason 413: User authentication failed.
On the Novell Radius Service screen it says "Access Accepted" four times and the username of the person trying to login.
We do not have Border Manager on the server.
Secure VPN Connection terminated locally by the Client. Reason 413: User authentication failed.
On the Novell Radius Service screen it says "Access Accepted" four times and the username of the person trying to login.
We do not have Border Manager on the server.
ASKER
ShineOn,
We were at support pack 3.
We have iManager 2.02 and we are upgrading to 2.6 along with the plugins to upgrade the certificates thru iManager.
Thanks
We were at support pack 3.
We have iManager 2.02 and we are upgrading to 2.6 along with the plugins to upgrade the certificates thru iManager.
Thanks
ASKER
We did several things to fix the problem.
We installed the ConsoleOne Snapins from the Border Manage 3.8 Demo CD.
Reconfigured the DAS and the DAP objects, as well as reconfiguring User context DAS configuration. Also recreated default certificates. Reconfiguring DAS eliminated two missing attribute errors from Radius debug log.
But we think the fix was to set up Enhanced Passwords.
We installed the ConsoleOne Snapins from the Border Manage 3.8 Demo CD.
Reconfigured the DAS and the DAP objects, as well as reconfiguring User context DAS configuration. Also recreated default certificates. Reconfiguring DAS eliminated two missing attribute errors from Radius debug log.
But we think the fix was to set up Enhanced Passwords.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The reason I ask is, IIRC somewhere along the way in one of the NW6.5 support packs, Certificate Services got upgraded. That made for lots of consternation and odd authentication-related issues.
I think one of the fixes for that was to re-create the server certs with pkidiag. There may be something that needs to be done with sdidiag too, I don't remember...