Software development, .Net, SQL Server, TDD, Agile, Community and other Odds and Sods
Mitch Wheat has been working as a professional programmer since 1984, graduating with a honours degree in Mathematics from Warwick University, UK in 1986. He moved to Perth in 1995, having worked in software houses in London and Rotterdam. He has worked in the areas of mining, electronics, research, defence, financial, GIS, telecommunications, engineering, and information management. Mitch has worked mainly with Microsoft technologies (since Windows version 3.0) but has also used UNIX. He holds the following Microsoft certifications: MCPD (Web and Windows) using C# and SQL Server MCITP (Admin and Developer). His preferred development environment is C#, .Net Framework and SQL Server. Mitch has worked as an independent consultant for the last 10 years, and is currently involved with helping teams improve their Software Development Life Cycle. His areas of special interest lie in performance tuning
Saturday, June 13, 2009
Troubleshoot SQL Server Connectivity Problems: PortQryUI
If you want a quick and easy way to check SQL Server connectivity, without resorting to the full blown functionality of WireShark (or similiar), you can use Microsoft's PortQryUI utility to troubleshoot TCP/IP connectivity problems. PortQryUI is a GUI on top of the PortQry command line tool, with predefined groups of ports to scan. One of the these groups targets SQL Server, which consists of UDP port 1434 and TCP port 1433. To check these ports, enter the IP address (or fully qualified domain name) of the target SQL Server instance, select SQL Service in the 'Service to Query' drop-down box and click the Query button.
If the ports are OK, the utility will list the ports as Listening. Otherwise, it will tell you the ports are being Filtered or are Not Listening.
You can download PortQryUI from here: PortQryUI - User Interface for the PortQry Command Line Port Scanner.
MSN, Email: mitch døt wheat at gmail.com