Look at it from a "simple user" point-of-view.
How can a "simple user" see/detect that the server is not dialing to the
net?
By doing a ping to the internet?
=> if so have SA do a ping to the internet
Same for the radius.
(why not try to let SA authenticated a user towards the radius
server?)
Dirk.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Webmaster
Sent: Tuesday, January 06, 2004 3:48 PM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] SA Features Questions
At 12:44 AM 1/6/04, you wrote:
>Define "not accepting calls", once we know what you mean by that we can try
>to advince what kind of checks to do.
>
>
>Dirk.
>
>
This past week the NT 4.0 Server (running Worldgroup Software) did not
respond to my dialup to the net. Worldgroup normally verifies my user
account against it's dBase. The server and program must be rebooted in
order for me to connect. I cannot just start the program for this reason I
think the problem is with the server. If SA can detect the server
not responding and reboot, it would be very helpful. More helpful would be
if it can check
the line at designated times and reboot both the server and then the radius
box.
The Radius Server does accept calls (but I'm in terminal mode) and my logon
cannot be verified against the dBase on the Main Server because it's not
responding.
I must physically be at the Main Server to reboot in the above event.
Thank you,
Dee
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
