{"id":106869,"date":"2025-07-07T13:23:35","date_gmt":"2025-07-07T13:23:35","guid":{"rendered":"https:\/\/www.red-gate.com\/simple-talk\/?p=106869"},"modified":"2025-12-15T11:05:32","modified_gmt":"2025-12-15T11:05:32","slug":"common-sql-server-problems-network-related-or-instance-specific-error-occurred","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/featured\/common-sql-server-problems-network-related-or-instance-specific-error-occurred\/","title":{"rendered":"Common SQL Server Problems: Network Related or Instance Specific Error Occurred"},"content":{"rendered":"\n

This is the first in a series of articles meant to provide practical solutions to common issues. In this post, we\u2019ll talk about one of the most pervasive error messages out there:<\/p>\n\n\n\n

A network-related or instance-specific error occurred while establishing a connection to SQL Server. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.<\/p>\n\n\n\n

Followed by either:<\/p>\n\n\n\n

(provider: SQL Network Interfaces, error: 26 \u2013 Error Locating Server\/Instance Specified)<\/p>\n\n\n\n

or<\/p>\n\n\n\n

(provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)<\/p>\n\n\n\n

One thing I\u2019ll say right off the bat: This is not a permissions issue.<\/strong><\/p>\n\n\n\n

Debugging Steps<\/h2>\n\n\n\n

People often come to my team when they encounter this error, but we can rarely offer a simple, one-size-fits-all answer. But more often than not, the solution to their issue is one of the following:<\/p>\n\n\n

\n
    \n
  1. The server could actually be down<\/strong>. (We do verify this before we send them away!). <\/li>\n\n\n\n
  2. It could be a typo in the connection string<\/strong>. Sometimes it really is as simple as verifying that the instance name is correct. This includes cases where you are specifying an instance name and shouldn\u2019t be, or vice-versa. If you\u2019re using SQL Server Express, often it means you should be using myserver\\SQLEXPRESS<\/code> or localhost\\SQLEXPRESS<\/code>. Check the instance names that are actually running in SQL Server Configuration Manager<\/a>:
    \n
      \n
    1. Open Configuration Manager <\/li>\n\n\n\n
    2. Expand \u201cSQL Server Network Configuration\u201d <\/li>\n\n\n\n
    3. Review the \u201cProtocols for\u201d items listed there:
      \n
        \n
      1. MSSQLSERVER<\/code> is the default instance. That means you specify the server name but no instance name. <\/li>\n\n\n\n
      2. Any other value is a named instance. That means you specify the server name and the instance name, in the form SERVERNAME\\INSTANCENAME<\/code> (though some applications and libraries expect those parameters to be provided separately). <\/li>\n<\/ol>\n<\/div><\/li>\n<\/ol>\n<\/div><\/li>\n\n\n\n
      3. It could be DNS.<\/strong>
        \n
          \n
        1. Make sure nslookup<\/a> and\/or Resolve-DNSName<\/a> return the result(s) you expect when querying the name in the connection string. <\/li>\n\n\n\n
        2. Try connecting by IP address instead of server name. <\/li>\n\n\n\n
        3. Try using the fully-qualified domain name (FQDN) \u2013 e.g. myserver.mydomain.com<\/code> instead of just myserver<\/code>. <\/li>\n\n\n\n
        4. Validate the results of Test-NetConnection<\/a> \u2013 both without a port and with -Port 1433 (or whatever port SQL Server is running on) from the machine trying to connect, not from the database server or from your workstation. <\/li>\n\n\n\n
        5. Don\u2019t rely on ping \u2013 often ping and other ICMP traffic will be rejected by design, so an unsuccessful ping isn\u2019t necessarily evidence that the server is unreachable on SQL Server-specific ports. <\/li>\n<\/ol>\n<\/div><\/li>\n\n\n\n
        6. Check to see if the server is configured to allow remote connections.<\/strong>
          \n
            \n
          1. In SSMS<\/a>, right-click the server, and select Properties<\/strong>. <\/li>\n\n\n\n
          2. On the Connection tab, make sure \u201cAllow remote connections to this server\u201d is checked. <\/li>\n\n\n\n
          3. If necessary, check the box, and restart the SQL Server service (following established process, of course \u2013 please don\u2019t take down production and then say, \u201cAaron told me to!\u201d). <\/li>\n<\/ol>\n<\/div><\/li>\n\n\n\n
          4. Check availability group settings.<\/strong> If using an availability groups listener, make sure the database name is in the connection string and that MultiSubnetFailover=True<\/code> is included. Otherwise, you could get directed to an IP that is not actively hosting any resources for the availability group. <\/li>\n\n\n\n
          5. TCP\/IP may be disabled<\/strong>. This is the default behavior for some versions and editions. You can enable this through SQL Server Configuration Manager:
            \n
              \n
            1. Open Configuration Manager. <\/li>\n\n\n\n
            2. Expand \u201cSQL Server Network Configuration.\u201d <\/li>\n\n\n\n
            3. Highlight \u201cProtocols for\u201d the instance you want to affect. <\/li>\n\n\n\n
            4. In the right pane, check that \u201cTCP\/IP\u201d is enabled. <\/li>\n\n\n\n
            5. If necessary, right-click, Enable, then restart the SQL Server service (following established process, of course). <\/li>\n<\/ol>\n<\/div><\/li>\n\n\n\n
            6. Check the Port.<\/strong> The server could be running on a port you didn\u2019t expect. You can check the port it\u2019s running on via SQL Server Configuration Manager<\/a>:
              \n
                \n
              1. Open Configuration Manager. <\/li>\n\n\n\n
              2. Expand \u201cSQL Server Network Configuration.\u201d <\/li>\n\n\n\n
              3. Highlight \u201cProtocols for\u201d the instance you are trying to reach. <\/li>\n\n\n\n
              4. In the right-pane, right-click TCP\/IP and select Properties. <\/li>\n\n\n\n
              5. On the IP Addresses tab, scroll to IPAll and see what port is listed under either TCP Dynamic Ports or TCP Port.
                \n
                  \n
                1. If using TCP Port, change your connection string to reference that port explicitly, e.g. myserver.mydomain.com,1488. <\/li>\n\n\n\n
                2. If using TCP Dynamic Ports, see the section below about firewall\/routing, because you won\u2019t want to hard-code the port for a named instance, since the port will be reassigned on service restart. <\/li>\n<\/ol>\n<\/div><\/li>\n<\/ol>\n<\/div><\/li>\n\n\n\n
                3. Check the Docker connection details.<\/strong> If you are using Docker<\/a>, it is pretty common to expect SQL Server inside the container to run on the host\u2019s<\/em> port 1433, so people expect to connect \u2013 particularly from within another container \u2013 via localhost<\/code> or 127.0.0.1<\/code>.
                  \n
                    \n
                  1. You should set your SQL Server container to expose port 1433 on a dedicated port on the host machine, e.g. docker run \u2026 -p 6000:1433<\/code>, then you can connect to localhost,6000<\/code>. <\/li>\n\n\n\n
                  2. You can also look at using host.docker.internal<\/a>. <\/li>\n<\/ol>\n<\/div><\/li>\n\n\n\n
                  3. It could be firewall\/routing<\/strong>.
                    \n
                      \n
                    1. It could be that ports 1433 (TCP) and\/or 1434 (UDP) are not open. This could be due to:
                      \n
                        \n
                      1. Windows Defender firewall \u2013 to validate this in a home lab, just turn the service off temporarily (on both the machine trying to connect and, on the server). In a corporate setting, please work with your IT and\/or networking teams before playing with native firewalls. <\/li>\n\n\n\n
                      2. A real firewall, load balancer, or other routing devices\/rules in your network \u2013 work with your IT and\/or networking teams. <\/li>\n\n\n\n
                      3. If you\u2019re trying to connect to database resources in Azure or some other cloud, make sure you have added your IP address\/range to inbound allow rules, and that you prefix the FQDN with tcp:<\/code> to force TCP\/IP , e.g. for Azure SQL Database, use tcp:myserver.database.windows.net,1433<\/code>. <\/li>\n<\/ol>\n<\/div><\/li>\n\n\n\n
                      4. Within a cloud environment, it could be that your resource groups or environments don\u2019t share a common network. It may very well be by design that the app running in your staging environment is not able to access the databases in your production environment. In Azure, ensure that the SQL Server firewall settings enable \u201cAllow Azure services and resources to access this server.\u201d <\/li>\n\n\n\n
                      5. If you are using a named instance, it will use dynamic ports by default. This requires the SQL Server Browser service to be enabled and running, and reachable via port 1434. If you can\u2019t rely on this, you may have to work with your networking or reliability engineering team to agree on a specific port to use, then set that explicitly for the service using SQL Server Configuration Manager:
                        \n
                          \n
                        1. Open Configuration Manager. <\/li>\n\n\n\n
                        2. Expand \u201cSQL Server Network Configuration.\u201d <\/li>\n\n\n\n
                        3. Highlight the \u201cProtocols for\u201d the instance you want to affect. <\/li>\n\n\n\n
                        4. In the right pane, right-click TCP\/IP and select Properties. <\/li>\n\n\n\n
                        5. Remove any ports from TCP Dynamic Ports. <\/li>\n\n\n\n
                        6. Add the agreed-upon port to TCP Port. <\/li>\n\n\n\n
                        7. Click Apply\/OK, then restart the SQL Server service (following established process, of course). <\/li>\n<\/ol>\n<\/div><\/li>\n<\/ol>\n<\/div><\/li>\n<\/ol>\n<\/div>\n\n\n
                          \"A<\/figure>\n\n\n\n

                          \n \n<\/p>\n\n\n\n

                          Let me know if you know any other fixes for this problem<\/h2>\n\n\n\n

                          Those are the most common fixes I see for the \u201cA network-related or instance-specific error\u2026\u201d messages. Do you have additional fixes or comments about the ones I\u2019ve listed? Please leave a comment below!<\/p>\n","protected":false},"excerpt":{"rendered":"

                          This is the first in a series of articles meant to provide practical solutions to common issues. In this post, we\u2019ll talk about one of the most pervasive error messages out there: A network-related or instance-specific error occurred while establishing a connection to SQL Server. Verify that the instance name is correct and that SQL……<\/p>\n","protected":false},"author":341115,"featured_media":106905,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[53,143524],"tags":[159371,4151,159322],"coauthors":[158980],"class_list":["post-106869","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-featured","category-sql-server","tag-common-issues-in-sql-server","tag-sql-server","tag-troubleshooting-sql-server"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/106869","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/users\/341115"}],"replies":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/comments?post=106869"}],"version-history":[{"count":7,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/106869\/revisions"}],"predecessor-version":[{"id":106884,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/106869\/revisions\/106884"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media\/106905"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=106869"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=106869"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=106869"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=106869"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}