This guide explains how the selected NMDC, NMDCS, ADC, or ADCS transport is tested without confusing socket success with a full login.
Usage
- Open Protocol Test and enter the public hostname or hub URL in Host Or Address.
- Select the Protocol: dchub/NMDC, NMDCS, ADC, or ADCS.
- Leave TCP Port empty for the configured common default or enter the exact advertised port.
- Select Test Hub Protocol.
Concrete Example
To check nmdcs://secure.example.net:1411, choose NMDCS and port 1411. A successful TLS socket is the primary reachability result. A returned NMDC lock, hub name, or other immediate banner is extra evidence that the expected hub service answered.
Interpretation
For NMDC or ADC, the primary result is TCP acceptance. For NMDCS or ADCS, it is TLS acceptance. Banner and greeting rows provide additional protocol evidence when the service sends data immediately. Some valid hubs wait for client input, so no immediate banner is not failure by itself.
Troubleshooting
- Protocol Mismatch: Do not send plaintext to a TLS listener or TLS to a plaintext listener.
- Timeout: Check DNS Overview, inspect routing with Traceroute, test the socket with TCP Connect, and review the firewall, NAT, and running hub process.
- Force Move: Verify whether the returned destination is an intended redirect.
- Registration Required: Reachability can succeed even when guest login is restricted.
Icon Reference
| Icon | Label | What It Does |
|---|---|---|
| Test Hub Protocol | Test Hub Protocol submits one public endpoint, protocol, and port. | |
| Complete | Complete marks successful TCP or TLS acceptance. | |
| Review Output | Review Output marks a banner, redirect, restriction, or failed transport needing context. | |
| Open Help | Open Help opens this guide from the Protocol Test panel. |