When you're running RadiusNT 2.5 (2.5.100?), are you doing it in debug mode
or do you have it running as a service? Either way, is accounting being
handled via ODBC or text file? If you're not using ODBC as the means for
logging ACCT records, then Emerald will have no way of knowing that the
users have disconnected. Until this problem is resolved, you might want to
disable Concurrency Control in the RadiusNT Admin.
By the way, I forgot to ask you this when we upgraded your Max last week,
but do you have any Unix machines? Having a SysLog output from the Max
helps tremendously because you can watch almost everything that goes on
with the Max. I don't know if the SysLog output has to go to a Unix
machine or not, but our Maxes output to one of our Suns, while everything
else is handled by our NT machines. Right now, your SysLog settings in the
Max are not set (at least they weren't when we upgraded your Max).