N-central Troubleshooting
Remote Desktop (RDP), SSH, and custom remote control types fail to connect - connection could not be established
Last Modified
Mon Oct 08 19:19 GMT 2018
Description
The connection could not be established. Select "Try Again" to restart the timer.remote_control_connector.log in the technician deviceWARNING [Oct 05, 2018 - 11:11:57 PM]registeredWithServer:false readyToAcceptConnections:trueWARNING [Oct 05, 2018 - 11:11:57 PM]Test UI tunnel result: falseINFO [Oct 05, 2018 - 11:11:57 PM]SSH & HTTPS Available but no UDPWARNING [Oct 05, 2018 - 11:11:57 PM]Testing Tunnel: Handshake Ok ? false
Environment
- N-able N-central 10 or later
Solution
- These types of remote control require access to the N-able N-central server on port 443. If you are using port forwarding/custom port to access your N-able N-central login page, then RDP and any others using this JNLP/JRCC method will not work.
- Reference: DSRC-361