// SQL Server error reference

SQL Server error 53: Network-related or instance-specific

The client couldn't reach SQL Server at all: wrong server or instance name, the service is stopped, TCP/IP is disabled, or a firewall blocks the port.

Error number
53
Category
Connection and login
Error message
A network-related or instance-specific error occurred while establishing a 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

What it means

Error 53 comes from the client's network layer, not from SQL Server. It is the Windows error "The network path was not found", and it means the client never got as far as talking to the database engine, so no login was attempted.

The same family of failures shows up under other numbers depending on the client library: error 26 (Error Locating Server/Instance Specified) when a named instance can't be found, 10060 when the connection attempt times out, 11001 when the host name doesn't resolve, and "actively refused" when nothing listens on the port.

Common causes

  • The server name or instance name in the connection string is wrong, or points to another environment.
  • The SQL Server service is not running.
  • TCP/IP is disabled for the instance in SQL Server Configuration Manager, which is the default on some editions such as Developer and Express.
  • A firewall blocks TCP 1433 (or the instance's port), or UDP 1434 that the SQL Server Browser service uses to tell clients a named instance's port.
  • The SQL Server Browser service is stopped, so a named instance on a dynamic port can't be located.
  • The host name doesn't resolve, or resolves to a stale address.

How to fix it

  1. Check that the service is running, on the server, in SQL Server Configuration Manager (SQL Server Services) or the Services console.

  2. Connect with an explicit TCP address and port to take name resolution and the Browser service out of the picture: tcp:192.168.1.101,1433 (or the instance's port). If that works, the problem is the name, the instance lookup, or UDP 1434.

  3. Find the port the instance really listens on from its error log.

    EXEC sys.xp_readerrorlog 0, 1, N'Server is listening on';
  4. Enable TCP/IP under SQL Server Network Configuration, Protocols for the instance, then restart the SQL Server service.

  5. Allow the port through the server's firewall and any network firewall, and UDP 1434 if you connect to a named instance by name. Start the SQL Server Browser service for named instances on dynamic ports, or give the instance a static port.

  6. Test plain TCP reachability from the client with Test-NetConnection server -Port 1433 (PowerShell) or nc -vz server 1433.

Questions

Does error 53 mean my password is wrong?

No. The client never reached SQL Server, so credentials weren't checked yet. Fix the network path first; a wrong password shows up as error 18456.

Why can I connect on the server itself but not from my machine?

Local connections use shared memory, which skips the network. Remote connections need TCP/IP enabled, the right port and an open firewall.

Related errors

More connection and login errors

The code and message text are from the Microsoft Database Engine events and errors reference. Browse the full SQL Server error list or search every database error.

// fewer errors, faster fixes

Work on SQL Server in SQLly

A native SQL client for macOS, Windows and Linux with schema-aware IntelliSense, guardrails for risky statements and clear error messages, for SQL Server and the other databases you use.