A network-related or instance-specific error occurred while establishing a connection to SQL Server Amicle + 12/29/2022 + 26 minutes to read Applies to: SQL Server When connecting to a SQL Server instance, you may encounter one or more of the error messages below. This article provides some steps to help you troubleshoot these errors, which are provided in order of the issues from simple to complex. Error messages The complete error messages vary depending on the client library that is used in the application and the server environment. You can check the following details to see if you're encountering one of the following errar messages: “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” ¥ provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server (Microsoft SQL Server, Error: $3) A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found for was not accessible. Verity that the instance name is correct and that SQL Server is configured to allow remote connections. provider: Named Pipes Provider, error: 40 - Could not open a connection to SQLServer (Microsoft SQL Server, Error: 53) provider: TCP Provider, error: 0 - No such host is known. (Microsoft SQL Server, Error: 11001) ¥ provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified ‘A network-related or instance-specific error occurred while establishing 2 connection to SQL Server. The server was not found or was not accessible, Verify that the instance name is correct and that SQL Server is configured to allow remote connections. provider: SQL Network Interfaces, error. 26 - Error Locating Server/Instance Specified ¥ Login timeout expired SQL Server Native Client Data Link Error [Microsoft SQL Server Native Client 10.0}: Login timeout expired [Microsoft SQL Server Native Client 10.0}: A network-related or instance-speeifc error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [Microsoft SQL Server Native Client 10.0}: SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF] ¥ A.connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ‘A network-related or instance-specific error occurred while establishing a connection to SQlL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. provider: TCP Provider, error: 0 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond, Microsoft SQL Server, Error: 10060 ¥ provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server ‘A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found for was not accessible, Verify that the instance name is correct and that SQL Server is configured to allow remote connections. provider: Named Pipes Provider, error: 40 - Could not open a connection to SQ Server Microsoft SQL Server, Error: 53, The network path was not found ¥ (Microsoft|(SQL Server Native Client 11.0]TCP Provider: No connection could be made because the target machine actively refused itSQL. Server Native Client Data Link Error [Microsoft][SQL Server Native Client 11.0]TCP Provider: No connection could be made because the target machine actively refused it Microsoft|[SQL Server Native Client 11.0]Login timeout expired, [Microsoft][SQL Server Native Client 11.0)A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible, Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. "SQL Server does not exist or access denied" This error usually means that the client can't find the SQL Server instance. This issue occurs when at least one of the following problems exists ‘The name of the computer hosting SQL Server is incorrect, The instance doesn't resolve the correct IP. = The TCP port number isn't specified correctly, ONote For troubleshooting connectivity issues in high availabilty scenarios, see the following articles: # Connect to an Always On availabilty group listener ‘+ Always On Failover Cluster Instances (SQL Server) Gather information for troubleshooting the error ‘We recommend that you gather the information listed in this section using one of the options below before proceeding with the actual steps to troubleshoot the error. Option 1: Use the SQL Check tool to gather the required information I you can sign in locally to the SQL Server computer and have administrator access, use SQLCheck from the Microsoft SQL Networking Githiub repository. This tool provides most of the information requited for troubleshooting in one file. Review the tool's home page for more information on using the tool and the information it gathers. You can also check the recommended prerequisites and checklist page. Option 2: Collect the data individually using the following procedures Get the instance name from Configuration Manager On the server that hosts the SQL Server instance, use SQL Server Configuration Manager to verify the instance name: ONote Configuration Manager is automatically installed on the computer when SQL Server is installed. Instructions on starting Configuration Manager vary slightly by versions of SQL Server and Windows. For version-specific details, see SQL Server Configuration Manager. 1. Sign in to the computer hosting the instance of SQL Server. 2. Start SQL Server Configuration Manager. 3.1In the left pane, select SQL Server Services. 4, In the right pane, verify the name of the instance of the database engine ‘+ SOL SERVER (MSSQLSERVER) indicates a default instance of SQlL Server. The name of the default instance is .‘© SQL SERVER () indicates a named instance of SQL Server, The name of the named instance is computer name>\, Get the IP address of the server You can use the following steps to get the IP address of the computer hosting the instance of SQL Server. 1, On the Start menu, select Run, In the Run window, type md, and then select OK, 2.1n the Command Prompt window, type ipconfig/all and then press Enter. Note down the IPv4 address and the IPvé address, Note SQ. Server can connect by using either IP version 4 protocol or IP version 6 protocol. Your network could allow either or both, Get the TCP port of the instance In most cases, you connect to the Database Engine on another computer by using the TCP protocol. To get the TCP port of the instance, follow these steps: 1. Use SQL Server Management Studio on the computer running SQL Server and connect to the instance of SQL Server. In ‘Object Explorer, expand Management, expand SQLServer Logs, and then double-click the current log. 2.1n the Log File Viewer, select Filter on the toolbar. In the Message contains text box, type server is listening on, select ‘Apply filter, and then select OK. 3. Amessage like Server is listening on [ ‘any’ 1433] should be listed. This message indicates that the instance of SQL Server is listening on all IP addresses on this computer (for IP version 4) and TCP port 1433. (TCP port 1433 is usually the port that's used by the Database Engine or the default instance of SQL Server. Only one instance of SQL Server can use this port. If more than one instance of SQL Server's installed, some instances must use other port numbers) Note down the port number used by the SQL. Server instance that you're trying to connect to, ONote ‘© IP address 127.001 is probably listed, It's called the loopback adapter address. Only processes on the same computer can use the IP address to connect. + You can also view the SQL Server error log by using a text editor. By default, the error log is located at Program Files\Microsoft SQL Server\MSSQLn\MSSQL\LOG\ERRORLOG and ERRORLOGn files. For more information, see Viewing the SQL Server error log, Step 1: Verify that the instance is running Option 1: Using the output file from the SQLCheck tool 1. Search the output from SQL.Check file for “SQL Server Information’ 2. In the section titled "Services of Interest’ find your SQL Server instance under Name and Instance (for named instances) columns and check its status by using Started column. Ifthe value is True, the services are started, Otherwise the service is currently not running 3. Ifthe service isn't running, start the service by using either SQL Server management studio, SQL Server Configuration manager, Powershell, or Services applet. Option 2: Use SQL Server Configuration ManagerTo verify that the instance is running, select SQL Server Services in SQL Server Configuration Manager and check the symbol by the SQL Server instance, * Agreen arrow indicates that an instance is running *# Ared square indicates that an instance is stopped. If the instance is stopped, right-click the instance andl select Start. Then, the server instance starts, and the indicator becomes 2 green arrow Option 3: Use PowerShell commands You can use the following command in PowerShell to check the status of SQL Server services on the system: Poweshel Get-service | where {$_-status -eq “running’ -and §_isplayNane -natch “sql server**) You can use the following command to search the error lag file for the specific string "SQL Server is now ready for cient connections. This isan informational message; no user ation is required" Powershl Get-chitarten -Path "c:\prograr Files\nicrosoft sql server\nssql*™ -Recurse -Include Errorlog |select-string SQL Server 1s now ready for client connections. Step 2: Verify that the SQL Server Browser service is running ONote This step is required only for troubleshooting connectivity issues with named instances, Option 1: Using the output file from SQLCheck tool 1. Search the output from SALCheck file for “SQL Server Information’ 2.1n the section titled "Services of Interest’, search for SQLBrowser in the Name column and check its status using the Started column, Ifthe value is True, the service is started. Otherwise, the service is currently not running, and you need to start it. For more information, see Start, stop, pause, resume, restart SQlL Server services, Option 2: Use SQL Server Configuration Manager To connect to a named instance, the SQL Server Browser service must be running. In SQL Server Configuration Manager, locate the SQL Server Browser service and verify that it's running. Ifit's not running, start the service. The SQL Server Browser service isn't required for default instances, For more information on using SQL Server Browser service in your environment, see SQL Server Browser service. For more information on stopping and starting SQL Services, ee Star, stop, pause, resume, restart SQL Server services ONote you can't have the SQL Server Browser service running in your environment, see Connecting to SQL server named instance without SQL Server browser service Step 3: Verify the server name in the connection string You often encounter errors when an incorrect server name is specified in the connection string. Make sure that the server name matches the one that you retrieved in the previous steps,ONote If you are using the SQLCheck tool, review the NetBios Name/FODN values in the Computer Information section of the output file + For examples on connection strings, see SQL Server Connection Stings * For more detailed examples, see Proof of concept connecting to SQL using ADO.NET under Homepage for SQL client programming. Step 4: Verify the aliases on the client machines Aliases are often used in client environments when you connect to SQL Server with an alternate name or when there are name resolution issues inthe network, They're created by using SQL. Server Configuration Manager or client network utility, {An incoreect alias can cause the connections from your applications to connect to the wrong server, resulting in failure, Use the following methods to check for incorrect aliases. You can also use a tool (such as SQLCHECK on the client machine to check for aliases and various other connectivty-related settings on a client machine. ONote The following options only apply to the applications that use SQL Server Native Client to connect to SQL Server. Option 1: Using the output file from the SQLCheck tool 1. In the SL.Check output file, search for the string SQL Aliases, (Ths string will be inside the Client Security and Driver Information section ofthe fle) 2, Review the entries in the table, IF there's none present, there are no aliases on the computer. If there's an entry, review the information to ensure the server name and port number are set to the correct values. Example output: SQL Aliases: Alias None Protocol Server Name Part 32-bit prods Ter prod_salserver 1430 The above indicates that prodsal is an alias for a SQL Server called prod_saiserver that is running on port 1430. Option 2: Check aliases in SQL Server Configuration Manager 1. In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, and select Aliases. 2. Check whether any aliases are defined for the server that you're trying to connect to. Ifthe aliases exis, follow these steps ‘8, Open the Properties pane of the alls, b, Rename the value in the Alias Name field (for example, if your server name is MySQL, rename it as MySQL test) and retry the connection. Ifthe connection works, your alias is incorrect and may come from an old configuration that is no longer needed. Ifthe connection doesn't work, rename the alias back to its original name and go to the next step. «. Check the connection parameters for the alias and make sure that they're correct. The following common scenarios can cause connectivity problems: ‘= Incorrect I? address for the Server field, Make sure that the IP address matches the entry in the SQL Server error lag file ‘+ Incorrect server name in the Server field. For example, your server alias points to the correct server name, However, the connections will fal f the value of the server name parameter is incorrect. ++ Incorrect pipe name format (assuming that you use a named pipes alia).‘© When connecting to a default instance named Mydefaultinstance, the pipe name should be \WMydefaultinstance\pipe\sqi\query. ‘© When connecting to a named instance MySQLINamed, the pipe name should be \WMySQlipipe\MSSQLSNamedisqliquery. Option 3: Check aliases in SQL Server Client Network Utility 1, Open SQL Server Client Network Utility by typing cliconf.exe in your Run command. 2. Follow step 2 in Option 2: Check aliases in SQL Server Configuration Manager. Step 5: Verify the firewall configuration You can verify the firewall configuration depending on the default instance or named instance, ONote Ifyou are using third party firewalls in your network, the concepts still apply. However, you may have to work with your network administrator or consul the firewall product's documentation for more information on configuring the firewall to allow necessary ports for communication with SQL Server Default instance of SQL Server ‘A default instance typically runs on port 1433. Some installations also use a non-standard port (other than 1433) to run SQL. instances. The firewall may block either port. To check the port number further, follow these steps 1, Determine the port your SQL instance is running on, see Get the TCP port of the instance. * If your SQL Server is configured to listen on port 1433, make sure that firewalls on the network between the client and the server allow traffic on that port. Review Configure a Windows Firewall for Database Engine Access and work with your network administrator to implement necessary solutions, * If your SQL Server default instance isn't using 1433, try to append the port number of SQL Server to the server name by Using the format , cportnunber> and see whether it works, For example, your SQL instance name is. ‘MySQUDefouttinstance and it's running on port 2000. Specify the server name as MySQLServer, 2000 and see whether it works. * fit doesn't work, it indicates the firewall is blocking the port. You can follow the instructions at Configure a Windows Firewall for Database Engine Access or work with your network administrator to add the port to the firewall exclusion Ist © Ifitdoes work, it indicates that the firewalls allowing communication through that port. You need to change your connection string in order to use the port number and your server name in the connection string of your application Named instance of SQL Server I your SQL instance is a named instance, it may be configured to use either dynamic ports or a static port In either case, the underlying network libraries query the SQL Server Browser service running on your SQL Server machine through UDP port 1434 to enumerate the port number for the named instance. If firewall between the client and the server blocks this UDP port, the clien library can't determine the port (a requirement for connection) and the connection fails. To check the connection, you can use one of the following methods: Method 1: Check connection by specifying the port number in your connection string 1, Determine the port your SQL instance is running on, see Get the TCP port of the instance. 2. Try to connect to the named instance by using the port number appended to the server name in the format , and see if that works, For example, if your SQL instance name is ‘MySQLINamedinstance and it’s running on port 3000, specify the server name as MySQL\Namedinstance, 3000, © Ifit does work, it indicates the firewall is blocking the UDP port 1434 or the instance is hidden from SQL Server Browser. © If it doesn't work it indicates one of the following situations:© Either UDP port 1434 is blocked or the static port is blocked, or both, To confirm whether it's the UDP port or the static port, use Portary. ©The instance is hidden from the SQL Server Browser service. ‘+ Method 2: Check the connection by using the PortQryUI tool Use the PortQryUI tool with your named instance and observe the resulting output. You may see a message that the UDP port 1434 is filtered. This message indicates that the port is blocked on the network. For instructions on how to use the tool, see Using the PortQryUl Tool with SQL Server. Determine whether the SQL Server instance is Iistening on dynamic or static ports. Then use the following method that is relevant to your scenario. If you aren't sure, see How to check if SQL Servers listening on a dynamic port or static port © Scenario 1: Dynamic ports. In this case, ensure that the SQL Server Browser service is started and UDP port 1434 isn’t blocked on the firewall between the client and the server. f you can't do either of these things, you should switch your SQL Server instance to a static port and use the procedure documented in Configure a Server to Listen on Specific TCP Port. © Scenario 2: Static port configuration. Either SQL Server Browser isn't running or UDP 1434 can't be opened on the firewall In this case, make sure to specify the static port in your connection string and that the firewall doesn't block the port, For more information, review Configure a Windows Firewall for Database Engine Access Step 6: Verify the enabled protocols on SQL Server In some installations of SQL Server, connections to the Database Engine from another computer aren't enabled unless an administrator manually enables them. You can use one of the following options to check and enable the necessary protocols to allow remote connections to SQL Server Database Engine, le from SQLCheck tool 1, Search the SQLCheck output file for "Details for SQL Server instance" section and locatt SQL Server instance, Option 1: Using the output the information section for your 2. In the section, find the values listed in the following table to determine if the SQL Server protocols are enabled: Value name Implication More information Shared Memory Can either be true of fale - only affects local connections Creating a Valid Connection String Using Enabled Shared Memory Protocol Named Pipes If false, both local and remote connections using Named pipes wil fail Choosing a Network Protocol Enabled TCP Enabled fale, both local and remote connections sing TCP/IP wil fl Choosing a Network Protocol [Note The majority ofthe SQL Server installations use TCP/IP as the communication protacol between server and the client, 3. Enable required protocols by using SQL Server Configuration Manager or SQlL Server PowerShell. For more information, see Enable or Disable a Server Network Protocol. ONote After enabling a protocol, the Database Engine must be stopped and restarted for the change to take effect. Option 2: Use SQL Server Configuration Manager To enable connections from another computer by using the SQL Server Configuration Manager, follow these steps: 1. Open the SAL Server Configuration Manager. 2.1In the left pane, expand SQL Server Network Configuration, and then select the instance of SQL Server that you want to connect to. The right pane lists the connection protocols available. Shared Memory is normally enabled. It can onlybe used from the same computer, so most installations leave Shared Memory enabled, To connect to SQL Server from another computer, use TCP/IP, If TCP/IP isn't enabled, right-click TCP/IP, and then select Enable. 3. If you change the enabled setting for any protocol, restart the Database Engine. In the left pane, select SQL Server Services. In the right-pane, right-click the instance of the Database Engine, and then select Restart Step 7: Test TCP/IP connectivity Connecting to SQL Server by using TCP/IP requires that Windows establish the connection. You can use the following steps to test TCP connectivity by using the ping tool 1. On the Start menu, select Run. In the Run window, type cmd and select OK. 2.1m the Command Prompt window, type ping and the IP address of the computer that’s running SQLServer, For example: ‘© IPv4: ping 192.268.1101 1 PVG: ping #ea0::451d:5a05:6F09:9Fa6x12 3. f your network is configured properly, ping returns Reply fros <1P address> followed by some additional information. IF ping returns oestination host unreachable OF Request tined out, TCP/IP isn't correctly configured. Errors at this point indicate a problem with the client computer, the server computer, oF something about the network such as a router. To troubleshoot network problems, see Advanced troubleshooting for TCP/IP issues. 4, Ifthe ping test succeeds by using the IP address, test whether the computer name can be resolved to the TCP/IP ‘address. On the client computer, in the Command Prompt window, type ping and the name of the computer that's running SQL Server. For example, ping nenof#icepe 5. Ifping to the IP address succeeds, but ping to the computer name returns Destination host unreachable OF Request ‘ined out, you might have old (stale) name resolution information cached on the client computer. Type ipconfig, ‘/flushans to clear the DNS (Dynamic Name Resolution) cache. Then ping the computer by name again. When the DNS cache is empty, the client computer checks the latest information about the IP address for the server computer. 6. If your network is configured properly, ping returns Reply fron followed by some additional information. Ifyou can successfully ping the server computer by IP address but receive an error such as bestination host unreachable OF Request timed out when pinging by computer name, then name resolution isn't correctly configured, For more information, see how to Troubleshoot Basic TCP/IP Problems. Successful name resolution isn't required to connect to SQL Server. However, ifthe computer name can’t be resolved to an IP address, connections must be made to specify the IP address. Name resolution can be fixed late. ONote You can also use either Test-NetConnection or Test-Connection cmdlet to test TCP connectivity according to the PowerShell version that’s installed on the computer. For more information on PowerShell cmdlet, see Cmdlet Overview. Step 8: Test local connection Before troubleshooting a connection problem from another computer, test your ability to connect from a client application, installed locally on the computer that is running SQL Server. Local connection avoids issues with networks and firewalls This procedure requires SQL Server Management Studio. f you don't have Management Studio installed, see Download SQL Server Management Studio (SSMS) I you can’t install Management Studio, you can test the connection by using the sqlemd.exe utility. sqlemd.exe is installed with the Database Engine, For information about sqlemd exe, see sqlemd Utility 1. Sign in to the computer where SQL Server is installed by using a login that can access SQL Server. During installation, SQL Server requires at least one login to be specified as a SQL Server administrator. f you don't know an administrator, ‘see Connect to SQL Server When System Administrators Are Locked Out, 2..On the Start page, type SQL Server Monagement Studio, or on the Start menu of the older versions of Windows, select All Programs, select Microsoft SQL Server, and then select SQL Server Management Studio.3..On the Connect drop-down menu, select Database Engine, In the Authentication box, select Windows Authentication In the Server name box, type one of the follewing connection types: Connecting to Type Example Default instance conpoter name> peor? Named instance computer nane\inetance anes Acer 7\PYROLL Note ‘When connecting to SQL Server from a client application on the same computer, the shared memory protocol is. used. Shared memory isa type of local named pipe, so you sometimes encounter errars related to pipes. 4, Ifyou receive an error at this point, you must resolve it before proceeding, Your login might not be authorized to connect. Your default database might be missing Note You can't troubleshoot the problem without enough information because some error messages are passed to the client intentionally. This is a security feature to avoid providing an attacker with information about SQL Server. To view the details about the error, see the SQL Server error log, 5. Ifyou receive error 18456 Login failed for user, Books Online article MSSQLSERVER_18456 contains additional information about error codes. Aaron Bertrand's blog also has an extensive list of error codes at Troubleshooting Error 18436 (external link). You can view the error log by using SSMS (if you can connect), in the Management section of the Object Explorer. Otherwise, you can view the error log with the Windows Notepad program. The default location varies with your version and can be changed during setup. The default location for SQL Server 2019 (15.x) is C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log\ERRORLOG, 6, If you can connect by using shared memory, test connecting by using TCP. You can force a TCP connection by specifying ‘tcp: before the name, Here are the examples: Connecting to: Type: Baampl Default instance tepscconputer nane> epsacexrz7 Named instance tepscconputer nane/instance name> epsAcONT2TYPANAOLL, 7. f you can connect by using shared memory but not TCP, you must fx the TCP problem. The most likely issue is that TCP isn't enabled. To enable TCP, see Step 6: Verify the enabled protocols on SQL Server. 8, If your goal is to connect by using an account other than an administrator account, you can begin by connecting as an administrator. Then, try to connect again with the Windows Authentication login or the SQL Server Authentication login that the client application uses. Step 9: Test remote connection Once you can connect by using TCP on the same compute, i's time to ty to connect from the cient computer. You could use any client application, but to avoid complexity, install the SQL Server Management tools on the client. After installation, to use SQL Server Management Studio. 1. Use SQL Server Management Studio on the client computer and try to connect by using the IP address and the TCP port number in the format IP address comma port number. For example, 192.368.1.162,1433. If this connection fails, you probably have one of the following problems: ‘ping of the IP address doesn’t work. Ths indicates a general TCP configuration problem, Go back to the section Step 7: Test TCP/IP connectivity '* SQL Server isn't listening on the TCP protocol. Go back to the section Step 6: Verify the enabled protocols on SQL Server. ‘+ SQL Server is listening on a port other than the port that you specified, Go back te section Get the TCP port.‘© The SQL Server TCP port is being blocked by the firewall. Go back to the section step 5: Verify the firewall configuration 2. Once you can connect by using the IP address and port number, review the following scenarios: ‘Ifyou connect to a default instance that i listening on any port other than 1433, you must use either the port number in the connection string or create an alias on the client machine to connect to the default instance, The SQL. Server Browser service can't enumerate ports of the default instance, ‘+ Ifyou connect to a named instance, try to connect to the instance in the format IP address backslash instance name. (For example, 192.158.1.201\.) If this action doesn't work, it means that the port number isn't being returned to the client. The problem is related to the SQL Server Browser service, which provides port number of a named instance to the client. Here are the solutions © Start the SQL Server Browser service. See the instructions to start browser in SQL Server Configuration Manager. © The SQL Server Browser service is being blacked by the firewall. Open UDP port 1434 in the firewall. Go back to the section Step 5: Verily the firewall configuration, Make sure that you're opening a UDP port, not a TCP port. (© The UDP port 1434 information is being blocked by a router. UDP communication (user datagram protocol) isn’t designed to pass through routers and keeps the network from getting filled with low-priorty traffic. You ‘can configure your router to forward UDP traffic, or you can provide the port number every time you connect. © Ifthe client computer is using Windows 7, Windows Server 2008, or a more recent operating system, the client ‘operating system might drop the UDP traffie because the response from the server is returned from a different IP address that was queried. This action is a security feature blocking "loose source mapping.” For more information, see the Multiple Server IP Addresses section of the Books Online article Troubleshooting: Timeout Expired. (This article i from SQL Server 2008 R2, but the principals still apply. You can configure the client to use the correct IP address or provide the port number every time you connect) 43. Once you can connect by using the IP address (or IP address and instance name for a named instance), try to connect by using the computer name (or computer name and instance name for a named instance). Put tep: in front of the computer name to force a TCP/IP connection. For example, for the default instance on a computer named ACCNT27, use tep:Acenr27. For a named instance called| PAYROLL, on that computer use tep:ACcNT27\PaYROL’ . If you can connect, by using the IP address but not by using the computer name, you have a name resolution problem. Go back to the section Step 7: Test TCP/IP connectivity 4, Once you can connect by using the computer name forcing TCP, try to connect by using the computer name without forcing TCP. For example, for a default instance, and just use a computer name such as CCNT27. Far a named instance, use the computer name and instance name like ACCNTZ7\PAYROLL. If you can connect while forcing TCP, but not without forcing TCP, the client is probably using another protocol such as named pipes. To fix this issue, follow the steps: {On the client computer, use SQL Server Configuration Manager. Inthe left-pane, expand SQL Native Client Configuration, and then select Client Protocols . On the right-pane, make sure that TCP/IP is enabled. I TCP/IP is disabled, right-click TCP/IP and select Enable. Make sure that the protocol order for TCP/IP is a smaller number than the named pipes (or VIA on older versions) protocols. Generally, you should leave shared memory as order 1 and TCP/IP as order 2. Shared memory is only used when the client and SQL Server are running on the same computer. All enabled protocols are tried in order until one succeeds, but shared memory is skipped when the connection isn't on the same computer. See also + Troubleshoot connectivity issues in SQL Server + 0200 Consistent Network Issue + Connect to an Always On availabilty group istener * Always On Failover luster Instances (SQL. Server) ‘© Troubleshooting connectivity issues and other errors with Azure SQL Database and Azure SQL Managed Instance Feedback Provide product feedback | Get help at Microsoft Q&A Was this page helpful?