What problem does it solve?
Diagnose firewall, NAT, listener, and port reachability problems in KKTerm, including blocked SSH, RDP, VNC, HTTP(S), SFTP, custom ports, Windows Firewall, and remote service binding issues.
Core Features & Use Cases
- Identify protocol and port, including defaults only when the user has not provided one: SSH/SFTP 22, RDP 3389, VNC 5900+, HTTP 80, HTTPS 443.
- Distinguish timeout, connection refused, reset, TLS/application error, and authentication failure. They point to different layers.
- Check both sides: client-to-target reachability and whether the target service is actually listening on the expected address and port.
- Consider path controls: Windows Firewall, host firewall, router/NAT, VPN ACL, cloud security group, corporate proxy, and service allowlists.
- Prefer targeted allow rules or service binding fixes. Do not recommend disabling a firewall globally except as a short, explicit, user-approved test in a controlled environment.
- For NAT/port forwarding, verify public/private address, forward target, hairpin NAT expectations, and whether the service is bound to localhost only.
- For "works locally but not remotely," inspect listen address, firewall profile, and network classification before changing application credentials.
- Avoid port scans beyond the named target and small named port set unless the user explicitly authorizes broader discovery.
Quick Start
Describe the visible port issue to KKTerm and let this skill guide you through checks of protocol, port, and firewall settings.
