How To | Use Portqry

HTTP response: 200 OK portqry -n server01 -p tcp -e 3389 3. Scan a Range of Ports portqry -n 10.0.0.25 -p tcp -r 20..25 Output:

When a service won’t connect, the first question is often: “Is the port even open?” While tools like telnet and Test-NetConnection work, PortQry offers a more detailed, faster, and scriptable alternative—especially for Windows administrators. how to use portqry

TCP port 80 (http service): LISTENING If the web server returns an HTTP response, you might also see: HTTP response: 200 OK portqry -n server01 -p tcp -e 3389 3

| Result | Meaning | |--------|---------| | | A service is bound to the port and responded. | | FILTERED | No response received (firewall drop, host down, or no service). | | NOT LISTENING | Reached the host, but no service on that port (RST received). | Pro tip: FILTERED does not always mean a firewall—the service may be stopped or the IP unreachable. Advanced: Query Well-Known Services PortQry can query specific service endpoints like LDAP, NetBIOS, or SQL Server using the -o flag with known service names: | | FILTERED | No response received (firewall