KS-Soft

I have installed the RMA now and the Daemon is running OK.

However, despite the remote IP address being in the rma.ini file I get a failed connection in the RMA manager.

Is there any way of running a test on the RMA through SSH just to make sure that the problem is to do with open ports rather than the RMA?

Thanks.

rapport_ralph wrote:However, despite the remote IP address being in the rma.ini file I get a failed connection in the RMA manager.

Could you set the FilterActive=0 value in [IncomeFilter] section in rma.ini? Just for testing? Please note: you should restart rma in order to apply changes.

rapport_ralph wrote:Is there any way of running a test on the RMA through SSH just to make sure that the problem is to do with open ports rather than the RMA?

Sorry, RMA does not support SSH protocol. Please ensure the port, you have specified in rma.ini, is opened by firewall on the machine, where rma is running.

Regards,
Max

Hi,

It is already set to filteractive I just realised. Sorry.

Does it works now?

Regards
Alex

No,

It was already on filteractive=0 before when I tried it. It still doesn't work now

rapport_ralph wrote:It was already on filteractive=0 before when I tried it. It still doesn't work now

The port, you have specified in rma.ini, should be opened by firewall on the machine, where RMA is running. If firewall blocks connection to this port, you will not be able to connect to the agent from outside.
Could you also send rma.ini to support@ks-soft.net?

Regards,
Max

Is there any way of running a test on the RMA through SSH just to make sure that the problem is to do with open ports rather than the RMA?

You may check RMA log files or start RMA in interactive mode using -i option. If output on screen looks like
====================
Command line checking .. Ok
Settings checking .. Ok
CPU testing .. Ok
Basic encyption checking .. Ok
RMA encyption checking .. Ok
Sock testing .. Ok
Listening...
====================
and nothing else happens when you are trying to connect to the agent, then I see 2 possible reasons of the problem
1) network problem (e.g. firewall block the port)
2) or you have used wrong IP address and/or port when setup RMA record for RMA Manager

If RMA receives connects from RMA Manager and shows some messages on screen, please check what exactly RMA is trying to say.

Regards
Alex

Hi,

This was my fault sorry. I had added port 1055 to iptables but had not realised our firewall restart option flushes the rules before restarting.

It is all working fine now thanks.

You are welcome

Regards
Alex