{"id":2587,"date":"2017-07-12T23:25:12","date_gmt":"2017-07-12T23:25:12","guid":{"rendered":"http:\/\/pariswells.com\/blog\/?p=2587"},"modified":"2017-07-12T23:25:12","modified_gmt":"2017-07-12T23:25:12","slug":"how-to-enable-sql-server-express-for-remote-management-via-sql-management-studio","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/research\/how-to-enable-sql-server-express-for-remote-management-via-sql-management-studio","title":{"rendered":"How to enable SQL Server Express for Remote Management via SQL Management Studio"},"content":{"rendered":"

Configure the firewall to allow network traffic that is related to SQL Server and to the SQL Server Browser service.<\/strong><\/h4>

Four exceptions must be configured in\u00a0Windows Firewall<\/strong>\u00a0to allow access to\u00a0SQL Server:<\/strong><\/p>

  1. A port exception for\u00a0TCP Port 1433.\u00a0<\/strong>In the New Inbound Rule Wizard dialog, use the following information to create a port exception:
    • Select\u00a0Port<\/strong><\/li>
    • Select\u00a0TCP<\/strong>\u00a0and specify port\u00a01433<\/strong><\/li>
    • Allow the connection<\/li>
    • Choose all three profiles (Domain, Private & Public)<\/li>
    • Name the rule \u201cSQL \u2013 TCP 1433\u201d<\/li><\/ul><\/li>
    • A port exception for\u00a0UDP Port 1434.\u00a0<\/strong>Click\u00a0New Rule\u00a0again and use the following information to create another port exception:
      • Select\u00a0Port<\/strong><\/li>
      • Select\u00a0UDP<\/strong>\u00a0and specify port\u00a01434<\/strong><\/li>
      • Allow the connection<\/li>
      • Choose all three profiles (Domain, Private & Public)<\/li>
      • Name the rule \u201cSQL \u2013 UDP 1434<\/li><\/ul><\/li>
      • A program exception for\u00a0sqlservr.exe.\u00a0<\/strong>Click\u00a0New Rule\u00a0again and use the following information to create a program exception:
        • Select\u00a0Program<\/strong><\/li>
        • Click\u00a0Browse<\/strong>\u00a0to select \u2018sqlservr.exe\u2019 at this location:
          \u00a0<\/div><\/li><\/ul><\/li><\/ol><\/div><\/div>
          [C:\\Program Files\\Microsoft SQL Server\\MSSQL11.<INSTANCE_NAME>\\MSSQL\\Binn\\sqlservr.exe] where <INSTANCE_NAME> is the name of your SQL instance. \u00a0
          • Allow the connection<\/li>
          • Choose all three profiles (Domain, Private & Public)<\/li>
          • Name the rule SQL \u2013 sqlservr.exe<\/li>
          • A program exception for\u00a0sqlbrowser.exe\u00a0<\/strong>Click\u00a0New Rule\u00a0again and use the following information to create another program exception:
            • Select\u00a0Program<\/strong><\/li>
            • Click\u00a0Browse<\/strong>\u00a0to select sqlbrowser.exe at this location: [C:\\Program Files (x86)\\Microsoft SQL Server\\90\\Shared\\sqlbrowser.exe].\u00a0<\/li>
            • Allow the connection<\/li>
            • Choose all three profiles (Domain, Private & Public)<\/li>
            • Name the rule SQL \u2013\u00a0sqlbrowser.exe<\/li><\/ul><\/li><\/ul><\/div><\/div>","protected":false},"excerpt":{"rendered":"

              Configure the firewall to allow network traffic that is related to SQL Server and to the SQL Server Browser service.Four exceptions must be configured in\u00a0Windows Firewall\u00a0to allow […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,1],"tags":[1741,1955,1956,1957],"class_list":["post-2587","post","type-post","status-publish","format-standard","hentry","category-random","category-research","tag-remote","tag-sql-express","tag-sql-management","tag-sql-management-studio"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t