Re: Radius stops authenticating users

[Craig Johnson]

In article <dbertra...@no-mx.forums.novell.com>, Dbertran wrote:
> I changed the public IP address on my BM and then my NDPS manager
> stopped working along with my RADIUS services. I moved NDPSM to an other
> server and I am trying to fix the RADIUS issue. But I am still getting
> the same error for every authentication requests.
>
Where are the Radius requests coming from? Did you call out the old
public IP address in the DAS object?

Do you have public or private IP address in the BM server's HOSTS and
HOSTNAME files?

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

[Craig Johnson]

In article <dbertra...@no-mx.forums.novell.com>, Dbertran wrote:

> And HOSTNAME had:[old Public IP][new Public IP]
>
> I fixed the two files, restarted the server and Radius started working
> again.
> So that was the right question, thank you very much.
>
A bit of an educated guess there.

> If you happen to know why Radius was successful on all its call to nds
> but the Authenticate, I am curious to know:
> (->)NADMAuthRequest(AG_0000199.dial_in_users.girosol ) succeeded,
> time:6
> [2009-04-29 11:20:30 AM]
> (->)Authenticate (0 policy, NDS pswd) (for
> AG_0000199.dial_in_users.girosol), failed, -941 (0xfffffc53)

Don't know. Sometimes it's a lot easier to fix problems than to explain
them.

I know weird stuff goes wrong when you have wrong or missing entries in
the hosts and hostname files, so I routinely check them whenever I am up
against some sort of name resolution issue, or when IP addresses change.

You don't want to lose that loopback entry either.
>
> I am glad it is working now, thanks again.
>
You're welcome.