We have configured our sql servers accounting table to reject duplicate accounting records by setting the username+acctsessionid+sessiontime to be the primary key (no duplicates permitted) When the NAS sends a duplicate accounting record, sql/radiator spits out an error and does not write the packet to the SQL database (this part is good). My questions is - what does radiator then do with the Accounting Reply to the NAS - does it send back an acknowledgement or does it do nothing therefore making the NAS send the Acct packet again, and again, and again....(that would be bad) Kind regards, Brian Morris PS: Does anyone have a better way to prevent duplicate accounting records? === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.