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/02 00:09] – [Ping with TMSS10Ping] 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 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. |
troubleshooting/diagnosing_connection_problems.1630541367.txt.gz · Last modified: 2025/01/21 22:07 (external edit)