This article provides information on how to effectively test network connectivity between a local and remote endpoint on specific network ports and protocols. For example: For example: Notes: References: New features and functionality in PortQry version 2.0 http://support.microsoft.com/default.aspx?kbid=832919 How to Make Portqry.exe Only Report Listening Ports http://support.microsoft.com/kb/310513/ How to Use Portqry.exe to Troubleshoot Microsoft Exchange Server Connectivity Issues http://support.microsoft.com/kb/310298/ How to Use Portqry to Troubleshoot Active Directory Connectivity Issues http://support.microsoft.com/kb/310456/ http://support.microsoft.com/kb/310099/ Availability and description of the Port Reporter tool
Several methods are described, including portqry, port reporter and telnet.
Using PortQry.exe 2.0
The PortQry utility provides the flexibility to test any port number or range over TCP and UDP, as well as forcing a local source port and the destination. From a command prompt, run:
Portqry -n server1 -e 135 -v
Portqry -n server2 -e 53 -v -p BOTH
Portqry -n server3 -e 80 -v
Note that in the first example above, if RPC to server1 was not permitted, the result would be 'TCP port 135 (epmap service): FILTERED', whereas if it were allowed, a list of UUID's currently recorded by the endpoint mapper would be returned (also useful information in some cases).
Using telnet.exe
Remote endpoints on a particular TCP port that return a response (such as HTTP, FTP, SMTP etc) can be easily tested with telnet, from a command prompt run:
Telnet server3 80
Using Port Reporter
Locally on the machine:
Wayne's World of IT (WWoIT), Copyright 2008 Wayne Martin.
Information regarding Windows Infrastructure, centred mostly around commandline automation and other useful bits of information.
No comments:
Post a Comment