I think I figured it out. I now understand that the Configure button was suppose to pop up another dialog box were I enter what I want to check (i.e. Ping a server host name). I wasn’t seeing the dialog box until I got the port 20012 opened all the way and configured with the correct username and password. If Woodstone monitors this, I hope they re-evaluate their online manual for the agent configuration because it seemed incomplete. I didn’t see any documentation on what the Configure button did.
Shouldn’t the Woodstone service on the remote agent be set to Automatic? It is set to manual by default. Thanks for everyone’s help. -courtney From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Dirk Bulinckx Sent: Wednesday, September 22, 2010 10:46 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Understanding Remote Agents The entry is not pointing to a remote agent check apparently but to an COM check, and it's saying that it doesn't know the check that it points to. From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Courtney Kibbe Sent: Wednesday, September 22, 2010 7:16 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Understanding Remote Agents Are you referring to the logging of SA? I had just enabled it and this is what I get after an update… “Wednesday, September 22, 2010 9:39:10 AM External COM check (,20):ERROR: Unknown check” -courtney From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Dirk Bulinckx Sent: Wednesday, September 22, 2010 9:31 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Understanding Remote Agents and when it shows the down, what does it show as reason for the down? From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Courtney Kibbe Sent: Wednesday, September 22, 2010 6:16 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Understanding Remote Agents After excluding the 20012 port from remote agent’s Windows firewall, I no longer get the timeout error but is now showing that the server is down. I am able to telnet to x.x.x.97 20012 from the SA workstation. I get a “SSH-2.0-WeOnlyDo 2.0.6” prompt. -courtney From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Laatz, Anthony Sent: Friday, September 17, 2010 6:01 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Understanding Remote Agents You don’t have to do much of anything to the remote agent. I loaded the angentconfig.ini and left the defaults, of course change the pw. I forwarded port 20012 to the server it was running on and that’s it.. go back to the SA installation and configure the settings for remote agents.. then goto the ‘check’ and select remote agent check and enter in there what you want it to check. Thank you, Anthony Laatz Network Administrator – Answer Center America From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Courtney Kibbe Sent: Friday, September 17, 2010 5:16 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Understanding Remote Agents I’ve made the hole in the remote router’s firewall for the default port 20012 I’ve made the changes to AgentConfig.ini Protocol: SSH Port 20012 User/group type: SAClient IP Range: 192.168.2.4 – 192.168.2.4 User Name: *** Password: *** I don’t know what to do with tcpconfig.ini. Restart Woodstone’s Remote Agent for Windows I then went into Setup on SA and configured Agents (for remote Agent Checks) Host: x.x.x 97 Port 20012 Protocol: SSH Timeout: 0 Username: matches above Password: matches above Description I then created a new entry Server Name: x.x.x.97 (matches Host field above) Check tab Check to use: Remote Agent Check Select from list what I created above Press the configure button. With all that configured I get “Error: The current connection has timeout” -courtney From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Dirk Bulinckx Sent: Thursday, September 16, 2010 10:31 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Understanding Remote Agents Servers Alive connects to the Remote Agent and requests info from the Remote Agent. So on the firewall/router of net Remote Agents network you have to have an open inbound port. On the system running the Remote AGent there is an ini file contain the agent configuration. Using the AgentConfigManager (on the same system) you can open this INI and make change to it's config. (username/password/allowed IPs/port/…). If you do change some of the parameters, make sure to restart the Agent AND to adapt within Servers Alive to connection parameters for that agent too. dirk From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Courtney Kibbe Sent: Friday, September 17, 2010 2:31 AM To: Servers Alive Discussion List Subject: [SA-list] Understanding Remote Agents I’m not understanding how the remote agents works or how to configure it. Is there any documentation on it, other than the on-line manual? Do I need to open an inbound port on the remote router, 20012? Can the user name and password be changed? My understanding was that I can install the agent on a remote server and it would send information to Servers Alive, such as it’s on-line. -courtney To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
