There was a re-order in the way RadiusNT checks the validity of a
request coming in (from a legit ip, valid username, etc). However,
I don't see how any client could make a request without being in
the servers table, unless it previuosly was failing the validity
check ABOVE where it checks to see if its from a legit IP (although,
checking the IP is one of the first things it does).
> Second is user Not Found messages in the log file. There are no carriage
> returns at the end of these messages, so the lines get exceedingly long.
> Certain lines in the log file (maximum simultaneous login messages, for
> example) had two carriage returns at the end, putting in extra blank lines
> which were not necessary. I'm all for getting rid of those. But there
> should be one carriage return at the end of Not Found messages.
We've been working on trying to cleanup/reformat a lot of the uneeded
debugging and make sure its under the correct section. I'll see about
correcting these.
--Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com