chrisfoot

I have just a couple of more questions. Once again, much appreciated. What exactly happens when we fill in those fields for the proxy? Is there some extra configuration applied to the agent during install? The server that we specify as the proxy - I assume that we need to have a proxy application already running on it. Is…

Oops. I was wondering if those settings were applicable to our implementation. We are upgrading to 6.2.2 - actually as I write this. Once back up and running, we will configure a proxy according to your suggestions. Thanks again for your advice - we do appreciate it.

The database credentials are different that the OS credentials.

So, here is where we are. We have a WinOS proxy server set up using NETSH. We executed NETSH on the proxy to listen on port 17778. It forwards to our main polling engine IP and port 17778. We manually installed the agent on a couple of test boxes. When the installation wizard asked us for a polling engine IP and port, we…

Yes. Since it is a UNIX/Linux script, I am assuming that the "Credential for Monitoring" would be used for OS authentication - to run the script itself on the OS containing the embedded PERL commands. Once the script runs on the monitored target, I need a way to then authenticate to the database. So, I think I need to pass…

Thanks guys! We will keep moving forward with this strategy. We need to take a quick step back as we are experiencing performance problems. When we add an application template with 20 components to a node, it is really taking a long time I added 8 new applications, it is 5 hours later and 6 of them are finally polling.…

I appreciate the response! We will continue to plug away at using some form of port forwarding. Any suggestions from others attempting this would be appreciated. If we do get it working, we'll certainly provide what we did. We would really like to use an additional polling engine in the green zone, but the licensing costs…