Error: Connection error in RCC

[guybrush]

I have a RMA agent at a site that I can check the services on from the HostMonitor console just fine (it enumerates the services.) When I connect from the RCC I can see all my tests, when try to add the same test for a service at the remote site, it gives me "Error: Connection error in RCC"
Any idea?

Thanks!

[KS-Soft]

RCC cannot display "Connection error in RCC" message, may be it shows "RMA: Connection error"?
When exactly it shows error? When you click on combo box that shows list of services?
It can be firewal or timeout issue, make sure firewall (that protects network where RMA is installed) accepts connections from system where RCC is running

Regards
Alex

[guybrush]

Thanks for the quick reply, the error comes when I am in the RCC, connected to my list (called zmonitor) and when I pull up a test that connects to a network outside mine (using RMA), service check in this case, and click on the pull down box to list available services on a box. When using HostMonitor directly from the server it is installed on, this works without problem.

The error is a box that pops up with the title zmonitor (must be from my list name) and just says "Error: Connection error", I upped the timeout on the RMA at the remote site from 10 to 50 just to see if it helped with no change.

[KS-Soft]

So, what about firewall?
There is another timeout specified on HostMonitor/RCC side in "Agent Connection Parameters" dialog

Regards
Alex

[guybrush]

Actually, the error box does say rcc in the title and "Error: Connection error" in the dialog box. From the machine that the host monitor is installed on (On my LAN), this works perfectly, enumerates the services from the other LAN through the firewall. I am running the RCC on another PC on the same LAN as the host monitor and that's when the error comes editing the same rule trying to the services from the other LAN. So there is no firewall difference from the Host Monitor server and the PC running RCC... and since it works great from the Host Monitor machine itself it shouldn't be a firewall issue unless I have to open up communication ports also to the RCC PC. Doesn't all communication continue to go from the Host Monitor server to the RMA or does the RMA change to communicate with the RCC box when using RCC?

[Yoorix]

What about permissions?
What account do you use to start RCC?

[KS-Soft]

I am running the RCC on another PC
...
So there is no firewall difference from the Host Monitor server and the PC running RCC

Different system has different IP address, right? So, there is difference for the firewall.

shouldn't be a firewall issue unless I have to open up communication ports also to the RCC PC

Of course you have to open port for RCC. RCC connects to the agent, so port should be opened. That's what I am trying to say from begining.

Doesn't all communication continue to go from the Host Monitor server to the RMA or does the RMA change to communicate with the RCC box when using RCC?

RMA does not change behavior, it responds to the requests. If request was sent from HostMonitor, agent responds to HostMonitor. If request was send from RCC, agent respond to RCC.

What about permissions?
What account do you use to start RCC?

It doesn't really matter

Regards
Alex

[guybrush]

I must of missed that, I was under the assumption that the RCC passed the requests to the hostmonitor computer then that computer passed out to the WAN to limit the need to poke more holes....

Thanks for the quick responses, I will give that a try!