Should I still try the same troubleshooting method? Or do you have different
ideas? The problem is that I have no idea of knowing when it is going to
stop working. I mean, it ran for almost 7 hours before it stopped last time.
I am going to try and let it run all day tomorrow while I'm here and
hopefully I can re-create the error. In the meantime though, any more ideas?
> -----Original Message-----
> From: Dale E. Reed Jr. [SMTP:firstname.lastname@example.org]
> Sent: Tuesday, September 21, 1999 6:13 PM
> To: email@example.com
> Subject: Re: [Emerald] RadiusNT failed miserably
> Brad Teague wrote:
> > Then, mysteriously, it will just fail. Friday night (9/17/99), RadiusNT
> > bombed out on us and started failing every user that attempted to get
> > online. This caused EXTREME problems as you can imagine for about 30
> > until our emergency line got in touch with me and I was able to revert
> > the old authentication server.
> Define an acct/auth log file and turn on the four debug options and
> let it run as a service like that. Also, grab RadCheck and
> install it to restart RadiusNT. Then look at the logfile
> entries where RadiusNT crashes/restarts and send those to me.
> You can get RadCheck from:
> Note: Radcheck is NOT a solution. Its a temp workaround until we
> can figure out what the problem is (sorry, I couldn't resist).
> Dale E. Reed Jr. Emerald and RadiusNT
> IEA Software, Inc. www.iea-software.com
> For more information about this list (including removal) go to:
For more information about this list (including removal) go to: