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.
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: how to use portqry
portqry -n dc01 -p tcp -o ldap Other built-in service names: netbios , smtp , http , rpc , sql . This is a PortQry superpower: When a service won’t connect, the first question
PortQry (and its successor, PortQryUI) reports not only if a port is listening, but also which service is behind it. PortQry is a command-line utility that queries a target computer’s TCP and UDP ports. Unlike a basic ping or telnet, PortQry attempts to follow the application protocol (like HTTP, DNS, or NetBIOS) to confirm a service is truly responsive. This is a PortQry superpower: PortQry (and its
TCP port 21 (ftp service): LISTENING TCP port 23 (telnet service): FILTERED TCP port 25 (smtp service): LISTENING portqry -n 8.8.8.8 -p udp -e 53 PortQry sends a DNS query and validates the response. 5. Query a Local Computer portqry -n 127.0.0.1 -p tcp -e 445 Understanding PortQry’s Three Results PortQry reports one of three states: