(Note: Had regedit going to watch the registry)
1. Opened the admin program (of course everything there was again blown
2. Typed in all my stuff AGAIN
3. Installed the service via admin (Did not save yet)
4. Checked the registry, only a couple entries there, including mode=0 (no
5. Saved the config (recheck the registry, stuff there)
6. Went directly to the CP->Services and tried to start the service
7. It started!
I'm pretty sure that's exactly what I did (retracing steps not easy...)
Now I'll reboot the thing and see if it will start all by itself!
BTW, to answer your question, at the time it was crashing mode was set to 1
in the registry...
From: Dale E. Reed Jr. [mailto:firstname.lastname@example.org]
Sent: Wednesday, May 19, 1999 5:10 PM
Subject: Re: [RadiusNT] Unable to get RadiusNT running as a service...
Blake Eitniear wrote:
> 1. There is no service.log file. Is this something I need to enable?
> 2. The log file for Auth gave the error:
> Initializing Winsock...
> Couldn't open d:\radiusnt/clients to find client
> Client Initialization failure
> Which is what I then get when I try to restart Radius from the command
> prompt after bombing out on trying to start the service... So it appears
> that radius believes it must start with text mode regardless of what is
> checked in admin... Registry setting wrong?
What is the mode setting in the registry? It looks like its set to
0 and should be 1. If you run the RadiusNT Admin, does it show
text or ODBC mode?
Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com