And it can put accounting records back together out of thin air that it
never received. Its amazing new technology! :) Sorry, couldn't resist.
Acctually, what I was referring to is a bug in 1.16.60 and 1.18.0.
1.16.60 would ACK anything that came through. So if you lost the
SQL Server connection (and 1.16.60 also wasn't reconnecting corretcly)
you would loose all accounting packets during that time.
1.18.0 handled the loss correctly, but wouldn't ACK duplicate
accounting requests. Although not a loss, it would keep a continuous
ping match from the NAS for all duplicate accounting records.
1.19.0 will properly ACK duplicates and will correctly re-attach, even
to re-booted SQL Servers.
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com