Differences

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

--- troubleshooting:diagnosing_connection_problems [2021/09/01 01:28] – [Check TapeTrack Service is running] Scott Cunliffe
+++ troubleshooting: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 wont start see [[troubleshooting:Rebuild Database Environment Files]].
+If the Framework Server still wont start see [[server:reload|Reloading Server]]
 ==== Linux  ====
@@ Line 66: / Line 69: @@
 =====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>
 C:\WINDOWS\system32>TMSS10Ping localhost
+</code>
+Successful connection will return packets and display as shown below.
+<code>
 bytes from 127.0.0.1: seq=1 time=6.00 ms
 bytes from 127.0.0.1: seq=2 time=0.00 ms
@@ Line 80: / Line 91: @@
 </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.=====
 <code>
@@ Line 94: / Line 114: @@
 . TMSS10Ping was blocking (hanging). \\
 . 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.
 If you do not have access to change the Windows Firewall rules check with your Windows Admin team.
+{{tag> server troubleshooting connection }}