troubleshooting:diagnosing_connection_problems
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| troubleshooting:diagnosing_connection_problems [2021/09/01 03:55] – [Check TapeTrack is listening on port 5000.] 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: | If the Framework Server is not running, attempt to [[server: | ||
| + | If the Framework Server wont start see [[troubleshooting: | ||
| + | |||
| + | If the Framework Server still wont start see [[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: |
| - | 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: |
| < | < | ||
| Line 111: | 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 | ||
| + | |||
| + | < | ||
| + | Test-NetConnection your-server.com -Port 5000 | ||
| + | </ | ||
| + | |||
| + | Output: | ||
| + | |||
| + | < | ||
| + | PS C:\> Test-NetConnection yourserverk.com -P 5000 | ||
| + | |||
| + | ComputerName | ||
| + | RemoteAddress | ||
| + | RemotePort | ||
| + | InterfaceAlias | ||
| + | SourceAddress | ||
| + | PingSucceeded | ||
| + | PingReplyDetails (RTT) : 221 ms | ||
| + | TcpTestSucceeded | ||
| + | </ | ||
| This is most definitely a Firewall problem. | This is most definitely a Firewall problem. | ||
| Line 116: | Line 140: | ||
| 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 | + | {{tag> server |
troubleshooting/diagnosing_connection_problems.1630468516.txt.gz · Last modified: 2025/01/21 22:07 (external edit)
