Re: login concurrency -- FIXED

Josh Hillman ( (no email) )
Wed, 2 Apr 1997 10:49:42 -0500

Thanks Dale! The "Shared Profiles" was set to "No" in the Max, so I
changed it to "Yes" and concurrency now works just fine! I think I'll
enter in that little bit of knowledge into my "personal" documentation for

Josh Hillman

> Josh Hillman wrote:
> >
> > I've been trying for a while to get login concurrency to work, but for
> > whatever reason, can't get it to.
> >
> > In Radius .60's admin, I have Concurrency Control checked and also have
> > Variable Login Limits checked. Mode is ODBC. The RadiusNT service has
> > already been stopped and restarted after saving the above settings.
> > With the one account I'm trying to dialin twice on, the Login Limit (in
> > Emerald) is set to 2, while all other accts are set at 1.
> >
> > On the Max console screen, it disconnects me after displaying "LAN
> > error test" ("test" is the login name). It's doing this as if I'm
> > in the password incorrectly.
> >
> > What am I missing here??
> On the max do you have Shared Profiles = No? This could be causing the
> problem. i would like to see the -x15 debug of the authentication to
> see what RadiusNT is really soing behnd the scenes.
> --
> Dale E. Reed Jr. (