TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • database_message_files
troubleshooting:diagnosing_connection_problems

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
troubleshooting:diagnosing_connection_problems [2021/09/01 01:26] – [Windows] Scott Cunliffetroubleshooting:diagnosing_connection_problems [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 2: Line 2:
  
 =====Check  TapeTrack Service is running===== =====Check  TapeTrack Service is running=====
 +
 +Check the status of the TapeTrack Framework Server by running the following commands (operating system dependant) directly from the server the TapeTrack is installed on.
  
 ==== Windows ==== ==== Windows ====
Line 40: Line 42:
 If the Framework Server is not running, attempt to [[server:start_stop|start the Framework Server]] and then check your connection again.    If the Framework Server is not running, attempt to [[server:start_stop|start the Framework Server]] and then check your connection again.   
  
 +If the Framework Server wont start see [[troubleshooting:Rebuild Database Environment Files]].
 +
 +If the Framework Server still wont start see [[server:reload|Reloading Server]]
 ==== Linux  ==== ==== Linux  ====
    
Line 64: Line 69:
 =====Ping with TMSS10Ping===== =====Ping with TMSS10Ping=====
  
-Ping the TapeTrack Framework Server with TMSS10Ping, using localhost if run on the same server or the IP or DNS of the server if run from another computer. +If the TapeTrack Framework Server is running, use [[cli:tmss10ping|TMSS10Ping]] to check the connection to the server. 
- + 
 +Ping the TapeTrack Framework Server with [[cli:tmss10ping|TMSS10Ping]], using localhost on the server that TapeTrack Framework Server is installed on with: 
 <code> <code>
 C:\WINDOWS\system32>TMSS10Ping localhost C:\WINDOWS\system32>TMSS10Ping localhost
 +</code>
 +
 +Successful connection will return packets and display as shown below.
 +
 +<code>
 +
 44 bytes from 127.0.0.1: seq=1 time=6.00 ms 44 bytes from 127.0.0.1: seq=1 time=6.00 ms
 44 bytes from 127.0.0.1: seq=2 time=0.00 ms 44 bytes from 127.0.0.1: seq=2 time=0.00 ms
Line 78: Line 91:
 </code> </code>
  
 +Unsuccessful connection returns
 +
 +<code>
 +TMSS10Ping: Connect to TapeTrack Server failed: WSAError(10061)
 +</code>
 +
 +An unsuccessful connection from the computer TapeTrack Framework Server is installed on (localhost), while the TapeTrack Framework Server is running, suggests a port problem and should be referred to your network department to remedy the problem.
 +
 +A successful connection from localhost but not from client computers suggests a firewall issue not letting TapeTrack communications through and should be referred to your network department to remedy the problem.
 =====Check TapeTrack is listening on port 5000.===== =====Check TapeTrack is listening on port 5000.=====
 <code> <code>
Line 96: Line 118:
  
 If you do not have access to change the Windows Firewall rules check with your Windows Admin team. If you do not have access to change the Windows Firewall rules check with your Windows Admin team.
 +
 +{{tag> server troubleshooting connection }}
troubleshooting/diagnosing_connection_problems.1630459580.txt.gz · Last modified: 2025/01/21 22:07 (external edit)