> 1) Any reason the CallDate is set as a shortdatetime in the
> to figure out anything accurately to only 1 minute, and
> the documents to RadiusNT specify CallDate to be a
Just DB space. Newer versions of RadiusNT use GetDate() or
Date from the DB engine, so changing the type should allow
the greater information you are asking about.
> 2) RadiusNT has specific problems with accounting for one PortMaster
> - all the other PortMasters are remote and they account
> perfectly. The only one that has the problems is the local
> portmaster running on the same local lan - it seems it accepts
> the requests for a short while, and then all of a sudden it
> gives errors saying that their is a conflict with pk_Calls
> that already exists. What it looks like is that the SessionID
> is been repeated over and over, i.e. the PortMaster is not
> receiving a proper ACK back from the Accounting server.
Your last sentence is the problem. Make sure the RadiusNT's IP you have
your PM sending the requests to is the primary IP address for the
machine. Since that is the IP the request will be returned with, if
the PM sends to another IP address, it will be returned via a different
IP and the PM rejects the ACK.