> > Kenneth Gustav Eitenmiller Jr wrote:
> >
> > Awhile back I had some help setting up a session time limit for our
> > dialup customers:
> >
> > Radius Attribute
> > Session Time
> > 28800
> >
> > This cut people off after 8 hours...
> >
> > Ever since then my "online" and user concurancy is all screwed up.
> > I am get many "over log in limit" cases in my radius log...
> >
> > This is the error I get running radius -x15
> >
> > ODBC Error: 23000: 2627:
> > [Microsoft][ODBC SQL Server Driver][SQL Server] Violation of Primary
> > Key constraint 'pk_calls': Attempt to insert duplicate key in object
> > 'calls'.
> >
> > I have had to turn off concurancy control to allow my customers to
> > connect...
> >
> > Does ANYONE have ANY ideas???
>
> What type of terminal server are you using? Sometimes, they DO send
> duplicate ASIDs, for different sessions. I had to add the Username
> and port into the primary key for the calls table to work around
> the reuse of ASIDs, before.
3com Total Control...
How do you add the Username and port into the primary key for the calls
table to work around the reuse of ASIDs?
This is not a sometimes thing... This is like 50%+ of our logins...
Thanks,
Ken
>
> --
>
> Dale E. Reed Jr. Emerald and RadiusNT/X
> __________________________________________
> IEA Software, Inc. www.iea-software.com
>
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart