&gt&gtJosh Hillman wrote:&gt&gt&gt&gt&gt&gt They're being disconnected based on the idle limit set in the Max. By&gt&gt&gt default (unless it's changed recently), the Maxes have 120 seconds set&gt(why&gt&gt&gt so low, I don't know). On the assumption that you changed it to&gtsomething&gt&gt&gt like 1200 (20 mins) or something, then all users will be using that&gtsetting.&gt&gt&gt You won't be able to override it for individual users with radius&gtsettings&gt&gt&gt because the Max will ignore them (because Shared Prof = no).&gt&gt&gt&gtShared Profiles tell the Max not to let two non-multi-link connections&gt&gtuse the same username.

From: Ed Miller &ltemiller@del.net&gt&gtShould it be yes or no to the stop non-multi-link connections?

If you have RadiusNT set to use Concurrency Control and Variable Login
Limits, and also have your users' accounts have a Login Limit of 1, then
those users will not be able to log in more than once per username
simultaneously. This in-turn prevents MP.

Now that I think of it, I think we have Shared Prof = yes to allow a couple
of us to use MP--we authenticate directly in the Max instead of using the
database/radius, so that in the event that there's some problem with the
db/radius, we can still dial-up.
Information on Shared Prof is in the Max Reference Guide, &quotMAX Alphabetical
Parameter Reference&quot. I seem to remember MP not working until we set this
to &quotyes&quot, but I don't remember if it was strictly with the few accts on the
Maxes or if it also affected

&gtI have Ethernet/answer/Session options/Idle=&quot0&quot This does mean that i can&gtset the disconnect from Emerald services, Right?

This setting is overridden by whatever value you have set in the radius
attribute, Ascend-Idle-Limit. Setting either of these settings to zero
makes it not time out.