TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


general:framework_connection
 

This is an old revision of the document!


Connecting to a TapeTrack Framework Server

Each TapeTrack Framework Server accepts incoming communications on a single TCP/IP port (by default this port is 5000).

These incoming communications are firstly compressed with gzip level 9 compression, and then encrypted with AES 256 bit encryption.

To allow these connections the TapeTrack Framework Server must have firewall access to accept incoming connections, and the connecting clients must have outbound firewall access to establish a single TCP/IP stateful connection.

In the event the connection is terminated, either by a connection fault or the server timing out the connection, a new connection must be established.

In addition to direct TCP/IP connections, the TapeTrack communications API also supports connections via a HTTP Proxy.

Testing your TCP/IP connection

The simplest was to test if you are able to establish a connection to a TapeTrack Framework Server is to use the TMSS10Ping command line utility.

The TMSS10Ping utility simply sends an empty TapeTrack packet and receives a response. It is available for all supported platforms and has no other dependencies.
general/framework_connection.1496789513.txt.gz · Last modified: 2025/01/21 22:07 (external edit)