It seems that Radius is just locking up. On the 3.51 Machine, we are
running it from a DOS Prompt so we can see the activity, but unfortunately
we cannot capture it. It says something like an SQL Connect error (Write
File) We didn't have time to write it down, We had to get the service up
and running. The 4.0 Machine is running Radius as a Service so we are
unable to see that activity. Emerald seems to be up since we can connect
to it via the Admin and Client program. The funny thing is that when the
primary server goes down, anywhere from 4 to 18 hours after start, the
secondary follows shortly after the primary, about two hours.
> if you run it in foregroun? Whats the last thing to print? What
> options do you have enabled?
>
> -- Dale E. Reed Jr. (daler@iea.com)
> _________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.emerald.iea.com
>
> ----------------------------------------------------------
> RadiusNT Mailing List listserver@emerald.iea.com
>