TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • log_file • qr-code • assign_to_slot • sort_sequence • file_structure • version • diagnosing_connection_problems • upgrade_server • control_panel • introduction
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:57] – [Ping with TMSS10Ping] Scott Cunliffetroubleshooting:diagnosing_connection_problems [2025/10/01 02:20] (current) – [Check TapeTrack is listening on port 5000.] Scott Cunliffe
Line 42: 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 66: Line 69:
 =====Ping with TMSS10Ping===== =====Ping with TMSS10Ping=====
  
-If the TapeTrack Framework Server is running, use TMSS10Ping to check the connection to the server.+If the TapeTrack Framework Server is running, use [[cli:tmss10ping|TMSS10Ping]] to check the connection to the server.
  
-Ping the TapeTrack Framework Server with TMSS10Ping, using localhost on the server that TapeTrack Framework Server is installed on with:+Ping the TapeTrack Framework Server with [[cli:tmss10ping|TMSS10Ping]], using localhost on the server that TapeTrack Framework Server is installed on with:
  
 <code> <code>
Line 93: Line 96:
 TMSS10Ping: Connect to TapeTrack Server failed: WSAError(10061) TMSS10Ping: Connect to TapeTrack Server failed: WSAError(10061)
 </code> </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 107: Line 114:
 2. TMSS10Ping was blocking (hanging). \\ 2. TMSS10Ping was blocking (hanging). \\
 3. TapeTrack was on port 5000, which means it was up and listening. 3. TapeTrack was on port 5000, which means it was up and listening.
 +
 +Or alternatively use Powershell commandlet Test-NetConnection
 +
 +<code>
 +Test-NetConnection your-server.com -Port 5000
 +</code>
 +
 +Output:
 +
 +<code>
 +PS C:\> Test-NetConnection yourserverk.com -P 5000
 +
 +ComputerName           : yourserver.com
 +RemoteAddress          : XXX.XXX.XXX.XXX 
 +RemotePort             : 5000 
 +InterfaceAlias         : Wi-Fi 
 +SourceAddress          : XXX.XXX.XXX.XXX 
 +PingSucceeded          : True
 +PingReplyDetails (RTT) : 221 ms
 +TcpTestSucceeded       : False  
 +</code>
  
 This is most definitely a Firewall problem. This is most definitely a Firewall problem.
  
 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.1630461446.txt.gz · Last modified: 2025/01/21 22:07 (external edit)