TROUBLESHOOTING port connectivity between source and destination

Portqry.exe is a command-line utility that you can use to help troubleshoot TCP/IP connectivity issues. Portqry.exe runs on Windows based computers, on Windows Server 2003/08/12 and Windows Clients XP/7/8.1. The utility reports the port status of TCP and UDP ports on a computer that you select.

Portqry UI by default contains options to check the connectivity for:
·         Domain and trusts
·         IP Sec
·         Networking
·         SQL Server
·         Web Server
·         Exchange Server
·         Net Meeting

In addition, ports can be added manually. Both TCP/UDP ports can be checked using port Qry.

To start the Portqry UI app:

1.       By default portqryUI.exe is located in C:\PortQryUI
2.       Open PortqryUI.exe
3.       Enter destinations IP or FQDN in the “Destination to query” textbox.
4.       Enter the port number or select “Domains and Trusts” or required selection.
5.       Press “Query” button.
6.      Report will be generated under Query Results. 

PortQry reports the status of a TCP/IP port in one of the following three ways:

• Listening: A process is listening on the port on the computer that you selected. Portqry.exe received a response from the port.

• Not Listening: No process is listening on the target port on the target system. Portqry.exe received a response "Destination Unreachable - Port Unreachable" message back from the target UDP port. Or if the target port is a TCP port, Portqry received a TCP acknowledgement packet with the Reset flag set.

• Filtered: The port on the computer that you selected is being filtered. Portqry.exe did not receive a response from the port. A process may or may not be listening on the port. By default, TCP ports are queried three times, and UDP ports are queried one time before a report indicates that the port is filtered.

Return Code analysis: 

• If the return code is 0, it indicates that connection was successful. 

• If return code of 1, it indicates that this DC was unable to communicate on required port. This indicates that server on destination machine is not running or that port is FILTERED on the firewall.

• If return code 2 is normally reported for UDP ports as we don’t get an ACK for that communication. This can be ignored if it’s returned for a UDP port.

Download : http://www.microsoft.com/en-us/download/details.aspx?id=24009

source : http://arnavsharma.net/4/post/2014/05/troubleshooting-using-portqry-ui-tool.html