remote.it lets you make secure remote connections to TCP or UDP based services on your device. Most users start with a remote.it SSH Connection to port 22, which gives you remote console access.
You can also install remote.it Services for:
-
http based web server or application (default port 80)
-
https based web server or application (default port 443)
-
VNC server (Virtual Network Console, a remote graphical desktop system) (default port 5900)
-
nxWitness (remote video application) on port 7001
-
any other TCP or UDP based service on any port
The remote.it installer does not install or manage any of the server applications listed above. Most systems at least support SSH and SCP (secure remote console and file transfer) by default. Beyond that you will usually have to install the application yourself.
The Raspberry Pi uses the "raspi-config" program to enable or disable SSH and VNC.
sudo raspi-config
Next you can enable or disable SSH or VNC.
We recommend that you not disable SSH, and you can use VNC if you want to have access to the graphical desktop. By default Raspbian Stretch or later installs RealVNC server on port 5900.
You can also enable SSH at the time you create the SD card image by creating a file called "ssh" in the boot folder.
We define a "Network/LAN Application" as a TCP or UDP service that is running on a different device on your LAN. For example, the web UI on your router is an example of a "LAN application". Using the "LAN Application" option allows you to access TCP or UDP servers on your LAN without needing to install the remote.it connectd package on the device itself.
For a LAN application, you will need to know the device's IP address (which should be static or otherwise fixed, for example using "DHCP Reservation" or a similar feature on your router. Another possibility is to use mdns (aka Bonjour).
On most Linux systems, you can use the following command to show active TCP servers on the local device which you can connect to.
For TCP:
sudo netstat -lpn | grep tcp
For UDP:
sudo netstat -lpn | grep udp
Lines beginning with tcp or udp represent ipV4 services, while those marked tcp6 or udp6 are compatible with ipV6.
For ipV4 servers, the port is indicated by:
<interface>:port
<interface> might represent a specific hardware interface on the device. Most often it is set to "0.0.0.0" which means "all interfaces".
Usually, there is a line corresponding to an application for both tcp and tcp6. In this example, all of the applications just above have matching entries in tcp6. Sometimes, as in this case with "xrdp", you will see a port assignment for tcp6 that is not matched by one for tcp. However, the tcp (ipV4) server is in fact available. To be sure, you can try connecting to this port using your device's IP address on the LAN (that is, without using remote.it).
These are the port numbers that you will need to use when configuring remote.it Services.
Open an Administrator Command Prompt, then run PowerShell in order to run the following commands.
To scan for active TCP listeners on a given port:
Get-NetTCPConnection -State Listen -LocalPort <port>For example, let's use port 25565 which is used for the Minecraft Server Java version.
Note the number in the rightmost column. This is the Process ID. To get the name of the application which corresponds to this process ID, run:
Get-Process -Id <process ID>
For example, let's use process ID 5552:
The returned Process Name is java, which is what we expect for Minecraft Java version.
To scan for active UDP listeners:
Get-NetUDPEndpoint -LocalAddress 0.0.0.0 | Sort-Object LocalPort
To scan for active UDP listeners on a given port:
Get-NetUDPEndpoint -LocalAddress 0.0.0.0 -LocalPort <port>
The output of the Get-NetUDPEndpoint command does not include the process ID allowing you to double check the application name. However, it should still let you know whether there is a UDP listener on a given port.