Re: RadiusNT -
Steve Williams ( (no email) )
Wed, 4 Mar 1998 09:13:37 +1000
>>I guess I explained it wrong. What I should have said is when I reboot the
>>SQL server it leaves people in the table. The solution another user
>>suggests below is interesting but I run RadiusNT as a service.
>>
>>>We start RADIUS from the startup group with this batch file:
>>
>>>REM Starts RadiusNT Service
>>>isql -E -d Emerald -Q "UPDATE ServerPorts SET AcctStatusType = 2 WHERE
>>>AcctStatusType = 1"
>>>net start RadiusNT
>>
>>Do you have any other suggestions? Seems like RadiusNT should clear the
>>serverports before it starts, will this be changed in future versions?
>
>Gregg,
> We had to make RADIUSNT not start up automatically because it would
>sometimes win the race with SQL Server, so wouldn't process incoming calls.
>To get around this, we set the startup in the Services window to "Manual"
>and start it as I showed above. RADIUSNT is running as a Service, just
>being started a bit later via the batch file.
Simple fix for that. Go into the registry, and under the key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RadiusNT add the string
value
DependOnService "MSSQLServer"
This forces RadiusNT to wait until the MSSQLServer service has started
before the RadiusNT service starts. I think that the installation procedure
should give the user the option of adding that registry value when RadiusNT
is installed as a service.
Sly