No. Probably 100 time a day users get "hung" on by the system and it still
thinks they are connected even though they have disconnected. The user
doesn't connect then on even though they are not accually connected. That is
what the SNMP Concurrency Check is supposed to correct.
I don't think it is the NAS as much as crappy modems. I have different NAS's
and they all seem to do it. I connect to any of my NASs without fail 100% of
the time, and disconnect 100% of the time. I have physically unplugged the
phone line, shut off the modem, and done just about any abusive thing I can
think of to get a connection to "hang" but I have never been able to
reproduce this error, yet I see a huge number of these "hangups" per day.
They are really a pain in the butt.
----- Original Message -----
From: "Randy Martin" <IEAEmerald@austintx.net>
Sent: Tuesday, April 18, 2000 5:22 PM
Subject: Re: [Emerald] Work on SNMP Concurrency Checking
> I don't mean to jump into the middle of this, but isn't the above the
> NON-SNMP concurrency doing it's job correctly? It did the radcheckonline
> and found the user already online. It doesn't seem to me that you should
> need both? I don't have the SNMP concurrency setup, and everything works
> just fine on our system. Is there only certain combinations of NAS's etc.
> that have a problem with the non-SNMP concurrency checking?
For more information about this list (including removal) go to: