My problem with authentication being unpredictable with radlogin appears to
be that RadiusNT is responding too quickly to radlogin. Is this possible ?
It would explain why it works OK in the various debug modes as the response
times are that bit slower.
Is this possible? or am I talking out of the top of my head? The reason I
say this is that accounting tests (start + stop) are being correctly written
to the SQL server but radlogin isn't getting a response.
I have also run RadiusNT as a service in debug mode 1 with a log file set
and it seems to think it is working OK. (i.e. it is sending an ACK even
though radlogin isn't getting it)
For more information about this list (including removal) go to: