Home/Error Library/sqlserver-10060-10054-cannot-connect-transport-error

SQL Server

SQL Server 2017 - 2022Network & Connectivity

5 min read

A network-related or instance-specific error occurred... (provider: TCP Provider, error: 0 - 10060 / 10054)

SQL Server Remote Connection Drops: TCP/IP Configuration, SQL Browser & Firewall Triage

Resolving remote connection failures caused by disabled TCP/IP protocols, dormant SQL Server Browser services on named instances, and firewall rule blocks.

Reviewed by:Senior Database Architect & SRE (dataiotech Labs)

Tested Versions: SQL Server 2017 / 2019 / 2022

Operational Verification & Reliability Metadata

Last Technical Review: 2 Kasım 2026

Tested VersionsSQL Server 2019 CU27, 2022 CU14

Required PrivilegesSQL Server Configuration Manager and Windows Administrator

Risk Assessment

MediumProtocol configuration changes require restarting SQL Server service

Expected OutputTcpTestSucceeded: True on port 1433 via Test-NetConnection

Rollback Procedure:Revert TCP/IP settings via SQL Server Configuration Manager

Microsoft Docs: Network-related or Instance-specific Error

First 60 Seconds Emergency Protocol:

The error string is a symptom, not the root cause. Do not restart the server blindly. Run the diagnostic queries below to pinpoint the actual failure mode.

▸Symptom

Remote clients fail during TCP handshake:

plaintext

A network-related or instance-specific error occurred while establishing a connection to SQL Server.
(provider: TCP Provider, error: 0 - 10060 / 10054)

▸What You See in Production

SQL Server is running locally on the database host, but all remote application connections time out.

▸Root Cause Matrix

Probability	Root Cause	Description
%50	TCP/IP Protocol Disabled	TCP/IP disabled by default in SQL Server Configuration Manager.
%30	Firewall Ingress Block	Port 1433 blocked by host or network security groups.
%20	SQL Server Browser Service Stopped	Named instances require UDP 1434 to resolve dynamic ports.

▸EMERGENCY RUNBOOK (0-5 min)

powershell

# 1. Test port reachability
Test-NetConnection -ComputerName 10.0.0.5 -Port 1433

# 2. Enable SQL Server Browser service for named instances
Start-Service "SQLBrowser"

# 3. Unblock port 1433 inbound
New-NetFirewallRule -DisplayName "SQL Server 1433" -Direction Inbound -LocalPort 1433 -Protocol TCP -Action Allow

▸PERMANENT BLUEPRINT

1Static Port Standardization: Standardize all instances on static port 1433.
2Listener Decoupling: Connect via Availability Group Listeners.

▸Verification

powershell

sqlcmd -S tcp:10.0.0.5,1433 -U sa -Q "SELECT @@VERSION;"

Other Database Error Triage Playbooks

Other battle-tested diagnostic guides for high-severity database errors.

All Errors (82)

SQLSERVER5 min