Looks like a good idea to me...
dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jonathan Marsden Sent: Tue Aug 26 11:50 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Server 2003 and cross monitoring issues ok...I will leave the XP workstation on the network...but stop the SA service entirely, and see if the server locks...if it doesn't, then I will start the SA service with only a ping for the Win2k3 host, then keep adding the other three checks for that server one at a time, until I make it lock again...is that the idea? Jon -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dirk Bulinckx Sent: Tuesday, August 26, 2003 3:58 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Server 2003 and cross monitoring issues If you now retry having the XP station ON the network but not checking (so not running SA), does the lockup occure too? If so, then the next step (in order to determine what is causing it) is to put some of the checks (that are done towards the Win2K3 host) into maintenance... dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jonathan Marsden Sent: Tue Aug 26 2:59 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Server 2003 and cross monitoring issues Dirk, I am experiencing lockups twice a day...two times in a 24 hours period on the average... I have run the server for a week without SA...in fact, I ran it for months without SA and never had a problem, the only time I rebooted it was on the 15th of the month, and that was just to "refresh" everything, I have had it run over 90 days uninterrupted in the past...and the only program that interacts at the network level that I have added in the last several months, is SA. So, I removed the workstation from the network physically, and the lockups stopped. I now have reattached the XP workstation running SA back to my network, and the system locked up at 7:45-7:50 PM local time tonight. I received the SMS alert at that time. The server was not visible to pinging at that point in time, and I looked at every event log on my server...and none of them show any event at 7:45-7:50...as a matter of fact, the only events they do show within several hours of that time period is at 7:54, when I rebooted the server, they show it coming back up, but nothing when it crashed. The alert I had set to reboot the server obviously didn't reboot it, but that may have been a configuration fault of mine...in the alert setup, I only had the user name and password (username,password), and I note from the setup to do NT services checks you should have the (servername\username,password)...is that the same format I should use for the alert configured to restart a server? Jon Marsden -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dirk Bulinckx Sent: Monday, August 25, 2003 3:58 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Server 2003 and cross monitoring issues >From what I understand in your message, you see a link between installing SA and the lock-ups of the server. If you "run" for a week do you get at least one lock-up? If so why not run without SA for a week then to see if the lock-up still occures? Also do you find anything in the eventlog of the server? Can you still ping the server during the lock-up? dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jonathan Marsden Sent: Mon Aug 25 1:17 AM To: [EMAIL PROTECTED] Subject: [SA-list] Server 2003 and cross monitoring issues I have a request for help that I want to bring up... I have a server 2003 Enterprise version Wins server, which is also the gateway to my internet connection...a simple, single level network, so I am not running DNS, active directory, or DHCP, and I have SA running on an XP pro workstation attached to the network. Since installing SA on the workstation, my server intermittently locks up, freezing entirely, mouse, keyboard...everything dead...which means that my workstations are still running, but I lose all my connectivity...this seems to only happen when I am actually logged into the server as a local user, if I just restart it and don't' log in, it has never locked up. Could it be an issue of my NT logins, I use the same NT user name and password in SA to check the server, as I normally login to the server at the local level with...I think that Dirk mentioned a limitation of the OS issue this last week. I recently set SA to reboot the server in the event it couldn't ping it...but until it hangs again, I don't know if it will work or not...I have always had to go and physically reboot the server. I have the XP Pro workstation with SA set to send an smtp alert first, and then to send an SMS alert two minutes later, via a modem/phone line...I have it configured this way because when my server freezes, it kills my internet access, and therefore my smtp alert never gets sent... I also have the ten user version of SA installed on another workstation on the network, with the same alert methods in place, basically to monitor just the XP pro workstation that my main SA installation is running on, because that is my single point of failure, so far as I can see. If the main XP box crashes, or dies, I lose all my ability to alert, regardless of method, so I figured that the second box would "monitor the monitor". I just wanted any opinions from you folks out there, is there a better, or simpler way to make sure that my alerts actually get out? And do any of you have any suggestions of which services or processes I should be monitoring on the server to reboot it before I lose connectivity entirely? Jonathan Marsden --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 8/22/2003 Tested on: 8/24/2003 7:17:21 PM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com 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 --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 8/22/2003 Tested on: 8/25/2003 8:59:02 PM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com 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 --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 8/22/2003 Tested on: 8/26/2003 5:50:21 AM avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com 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
