Update: I switched my NT probes back to checking every 2 minutes (map default), and I set the timeout at 2 minutes (up from 10 seconds) and have seen no false positives. More news as the story develops.
James P. Ashe Systems Analyst 2 East Tennessee State University Office of Information Technology 4 2 3 * 4 3 9 * 4 6 4 8 -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Wigle Sent: Thursday, August 09, 2007 10:14 PM To: 'InterMapper Discussion' Subject: RE: [IM-Talk] NT Services probe default timeout Thanks Janice, Ok, I just tried that and it doesn't seem to help this probe - for us. Right now I set the timeout for 9 seconds (default is 3) (this loc has a RTT of 703 ms) and it still fails with the following: ***** Status: DOWN NT Services (1 up and 0 down) Reason: Timed out attempting to connect to server or get service information. ***** This despite the probe showing all the services so you can select one (or more) to monitor. It had to connect to get that right? It doesn't seem to matter how many times I right click - Reprobe Selection. Once it goes down - it stays down. Once down, if I right click - set probe, the service comes up (after a few seconds). The service I'm monitoring is checked. I click OK and then the probe immediately shows flashing red. Which is weird since as you can see above it says - NT Services (1 up and 0 down) So although the stuff it's monitoring is up, the probe shows down. Don't we want to show "down" when a monitored service is down? In this case the monitored service is up. What IM is using to determine "down" is not just the monitored service and the timeout select doesn't seem to affect it. Although the site has a RTT of 703 ms, everything else Microsoft still works - slowly but we get there. I can even RDP to the server and other probes work just fine. Kevin -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Janice Losgar Sent: 9-Aug-07 16:01 To: 'InterMapper Discussion' Subject: RE: [IM-Talk] NT Services probe default timeout Kevin, You can increase the probe timeout by selecting the device, right-clicking and choosing the Set Info > Set Timeout command. Regards, Janice Losgar Dartware, LLC From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Wigle Sent: Thursday, August 09, 2007 2:59 PM To: 'InterMapper Discussion' Cc: [EMAIL PROTECTED] Subject: RE: [IM-Talk] NT Services probe default timeout Good timing, We're starting to use this probe to watch a few applications. We're spread out in a forest with several domains, most of the domains we manage are at the end of a satellite link. The stuff close to us works like a charm but the satellite stuff times out as mentioned. The probe either has to do a retry now and then or we need to be able to adjust the timeout. Kevin From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Ashe, James P. Sent: 8-Aug-07 10:09 To: InterMapper Discussion Subject: [IM-Talk] NT Services probe default timeout Is there a way to adjust to default timeout on the NT services probe, or change the 'Timed out attempting to connect to server to get service information' status to a critical instead of a down? I love this probe, but I am reaching the 'crying wolf' threshold of false positives caused by it. James P. Ashe Systems Analyst 2 East Tennessee State University Office of Information Technology 4 2 3 * 4 3 9 * 4 6 4 8 ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED] ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED]
<<image001.gif>>
