Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Remote Network Monitor
- Thread starter deboyland
- Start date
JFBouchard
IS-IT--Management
Low cost: ipsentry (
At the office, we use Netiq app manager (
Hope this helps. Please let me know if this resolve your issue
Jeff
At the office, we use Netiq app manager (
Hope this helps. Please let me know if this resolve your issue
Jeff
It is a little tough to receive an email if the remote cannot access its SMTP server 
.
On the remote machine:
Start, Run, services.msc
Highlight the service(s) you wish to monitor one at a time.
Click on the "Recovery" tab, and set the first or second failure option to "Run a program"
You can then have this .bat or .cmd or scripting feature available to do any remote reporting you wish.
.On the remote machine:
Start, Run, services.msc
Highlight the service(s) you wish to monitor one at a time.
Click on the "Recovery" tab, and set the first or second failure option to "Run a program"
You can then have this .bat or .cmd or scripting feature available to do any remote reporting you wish.
- Thread starter
- #4
Try (a really good freeware), Look@LAN:
Very inexpensive utilities are available:
Very inexpensive utilities are available:
- Thread starter
- #6
Is there a freeware program which can tell you what services are not working. and if the server just restarted.
Let me ask. I am new at this. What do i want to know from a remote network monitor stand point?
then i can go from there.
thxs
Let me ask. I am new at this. What do i want to know from a remote network monitor stand point?
then i can go from there.
thxs
If Windows 2003 use Remote Desktop, and then you can use the services.msc, or the MMC to view what is going on.
If Windows 2k, the safer thing to do would be to use Terminal Services, or some of the freeware Monitors suggested earlier.
If it stops responding, there is an issue. If the server drops there is obviously no information you can obtain, other than it is no longer online.
On a higher level you could use the Microsoft Systems Management Server to monitor and control all of these events, but I was assuming your were a relatively small site.
If Windows 2k, the safer thing to do would be to use Terminal Services, or some of the freeware Monitors suggested earlier.
If it stops responding, there is an issue. If the server drops there is obviously no information you can obtain, other than it is no longer online.
On a higher level you could use the Microsoft Systems Management Server to monitor and control all of these events, but I was assuming your were a relatively small site.
And if the following has been done, or this seems unecessary advice, I apologize ahead of time:
We are entering into the Hurricane season on the East Coast of the US. You want your servers to be under the protection of a good UPS device. Most offer a reporting and email feature to report that the server is running under UPS because the power has failed.
For logical OS failures, my advice above I hope can help. Assuming at least the SMTP connection is live, implement a script to email you that there are problems for critical services.
MAPISEND as a utility might be available on the server:
Or look at freeware alternatives:
You could always redirect the output of an sc.exe to a text file and email that using the above tricks on a failure:
send_me_errors.cmd
sc queryex all >c:\server_status.txt
(insert here the sendmail command line appropriate from above, using the /f "C:\server_status.txt" as part of the command line.
We are entering into the Hurricane season on the East Coast of the US. You want your servers to be under the protection of a good UPS device. Most offer a reporting and email feature to report that the server is running under UPS because the power has failed.
For logical OS failures, my advice above I hope can help. Assuming at least the SMTP connection is live, implement a script to email you that there are problems for critical services.
MAPISEND as a utility might be available on the server:
Or look at freeware alternatives:
You could always redirect the output of an sc.exe to a text file and email that using the above tricks on a failure:
send_me_errors.cmd
sc queryex all >c:\server_status.txt
(insert here the sendmail command line appropriate from above, using the /f "C:\server_status.txt" as part of the command line.
- Status
Similar threads
- Locked
- Question
