Incontrol2-Server behind NAT - Remote Web Admin does not start

Hi!

I am trying to setup Incontrol2 as VM behind NAT.
TCP 5246 and UDP 5246 are forwarded to the VM.

The Peplink Balance routers are visible in Incontrol and reporting their state, but: Remote Web Admin does not work.

Contacting the device …
Connection timeout, please try again later

→ Can you give me a hint, what I did forget?

Thank you for your help!

Regards,
KPS

Please double check if the inbound TCP 5246 is properly forwarded. If you “nc” or “telnet” to port 5246 on the ICA’s public IP from external, you should see a greeting message like “SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.4”.

Hi!

This is working, but RA, does not:

telnet XXX.XXX.XXX.XXX 5246 Trying XXX.XXX.XXX.XXX... Connected to XXX.XXX.XXX.XXX. Escape character is '^]'. SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.4

If you’re sure the device’s outgoing port 5246 to the ICA is not blocked, please enable Remote Assistance on the ICA’s control panel page and DM me its s/n. Let me check for you remotely.

1 Like

Hi Michael!

Did you see anything on the system?

Please check my DM I sent yesterday.

1 Like

Hi!

Michael solved the problem.
The issue was:

The Peplink Router does not connect to Port 5246 of the IP, I entered for Incontrol - it uses Incontrols DNS name which was not public.

2 Likes