This guide covers the bounded DC++ port checker, its safe scope, and the difference between an open socket and a working hub protocol.
Usage
- Open Port Scan Tool and enter a public hostname, IP address, or hub URL in Host Or Address.
- Enter up to 20 TCP values in Ports.
- Select Scan Ports and review each row's status, duration, and detail.
Concrete Example
If an NMDC listener moved from port 411 to 1411, check 411,1411. An open 1411 row and a closed 411 row confirm the socket migration from the hublist server's network, but Protocol Test is still needed to identify the service.
Interpretation
Open means a TCP socket was accepted. Closed normally means no listener answered. A timeout can mean packet filtering, bad forwarding, an unreachable host, or an incorrect address. Duration is diagnostic timing, not application performance.
Troubleshooting
- Every Port Times Out: Check DNS Overview, inspect the route with Traceroute, and review the host firewall, VPS rules, and router forwarding.
- Only Secure Port Fails: Check the TLS listener and certificate configuration with TLS Certificate.
- Open But Clients Fail: Verify NMDC, NMDCS, ADC, or ADCS with Protocol Test.
- Scope: This is not a vulnerability scanner; keep the list limited to your hub-related ports.
Icon Reference
| Icon | Label | What It Does |
|---|---|---|
| Scan Ports | Scan Ports submits the public host and bounded port list. | |
| Complete | Complete marks a finished set of TCP port attempts. | |
| Review Output | Review Output marks closed, timed-out, or mixed rows that need follow-up. | |
| Open Help | Open Help opens this guide from the Port Scan panel. |