Hi Mike and Hugh,
Thank you very much for the new feature. Most of the time, it works
well. However, we just come into a situation when the old IP was
reallocated and the PING test just failed to tell.
I think the solution is simple. Before writing a new session record,
remove any existing one with the same IP address. This should be true
in all situations. An IP address just cannot be used by 2 or more
connections at the same time. For session data base using SQL, which we
are, it may need only one SQL statement like this to do the job.
delete * from RADONLINE where FRAMEDIPADDRESS = 'new.ip.addr';
Can you gentlemen make the change? I think it can be a 2 minute job for
you experts.
--
Regards,
Clement
ANS Communications P/L
===============================================
Post Addr: P O Box 6626 Blacktown BC, NSW 2148
Tel: (02) 9552 1655 Fax: (02) 9972 2633
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
