What stored procedure do I modify to allow roaming dial-up connections to
connect even if Emerald sees them online already? I don't need to modify
anything for our local dial-ups since that works fine and also uses SNMP
concurrency checking.
Unfortunately, we're apparently not receiving some of the stop records for
our roaming customers when they disconnect, so Emerald still thinks they're
online and therefore subsequent connections for these people are being
rejected because of concurrency (eventhough they're not online). I can't
use SNMP concurrency checking for the roaming people.
SQL 7, RadiusNT 2.5.213
Josh
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart