Once again I am looking for some insight into possible solutions for Radius
NT 2.5 crashes. We are running 2.5 on NT4, SP5, in debug mode. We have
concurrency control turned on and name trim turned on.
The problem is this: A bunch of garbage will occasionally come through from
our Portmasters, and Radius will completely choke on it when it tries to
authenticate. No error is generated, it simply kicks out to the C: prompt
and ceases to authenticate. It must then be manually restarted. This
happens on a daily basis and I need to know what the fix is. I have read in
the archives suggestions to turn off concurrency control, but this is not an
option for us. We use that feature, and we shouldn't have to turn it off to
keep things running smoothly.
Now I realize that the garbage is being sent by the Portmaster, and that is
a separate issue. My issue with Radius is that it -should- simply ignore or
reject the garbage, rather than just dying on me.
Has anyone had this problem, or does anyone know how to fix it, once and for
all?
Thanks,
Andy Guerriero
FoxBerry Network
Internet Services Manager
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart