# TCP ports on a master server

22: SSH Daemon

  Port 22 is not used by ThinLinc per se, but since no ThinLinc installation can work without a running SSH daemon, we list port 22 here. Port 22 is the normal SSH port, but basically any port can be used — the client has support for connecting to any port. Note that if the SSH daemon on the master server is listening on port x, all agent servers must also have their SSH daemons configured to listen on port x.

300: ThinLinc Web Access (`tlwebaccess.service`)

  By default, ThinLinc’s browser client is available on TCP port 300. Traffic to this port is encrypted (TLS).

  Note

  The port on which tlwebaccess runs is configurable via the parameter `/webaccess/listen_port`. See Parameters in /webaccess/ for details.

1010: ThinLinc web administration interface (`tlwebadm.service`)

  By default, ThinLinc’s web-based administration interface is available on TCP port 1010. In order to access this interface remotely, port 1010 will need to be reachable. Traffic to this port is encrypted (TLS).

  Note

  The port on which tlwebadm runs is configurable via the parameter `/tlwebadm/listen_port`. See Parameters in /tlwebadm/ for details.

9000: Master service (`vsmserver.service`)

  The master service listens on port 9000. The traffic is not encrypted, but sensitive information will only be shared with root or connections originating from a port lower than 1024, from a list of known IP addresses.