I am trying to use the device tools feature remote desktop, and when it launches it tries to connect, the prompt opens up and has an IP of the loopback address 127.0.0.1. Tries to connect and just fails. Can someone help with what settings I need to enable in order to get this to work

Article Comments

Hello,

thank you very much for your KB-Post. Unfortuantely this is a bit tricky. A Probe monitors the host it's running on (so the Probe Device), always via localhost 127.0.0.1. So it doesn't use any "external" IP or hostname. So implicitly it has 127.0.0.1 as IP entered in its settings.
And that's what the device tools / RDP then directly use. I'm afraid the only work-around could be creating a device under the Probe Device (could be empty), with the hostname or "external" IP of the Probe itself, and then use this to establish the RDP-Connection.

best regards.


Jun, 2013 - Permalink

How do I remote access a remote probe that is behind a NAT through the internet?


Jun, 2013 - Permalink

If like my colleague said, you set up a device without any sensors that had the External IP that the Remote Probe is sitting behind, then you would need to NAT the External IP to the internal IP for the Remote Probe server IP for the RDP port (3389). That way when the RDP client tried to connect to that external IP over port 3389 it would be directed to the Remote Probe and initiate the session.


Jun, 2013 - Permalink