Differences

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

--- general:framework_connection [2018/01/11 00:13] – [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 end point 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.
-------
+\\
-<code>
+\\
-gnicol> nslookup tapetrack.gazillabyte.com
+<code text;>
+jsmith> nslookup tapetrack.gazillabyte.com
 Server:  dc1.gazillabyte.local
 Address:  192.168.1.2
@@ Line 38: / Line 39: @@
 TMSS10Ping installs with TapeTrack software and is stored under (depending on what products are installed):
-<poem>
-TapeMaster        Program Files\TapeTrack\TapeTrack TapeMaster \\
-Lite              Program Files\TapeTrack\TapeTrack Lite \\
-Server Utilities  Program Files\TapeTrack\TapeTrack Server Utilities\bin\tapetrack \\
-</poem>
-Presuming your TapeTrack Framework Server at address **tapetrack.gazillabyte.com**, on port **5000** a successful test would look like this:
-<code>
+**TapeMaster** \\
+  Program Files\TapeTrack\TapeTrack TapeMaster \\
+**Lite**  \\
+ Program Files\TapeTrack\TapeTrack Lite \\
+**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>
+As an example, using TapeTrack Framework Server at address **tapetrack.gazillabyte.com**, on port **5000** a successful test would look like this:
+<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 65: @@
 If TMSS10Ping fails to make a valid connection, try to connect via port 443.
-<code>
+<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 71: / Line 77: @@
 </code>
-If a successful connection cannot be 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 78: / Line 84: @@
 All TapeTrack Command Line programs that communicate with the TapeTrack Framework Server will have a ''-S argument''.
-An example for connecting as user **fred**, with password **secret** is:
+An example for connecting as user **jsmith**, with password **mypassword** is:
-<code>
+<code plain;>
--S fred:-secret@tapetrack.gazillabyte.com
+-S jsmith:-mypassword@tapetrack.gazillabyte.com
 </code>
-For detailed instructions on how to use the ''-S argument'' please see the [[cli:server_argument|Command Line Server Argument]] page.
+For detailed instructions on how to use the ''-S'' argument please see the [[cli:server_argument|Command Line Server Argument]] page.
@@ Line 119: / 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:TMSSAPILOGDIR|TMSSAPILOGDIR]] environmental variable 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>
-Care should be taken to not leave the TMSSAPILOGDIR set as it will slow all TapeTrack Software due to the overhead of logging.
+Care should be taken to not leave the ''TMSSAPILOGDIR'' set as it will slow all TapeTrack Software due to the overhead of logging.
 </note>
-<code>
+<code plain;>
-set TMSSAPILOGDIR=c:\Users\gnicol\Desktop\logs
+set TMSSAPILOGDIR=c:\Users\jsmith\Desktop\logs
 TMSS10Ping localhost
 </code>
@@ Line 132: / Line 138: @@
 Creates the file **TMSSAPILOG-005336.txt** with the contents:
-<code>
+<code plain;>
 :39:25: TMSS10API_Init (API Version=Feb  2 2017 10:18:50)
 :39:25: TMSS10API_Connect: Server(localhost) Port(5000)
@@ Line 147: / Line 153: @@
 </code>
-{{tag>communication environmental_variables}}
+===== See Also =====
+[[technote:setting_environmental_variables|Setting Environmental Variables]]
+{{tag>communication  logging}}