TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • login_id • introduction • onetimepassword • test_netconnection • ebpf_configuration • attribute_list_values • security_linux • diagnosing_connection_problems • upgrade_server
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 [2025/01/21 22:07] – external edit 127.0.0.1troubleshooting:diagnosing_connection_problems [2025/10/01 02:20] (current) – [Check TapeTrack is listening on port 5000.] Scott Cunliffe
Line 114: 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.
troubleshooting/diagnosing_connection_problems.1737497272.txt.gz · Last modified: 2025/01/21 22:07 by 127.0.0.1