Host monitor will not monitor traffic

[emaika]

Hi, I have been trying to get a Traffic monitor to work from our application server to monitor another server. It is host monitor 7.22c, and when i run the test i receive the error "RMA: 301 - An existing connection was forcibly closed by the remote host".

I have tried setting the agent as a service, a passive RMA and an active RMA. When it is set up as passive RMA and i refresh the test it says "Connection established" (but still a 301 error on the HM side). When it is set up as an active RMA it says "Connected to HM" but then says "Traffic Monitor test .. error"

I have tried all the suggestions in the topic "RMA: 301 - Cannot retrieve information - Process test" at
http://www.ks-soft.net/cgi-bin/phpBB/vi ... php?t=2687

Do you have any suggestions, or is there anywhere I can look for more details about what the error could be? Thanks!

[KS-Soft]

I have tried all the suggestions in the topic "RMA: 301 - Cannot retrieve information - Process test" at
http://www.ks-soft.net/cgi-bin/phpBB/vi ... php?t=2687

Traffic Monitor and Process are completely different tests. Traffic Monitor uses SNMP protocol while Process test uses RPC calls and remote registry service.

I have tried setting the agent as a service, a passive RMA and an active RMA.

It does not matter what agent or application/service mode do you use in this case. I don't think this problem is related to our software.

1) you should check is SNMP agent started on target system
2) please check that no firewall or antivirus blocks requests (UDP port 161) from RMA system to target system
3) make sure SNMP agent does not have access restrictions (may be it accepts requests from some specific IP addresses only)
4) please make sure you have specified correct community string for the test (username and password if you are using SNMP v3). These options located in SNMP Credentials dialog (you may open this dialog when setup SNMP Get or Traffic Monitor test item)

Also, it can be timeout related issue. Make sure you do not have specified too short timeout interval for the agent (Agent Connection Parameters dialog)

Regards
Alex