How To Configure MS SQL Server on your Dedicated Server for an Alternate Port

Plesk Servers > SQL > MSSQL
 
 
How To Configure MSSQL Server on your Dedicated Server for an Alternate Port

If you require MSSQL Server on your dedicated server to listen on an alternative port for remote access (normally due to local firewall rules) do the following.
 
There are two systems that this can be applied to:
  • Windows 2003/2008/2008 R2
  • Windows 2012
Windows 2003/2008/2008 R2
  1. Login to your dedicated server using Remote Desktop.
  2. Go to Start > Programs > Microsoft SQL Server 2005/2008 > SQL Server Configuration Manager.
  3. Expand SQL Server Configuration Manager(Local) > SQL Server 2005/2008 Network Configuration > Protocols for MSSQLServer.
  4. Under Protocols, right-click TCP/IP and select Properties.
  5. Select the IP Addresses tab and then scroll to the IP All section.
  6. Change the TCP Port value from 1433 to 14333 (or any other port) and then click OK.
  7. Restart your SQL Server by going to Start > Settings > Control Panel > Administrative Tools > Services > SQL Server (MSSQLSERVER) > Restart.
Windows 2012
  1. Login to your dedicated server using Remote Desktop.
  2. Press (Windows Key) > (type) SQL Server Configuration Manager.
  3. Expand SQL Server Configuration Manager(Local) > SQL Server 2005/2008 Network Configuration > Protocols for MSSQLServer.
  4. Under Protocols, right-click TCP/IP and select Properties.
  5. Select the IP Addresses tab and then scroll to the IP All section.
  6. Change the TCP Port value from 1433 to 14333 (or any other port) and then click OK.
  7. Restart your SQL Server by going to Start > Settings > Control Panel > Administrative Tools > Services > SQL Server (MSSQLSERVER) > Restart.
Please note: Making this change will in no way effect any existing MSSQL Server services.  You will not need to update or change any code, DNS configurations, or any other settings on the server.  However, you will need to reconfigure any external connections to utilize port 14333.   Any internal communications will continue to function on port 1433.

Add Feedback