![Gira 2089 00 Configuration Download Page 58](http://html1.mh-extra.com/html/gira/2089-00/2089-00_configuration_2228998058.webp)
Gira S1 Windows client
Order No. 2089 00
Page 58
10.3.3. Using other TCP protocols via remote access
Using the settings in “TCP remote access connections”, you can use other TCP-based IP protocols via
remote access. To do so, click “Add” and enter the corresponding values for the remote access.
For example, the Microsoft Remote Desktop Protocol (RDP), which is used by the Microsoft Remote
Desktop connection application, is wellknown. Here, too, the port is usually already used locally by
the computer, which is why the translation to a port is required, as in the example in the figure below.
Figure 25: TCP remote access configuration.
Note: Often, you can no longer use the TCP port which must be addressed on the device on the remote
network (in this example, 3389, the default port for RDP) on your computer, for example, because you
have installed software on your computer which is already using this port. In this case, you must find
another available port. It can help to use ports starting with 40000 here (as in our example).
If you now want to establish a remote desktop connection to the target computer via remote access
(in our example, “computername”), you still have to enter the port if it does not correspond to the
default port.
In our example, the connection can be established as
follows:
Note: It is common syntax for the explicit specification
of a port to write the port with a preceding ":" directly
after the host name (only required if it is not the default
port). With HTTP, e.g. http://127.0.0.1:40003/
index.html.
Protocols such as Telnet and SSH can also easily be
used via SDA.