Purpose Of The TCP Connect Tool
The TCP Connect tool attempts a bounded socket connection to one public host and port. It answers the practical question: can the hublist server open a TCP connection to the address your users will use?
Fields And Controls
- Host Or Address: Public hostname, IP, or hub URL.
- Port: The exact hub listener port. Common values include 411, 412, 1411, 1511, and 4111, but custom ports are valid.
- Timeout: The app uses bounded timeouts so checks cannot hang the web request.
Reading The Results
Open means the port accepted a TCP socket. It does not guarantee the right Direct Connect protocol, so use Protocol Test next. Closed usually means no listener. Timed out usually points to firewall, NAT, provider filtering, or a stopped host.
Common Errors
If ping works but TCP connect fails, focus on firewall and hub service configuration. If TCP works but clients still fail, check protocol type, TLS mode, hub redirects, and minimum client requirements.