Differences

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

--- troubleshooting:diagnosing_connection_problems [2021/09/01 01:57] – [Ping with TMSS10Ping] Scott Cunliffe
+++ troubleshooting:diagnosing_connection_problems [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ 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=====
-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>
@@ Line 93: / Line 96: @@
 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 111: / Line 118: @@
 If you do not have access to change the Windows Firewall rules check with your Windows Admin team.
+{{tag> server troubleshooting connection }}