Purpose Of The Protocol Test Tool
The Protocol Test tool attempts a low-impact connection using the selected Direct Connect protocol. It helps confirm that a public endpoint is not merely open, but responding like a DC++ hub for NMDC, NMDCS, ADC, or ADCS.
Fields And Controls
- Protocol: Choose dchub/NMDC, NMDCS, ADC, or ADCS based on the address users should connect to.
- Port: Leave empty for the common default or enter the exact advertised port.
- Host Or Address: Use the same hostname or hub URL clients will use.
Reading The Results
A successful TCP/TLS connection means the socket opened. A returned lock, banner, hub name, or ADC greeting gives stronger evidence that the hub protocol is correct. No banner can still be normal for some services, so compare with chat, TCP connect, and port scan checks.
Common Errors
- Protocol Mismatch: A plaintext test against a TLS port, or a TLS test against a plaintext port.
- Force Move: The hub accepted a connection but redirected the client to another address.
- Registration Required: The hub responds, but guest login is restricted.
- Timeout: The socket did not complete before the bounded limit.