syko24
 
 

Recently I had a similar issue with a client.  The problem ended up being that there was another program running on the same port as my SQL instance.  Try running a netstat -b on from command prompt on the server and see what ports are being used.  Then go into SQL Server Configuration Manager from the start menu.  Select your SQL instance under SQL Server Network Configuration and then right click on TCP/IP and select properties.  Check the IP Addresses tab and see if any ports match the ports you found in your netstat results.