Differences

This shows you the differences between two versions of the page.

--- general:framework_connection [2019/08/01 23:14] – [Testing your TCP/IP connection] Scott Cunliffe
+++ general:framework_connection [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 3: / Line 3: @@
 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.
+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.
@@ Line 11: / Line 11: @@
 In addition to direct TCP/IP connections, the TapeTrack communications API also supports connections via a HTTP Proxy.
-====== Names and IP addresess ======
+====== Names and IP addresses ======
-As with all TCP/IP connections, the endpoint address can be represented by either a name or dotted IP address.
+As with all TCP/IP connections, the endpoint address can be represented by either a domain name or dotted IP address.
-It is recommended that you always use a name, rather than dotted IP address to connect to your TapeTrack server as this contemplates a future change in IP address.
+It is recommended that you always use a domain name, rather than dotted IP address to connect to your TapeTrack server as this contemplates a future change in IP address.
-<note tip>If you are using a name to connect to your TapeTrack Server and can not connect, you should check to ensure that your name is resolving to an IP address.
+<note tip>If you are using a domain name to connect to your TapeTrack Server and can not connect, you should check to ensure that your domain name is resolving to an IP address.
 \\
 \\
-<sxh text;>
+<code text;>
 jsmith> nslookup tapetrack.gazillabyte.com
 Server:  dc1.gazillabyte.local
@@ Line 28: / Line 28: @@
 Name:    tapetrack.gazillabyte.com
 Address:  192.241.211.124
-</sxh>
+</code>
 </note>
@@ Line 46: / Line 46: @@
 **Server Utilities**  \\
  Program Files\TapeTrack\TapeTrack Server Utilities\bin\tapetrack \\
+<note tip>Examples shown use fictional values.  Replace domain name with the actual value you want to check the connection on</note>
-Presuming your TapeTrack Framework Server at address **tapetrack.gazillabyte.com**, on port **5000** a successful test would look like this:
+As an example, using TapeTrack Framework Server at address **tapetrack.gazillabyte.com**, on port **5000** a successful test would look like this:
-<sxh plain;>
+<code plain;>
 [root@documentation-us conf]# TMSS10Ping -P 5000 tapetrack.gazillabyte.com
 bytes from 192.241.211.124: seq=1 time=0.00 ms
@@ Line 59: / Line 61: @@
 packets transmitted
 round-trip min/avg/max = 0.00/0.00/0.00 ms
-</sxh>
+</code>
 If TMSS10Ping fails to make a valid connection, try to connect via port 443.
-<sxh plain;>
+<code plain;>
 [root@documentation-us conf]# TMSS10Ping -P 443 tapetrack.gazillabyte.com
 bytes from 192.241.211.124: seq=1 time=0.00 ms
@@ Line 73: / Line 75: @@
 packets transmitted
 round-trip min/avg/max = 0.00/0.00/0.00 ms
-</sxh>
+</code>
-If a connection cannot be successful completed through either port contact your network administrator to ensure ports are open.
+If a connection cannot be successfully completed through either port contact your network administrator to ensure ports are open.
 ===== Connecting via TapeTrack Software =====
@@ Line 84: / Line 86: @@
 An example for connecting as user **jsmith**, with password **mypassword** is:
-<sxh plain;>
+<code plain;>
 -S jsmith:-mypassword@tapetrack.gazillabyte.com
-</sxh>
+</code>
 For detailed instructions on how to use the ''-S'' argument please see the [[cli:server_argument|Command Line Server Argument]] page.
@@ Line 123: / Line 125: @@
 All TapeTrack programs use an underlying low level communications API which allows users to trace connection and communications requests.
-To enable logging, set the [[variable:start|environmental variable]] [[variable:TMSSAPILOGDIR|TMSSAPILOGDIR]] to the path of an existing directory.
+To enable logging, set the [[variable:start|Environmental Variable]] [[variable:TMSSAPILOGDIR|TMSSAPILOGDIR]] to the path of an existing directory.
 <note important>
@@ Line 129: / Line 131: @@
 </note>
-<sxh plain;>
+<code plain;>
 set TMSSAPILOGDIR=c:\Users\jsmith\Desktop\logs
 TMSS10Ping localhost
-</sxh>
+</code>
 Creates the file **TMSSAPILOG-005336.txt** with the contents:
-<sxh plain;>
+<code plain;>
 :39:25: TMSS10API_Init (API Version=Feb  2 2017 10:18:50)
 :39:25: TMSS10API_Connect: Server(localhost) Port(5000)
@@ Line 149: / Line 151: @@
 :39:25: TMSS10API_Send: RC(Request OK) Feedback(0) MilliSecs(0) Avail(0) Count(0) Length(0)
 :39:25: TMSS10API_Term
-</sxh>
+</code>
 ===== See Also =====
-[[technote:setting_environmental_variables|Setting environmental variables]]
+[[technote:setting_environmental_variables|Setting Environmental Variables]]
-{{tag>communication environmental_variables logging}}
+{{tag>communication  logging}}