I am frequently troubleshooting problems in a Windows Command Prompt.  There are some functions which can be tested at a very basic level.  For example, if I am unable to connect to a server via Windows Explorer, I might jump into a command prompt and try to ping the server. 

    ping [servername]


    Lots of applications for this simple command.  Yesterday, I was troubleshooting a SQL connection issue and even though I had enabled TCP/IP in protocols, I was still unable to make a connection.  As a sanity check, I ran a shortened version of the command below which showed me that 1433 was not open and ultimately brought me to the source of the problem. 

    Launch a Command Prompt as the administrator (right click, CMD, select Run As Administrator).

    Enter the following command:


    In a previous post, I explained how to disable the Windows 7 firewall and leave it to Microsoft to change how an operation is performed.

    Like the previous post, there are times when I don't want the firewall in the way of troubleshooting a problem.  The following is how to disable it.

    From a Command Prompt run as the administrator, enter the following:


    Life was simple with Exchange 2003 but as life goes on, newer versions of Exchange have appeared and what was once simple has become a bit more complicated.

    One of the first gotchas you notice with Exchange 2007, 2010 and 2013 is the increased security and the challenges of connecting to Exchange remotely.  One tool that I find to be invaluable is the Microsoft Remote Connectivity Analyzer which can identify various issues with your configuration.


    © 2020 sevenlayers.com