My fault, spoke to soon. It appears that the
Boardtown RadiusNT scripts
setup the calls table so NASPort is a primary key,
and can not accept duplicate values. Is NAS-Port supposed to be a unique number
every time? Steve -----Original Message----- Anyone using Platypus with a session
ID of type INT as distributed by Boardtown with there RadiusNT integration
scripts? Some of the terminal servers we use
appear to report session-ID in hex, thus causing inserts into the calls and
serverports table to fail. Any ideas? Steve Brown |
- Re: (RADIATOR) RE: Platypus, hex session ID Steve Brown
- Re: (RADIATOR) RE: Platypus, hex session ID Hugh Irvine