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.

I keep getting Bad Authenticator messages when I get accounting requests from a GRIC roaming connection. Why?

0
Posted

I keep getting Bad Authenticator messages when I get accounting requests from a GRIC roaming connection. Why?

0

A number of radius servers, such as Merit, the AimTraveler server that GRIC uses and others do not correctly compute the authenticator on accounting requests. They do not conform to the Radius specification. Radiator checks all authenticators against the specification and complains if a bad authenticator is received. It does not look like these servers are going to be repaired, so Radiator has a special flag to ignore the authenticator in incoming accounting requests. See IgnoreAcctSignature in the clause. 12. How can I authenticate against NT passwords and GroupsOn NT, you can authenticate users using their NT user password and NT Global Groups. This means that you can ensure that only real NT users can log in. You can also ensure they get special NAS configurations that depend on which NT Local Group they are in. Your configuration file should look something like this: # put etc clauses here ….. # might want to specify the name of the user

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123