{"id":4099,"date":"2015-01-07T18:54:53","date_gmt":"2015-01-07T10:54:53","guid":{"rendered":"http:\/\/rmohan.com\/?p=4099"},"modified":"2015-01-07T19:01:05","modified_gmt":"2015-01-07T11:01:05","slug":"enable-remote-connections-for-sql-server-express-2012","status":"publish","type":"post","link":"https:\/\/mohan.sg\/?p=4099","title":{"rendered":"Enable remote connections for SQL Server Express 2012"},"content":{"rendered":"

On my installation of SQL Server 2012 Developer Edition, installed with default settings, I just had to load the SQL Server Configuration Manager -> SQL Server Network Configuration -> Protocols for MSSQLSERVER and change TCP\/IP from Disabled to Enabled.<\/p>\n

 <\/p>\n\n\n\n
\n
down vote<\/a>accepted<\/span><\/div>\n<\/td>\n
\n
\n

Well, glad I asked<\/a>. The solution I finally discovered was here:<\/p>\n

How do I configure SQL Server Express to allow remote tcp\/ip connections on port 1433?<\/a><\/p>\n

    \n
  1. Run SQL Server Configuration Manager.<\/li>\n
  2. Go to SQL Server Network Configuration > Protocols for SQLEXPRESS.<\/li>\n
  3. Make sure TCP\/IP is enabled.<\/li>\n<\/ol>\n

    So far, so good, and entirely expected. But then:<\/p>\n

      \n
    1. Right-click on TCP\/IP and select Properties<\/strong>.<\/li>\n
    2. Verify that, under IP2, the IP Address is set to the computer’s IP address on the local subnet.<\/li>\n
    3. Scroll down to IPAll.<\/li>\n
    4. Make sure that TCP Dynamic Ports<\/strong> is blank<\/strong>. (Mine was set to some 5-digit port number.)<\/li>\n
    5. Make sure that TCP Port<\/strong> is set to 1433<\/strong>. (Mine was blank.)<\/li>\n<\/ol>\n

      (Also, if you follow these steps, it’s not<\/em> necessary to enable SQL Server Browser, and you only need to allow port 1433, not 1434.)<\/p>\n

      These extra five steps are something I can’t remember ever having had to do in a previous version of SQL Server, Express or otherwise. They appear to have been necessary because I’m using a named instance (myservername\\SQLEXPRESS) on the server instead of a default instance. See here:<\/p>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

       <\/p>\n

       <\/p>\n

      \n
      \n<\/div>\n
      \n

      To assign a TCP\/IP port number to the SQL Server Database Engine<\/h3>\n
      \n
        \n
      1. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration<\/span>, expand Protocols for <instance name><\/span>, and then double-click TCP\/IP<\/span>.<\/li>\n
      2. In the TCP\/IP Properties<\/span> dialog box, on the IP Addresses<\/span> tab, several IP addresses appear in the format IP1<\/span>, IP2<\/span>, up to IPAll<\/span>. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses appear for each IP Address on the computer. Right-click each address, and then click Properties<\/span> to identify the IP address that you want to configure.<\/li>\n
      3. If the TCP Dynamic Ports<\/span> dialog box contains 0<\/span>, indicating the Database Engine is listening on dynamic ports, delete the 0.<\/li>\n
      4. In the IP<\/span>n<\/em> Properties<\/span> area box, in the TCP Port<\/span> box, type the port number you want this IP address to listen on, and then click OK<\/span>.<\/li>\n
      5. In the console pane, click SQL Server Services<\/span>.<\/li>\n
      6. In the details pane, right-click SQL Server (<\/span><instance name>)<\/span> and then click Restart<\/span>, to stop and restart SQL Server.<\/li>\n<\/ol>\n

        After you have configured SQL Server to listen on a specific port, there are three ways to connect to a specific port with a client application:<\/p>\n