Article ID: 310456 - View products that this article applies to.
This article was previously published under Q310456
Portqry is a command-line utility that you can use to help troubleshoot TCP/IP connectivity issues, which you can run on Windows 2000 and Windows XP. The utility reports the port status of target Transition Control Protocol (TCP) and User Datagram Protocol (UDP) ports on a remote computer.
You can also use Portqry in the following ways:
Note Version 2 of Portqry.exe is now available. The Microsoft Download Center link at the end of this article has been updated to reflect the new version. Version 1.0 of Portqry.exe has been removed from the Microsoft Download Center.
Portqry reports the status of a port in one of three ways:
ExampleWhen you run the following command:
portqry -n myserver -p udp -e 389Portqry automatically resolves UDP port 389 using the %SystemRoot%\System32\Drivers\...\Services file that every Windows 2000 and Windows XP system has by default. If it resolves the port to the LDAP service, it sends an unformatted user datagram to UDP port 389 on the target system. Portqry will not receive a response from the port as the LDAP service only responds to a properly formatted LDAP query. Portqry will report that the port is listening or filtered. Portqry will then send a properly formatted LDAP query to UDP port 389. If it receives a response to the query, it returns the entire response to the user and report that the port is listening. If portqry does not receive a response to the query, it reports that the port is filtered.
In this sample, port 389 is listening and from the output it can be determined which LDAP service is listening on the port and some details about its configuration. This information may also be useful in troubleshooting various problems.
C:\>portqry -n mydc.reskit.com -e 389 -p udp Querying target system called: mydc.reskit.com Attempting to resolve name to IP address... Name resolved to 169.254.0.14 UDP port 389 (unknown service): LISTENING or FILTERED Sending LDAP query to UDP port 389... LDAP query response: currentdate: 10/11/2001 23:10:21 (unadjusted GMT) subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=reskit,DC=com dsServiceName: CN=NTDS Settings,CN=mydc,CN=Servers,CN=eu,CN=Sites,CN =Configuration,DC=reskit,DC=com namingContexts: DC=reskit,DC=com defaultNamingContext: DC=reskit,DC=com schemaNamingContext: CN=Schema,CN=Configuration,DC=reskit,DC=com configurationNamingContext: CN=Configuration,DC=reskit,DC=com rootDomainNamingContext: DC=reskit,DC=com supportedControl: 1.2.840.1135188.8.131.529 supportedLDAPVersion: 3 supportedLDAPPolicies: MaxPoolThreads highestCommittedUSN: 815431405 supportedSASLMechanisms: GSSAPI dnsHostName: MYDC.reskit.com ldapServiceName: reskit.com:mydc$@RESKIT.COM serverName: CN=MYDC,CN=Servers,CN=EU,CN=Sites,CN=Configuration,DC=reskit,DC=com supportedCapabilities: 1.2.840.1135184.108.40.2060 isSynchronized: TRUE isGlobalCatalogReady: TRUE ======== End of LDAP query response ======== UDP port 389 is LISTENING
Portqry knows how to send a query to the RPC end point mapper (using UDP and TCP) and interpret the response. This query will dump all of the end points currently registered with the RPC end point mapper. The response from the end point mapper is parsed, formatted and returned to the user.
ExampleWhen you run the following command:
portqry -n mydc.reskit.com -p udp -e 135
In this example, port 135 is listening and from the output it can be determined which services or applications have been registered with the target server's RPC end point mapper database. The output includes each application's Universally Unique Identifier (UUID), annotated name (if one exists), the protocol the application uses, the network address that the application is bound to, and the application's end point (port number, named pipe, and so forth, in square brackets). This information may also be useful in troubleshooting various problems.
Querying target system called: mydc.reskit.com Attempting to resolve name to IP address... Name resolved to 169.254.0.18 UDP port 135 (epmap service): LISTENING or FILTERED Querying Endpoint Mapper Database... Server's response: UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncacn_np:\\\\MYDC[\\PIPE\\lsass] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncacn_np:\\\\MYDC[\\PIPE\\lsass] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncacn_ip_tcp:169.254.0.18 UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service ncacn_ip_tcp:169.254.0.18 UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API ncacn_ip_tcp:169.254.0.18 UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API ncacn_np:\\\\MYDC[\\pipe\\00000580.000] Total endpoints found: 6 ==== End of RPC Endpoint Mapper query response ==== UDP port 135 is LISTENING
Portqry can send a properly formatted DNS query (using UDP or TCP). The utility will send a DNS query for "portqry.microsoft.com." Portqry then waits for a response from the target DNS server. Whether the DNS response to the query is negative or positive is irrelevant since any response indicates that the port is listening.
Portqry.exe is available for download from the Microsoft Download Center. To download Portqry.exe, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=89811747-C74B-4638-A2D5-AC828BDC6983&displaylang=enImportant The PortQueryUI tool provides a graphical user interface is available for download. PortQueryUI has several features that can make using PortQry easier. To obtain the PortQueryUI tool, visit the following Microsoft Web site:
Article ID: 310456 - Last Review: February 21, 2007 - Revision: 4.3
Contact us for more help
Connect with Answer Desk for expert help.