Scenario 1:
SQL is not connecting via Management studio locally after a fresh Installation:
1. After a fresh Installation of SQL and opening the port in the Firewall you may not be able to connect via SQL management studio.
Note: Installing SQL and opening the port in Firewall will not listen to the service/port. Its obvious that no service will listen even If the port is opened in the firewall. The application must listen to the service.
2. After Installing SQL, go to SQL Enterprise Manager in case of 2005, 2008, SQL server Network Utility If the version is 2000.
3. Go to TCP/IP, make sure the default localhost IP and the IP in which your server must listen to the SQL service should use the SQL port. Restart the SQL services.
Scenario 2:
If you require SQL Server to listen on an alternative port or to share additional port for remote access, please follow these directions:
1) Login to your server using Terminal Services Client
2) Go to Start -> Programs -> SQL Server -> Server Network Utility (SQL 2000) , SQL enterprise Manager -> services ->TCP/IP (SQL 2005, 2008)
3) Under Enabled Protocols, select TCP/IP and go to properties
4) In the default port field, enter “1433,2433” without the quotes for single IP. This will force SQL Server to listen on both port 1433 and 2433. If you would like to have SQL listen on a different port, simply enter additional port numbers in a comma delimited format.
5) Now restart the SQL Server service so that it can rebind it’s network connections.
6) If you have multiple IP’s with each IP must listen to different services , repeat the same steps from 1 to 4.
Note:
Making this change will in no way effect any existing SQL Server services. You will not need to update or change any code, DSNs, or anything on the server. However, you will need to reconfigure any EXTERNAL connections to utilize port 2433. Any internal communications will continue to function on port 1433.
