Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 53

Error 53 and Error 26: SQL Server Instance Not Found on the Network

11 min read Updated October 5, 2026 SQL Server

Fix it now

Neither of these is a login failure and no password helps. Error 53 is the Windows network path error, ERROR_BAD_NETPATH, surfacing through the client. Error 26 is the client’s own discovery layer reporting that it could not locate the server or instance you named. They fail at different points and have different fixes.

Run from the client that failed, in PowerShell. Do not test from the server console

nslookup sqlhost.contoso.com
Test-NetConnection sqlhost -Port 1433
  1. If the name does not resolve, stop: the fault is DNS and nothing after it matters yet.
  2. If TcpTestSucceeded is False while the same test works from the server’s own subnet, you have a firewall or a disabled protocol rather than a discovery problem.
  3. Check the instance name. A bare server name reaches a default instance; a named instance needs SERVER\INSTANCENAME, and a wrong instance name is the usual cause of error 26.
  4. For a named instance, confirm SQL Server Browser is running and UDP 1434 is open to it. Microsoft’s documented alternative is to specify the static port in the connection string instead.
  5. Prove where the fault is by bypassing discovery: connect to sqlhost,1433, or sqlhost\SALES,3000 for a named instance on a static port. If that works, the problem is the Browser or UDP 1434, not the server.

Use Test-NetConnection rather than ping. ICMP is frequently allowed where TCP is not, so a successful ping tells you almost nothing about whether SQL Server is reachable.

If the plain connection string works without an explicit port, you are done. If not, the next section separates name resolution from instance discovery from the listener itself.

Why it happens

A connection string that names a server and nothing else is asking for two things. First, resolve that name to an address, through DNS, the hosts file or NetBIOS depending on the environment. Second, decide which TCP port to open: 1433 for a default instance unless somebody changed it, and no fixed answer for a named instance, because those commonly use a dynamic port chosen at startup.

That second problem is what the SQL Server Browser exists to solve. The client sends a small UDP request to port 1434 naming the instance it wants, the Browser replies with the port that instance is listening on, and the client opens a normal connection to it. Error 26 is raised when that exchange produces no answer. Microsoft’s remedy where the Browser is unavailable or UDP 1434 cannot be opened is to specify the static port in the connection string.

Error 53 sits earlier still, and its provenance is worth knowing because it changes where you look. It is Windows system error ERROR_BAD_NETPATH, the network path was not found, and Microsoft’s connectivity guidance shows it arriving through the Named Pipes provider alongside error 40. That means the client reached for a named-pipe path over SMB and could not find it, which points at name resolution and at whether the machine is reachable at all, rather than at TCP 1433.

The companion numbers say which layer answered. 40 is the Named Pipes provider reporting that it could not open a connection, a wrapper around whatever failed underneath. 11001 is WSAHOST_NOT_FOUND, host not found, which is name resolution returning nothing. Neither adds a fix of its own.

The name does not resolve to the right machine

You have this one if nslookup returns nothing, or an address that does not belong to the SQL Server.

  1. Test the fully qualified name as well as the short name. A client with the wrong DNS suffix fails on one and succeeds on the other.
  2. Look for a stale A record from a decommissioned server, and a hosts file entry added during a migration and never removed.
  3. Test with the IP address. If that connects, the fault is name resolution.

Availability group listeners and cluster names have their own DNS records and registration behaviour. If the listener name fails while a node name works, that is where to look.

The instance name is wrong

You have this one if Error 26, and the server is reachable by name and answers a port test on something.

  1. Check what is actually installed on the host in SQL Server Configuration Manager, under SQL Server Services.
  2. Remember that a bare server name means the default instance. If only a named instance exists, that name will never connect.
  3. Get the correct name from the instance itself: SELECT @@SERVERNAME, SERVERPROPERTY('InstanceName');
  4. Correct the connection string and retry.

A default SQL Server Express installation creates a named instance, which is why an Express server so often produces error 26 for a connection string that names only the machine.

The SQL Server Browser is not answering

You have this one if A named instance fails without a port and connects with an explicit port.

  1. Start the Browser service and set it to start automatically. It is listed in SQL Server Configuration Manager alongside the instances.
  2. Open UDP 1434 inbound for the client subnets. It is UDP, not TCP, and that catches people out.
  3. Or give the instance a static TCP port and put that port in the connection string, which is the documented alternative.
  4. Retry without the explicit port to confirm discovery now works.

The Browser cannot enumerate ports for a default instance, so this cause only applies to named instances.

TCP/IP is disabled, or the instance is not listening where you think

You have this one if Connections work on the server console and fail from every other machine.

  1. In SQL Server Configuration Manager, open SQL Server Network Configuration, Protocols for your instance, and confirm TCP/IP is enabled.
  2. Open TCP/IP properties, IP Addresses tab, and read the port settings under IPAll.
  3. Restart the SQL Server service after enabling a protocol; the change does not take effect until you do.
  4. Check the client side too, under Client Protocols.

A firewall is blocking the path

You have this one if Name resolution is correct, the port test fails, and the same test succeeds from a machine on the server’s own subnet.

  1. Allow TCP on the instance’s port inbound on the Windows firewall, and UDP 1434 if you rely on the Browser.
  2. Ask the network team to confirm no ACL between the client subnet and the server drops the traffic.
  3. On a cloud virtual machine, remember there are two layers: the guest firewall and the platform’s own network rules.
  4. Retest with Test-NetConnection rather than ping.

Full reference

Which failure is which

Symptom Most likely cause
nslookup fails or returns an old address DNS, a stale record, or a client with the wrong DNS suffix
Ping works, port 1433 test fails Firewall, or TCP/IP disabled in SQL Server Configuration Manager
Default instance works, named instance does not SQL Server Browser stopped, or UDP 1434 blocked
Works with an explicit port, fails without one Confirms a Browser or UDP 1434 problem
Works on the server, fails everywhere else Shared memory on the console is hiding a network fault
Error 53 with a Named Pipes provider message The SMB path, so name resolution and reachability rather than TCP 1433

Connection string forms Microsoft documents

Scenario Form Example
Default instance on 1433 <computer name> ACCNT27
Default instance on another port <computer name>,<port> ACCNT27,2000
Named instance, discovered through the Browser <computer name>\<instance name> ACCNT27\PAYROLL
Named instance on a static port <computer name>\<instance name>,<port> ACCNT27\PAYROLL,3000
Forcing TCP tcp:<computer name> tcp:ACCNT27

Microsoft’s documented test sequence is worth following in order rather than jumping about: connect locally first to rule the instance in, then test the IP with ping, then the computer name, then connect by IP and port, then by name forcing TCP, then by name without forcing it. Each step adds exactly one variable, which is what makes the result mean something.

The codes, precisely

Code What it is
53 Windows ERROR_BAD_NETPATH, the network path was not found. Seen through the Named Pipes provider alongside error 40
26 SQL Network Interfaces: error locating server or instance specified
40 Named Pipes provider: could not open a connection to SQL Server
11001 WSAHOST_NOT_FOUND: host not found, no such host is known

Error 233, no process is on the other end of the pipe, looks similar and is not the same investigation. Microsoft documents it as SQL Server not listening on the Shared Memory or Named Pipes protocol, which means the client reached the machine and found the wrong protocol enabled rather than failing to find the machine at all.

Checking what is running from the server side

  • Get-Service | Where {$_.status -eq 'running' -and $_.DisplayName -like "sql server*"} lists the SQL Server services that are actually up, including the Browser.
  • In SQL Server Configuration Manager, a green arrow means running and a red square means stopped, for both the instances and the Browser.
  • The IP Addresses tab of TCP/IP properties tells you the truth about ports. A blank TCP Port with a value in TCP Dynamic Ports means the instance picks a port at every start.
  • SELECT @@SERVERNAME, SERVERPROPERTY('InstanceName'); on the instance itself settles arguments about what it is called.

Making it stop happening

Two changes remove most of the recurrence. Give every named instance a static TCP port and put that port in the connection string, which takes the Browser and UDP 1434 out of the path entirely. And use fully qualified names in connection strings, which takes the client’s DNS suffix search list out of it. Neither is a workaround; both are what Microsoft points at when the Browser cannot be reached, and both make the firewall rule you write today still correct after the next restart.

Every code this article covers

Code What it points at Source
53 The network path was not found. Windows ERROR_BAD_NETPATH, seen through the Named Pipes provider alongside error 40 Microsoft Learn
26 SQL Network Interfaces: error locating the server or instance specified. The discovery exchange produced no answer Microsoft Learn
40 Named Pipes provider: could not open a connection to SQL Server. A wrapper around whatever failed underneath Microsoft Learn
11001 WSAHOST_NOT_FOUND: host not found, no such host is known. Name resolution returned nothing Microsoft Learn

Confirm the fix worked

  1. Test-NetConnection <server> -Port <port> from the client that failed returns TcpTestSucceeded True.
  2. The plain connection string, with no explicit port, connects, which proves discovery works on its own.
  3. SELECT @@SERVERNAME, local_tcp_port FROM sys.dm_exec_connections WHERE session_id = @@SPID; confirms you reached the instance and port you intended.
  4. Restart the SQL Server service and confirm the port is unchanged, which proves it is static rather than dynamic.
  5. Test from a second client on a different subnet, so you know the firewall rule covers the range you meant.

Questions people ask about this

Do I need to open UDP 1434 as well as the TCP port?

Only if clients discover the instance through the SQL Server Browser. Microsoft’s documented alternative is to give the instance a static TCP port, put that port in the connection string, and leave UDP 1434 closed.

What is the difference between error 53 and error 26?

They fail at different points. 53 is the Windows network path error surfacing through the Named Pipes provider: the machine could not be reached or the name did not resolve. 26 is the client’s discovery layer failing to locate the instance you named, which usually means a wrong instance name or a Browser that is not answering.

Is any of this a licensing problem?

No. Connectivity behaves identically in every edition, including Express and Developer, and it costs nothing to fix. If somebody suggests an edition change solves error 26, they have misread the error.

Why does it work on the server but not from my desktop?

A connection made on the server usually goes over shared memory, which needs no network at all. That path succeeds even when TCP/IP is disabled or the firewall blocks everything, which is why local testing gives false confidence.

Express installs as a named instance. Does that matter?

It matters a lot here. A default SQL Server Express installation creates a named instance, so a connection string naming only the server fails with error 26 until you add the instance name or connect to an explicit port.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Error 512: Subquery Returned More Than One Value, and Related Query Failures Free Fix Error 3241: The Media Family on Device Is Incorrectly Formed License Error Error 701: Insufficient System Memory on a Memory-Capped SQL Server Edition Free Fix Service Error 1069 and 17058: The SQL Server Account Cannot Start the Instance
โ† Back to Knowledge Base