Enabling the TCP/IP connection in the SQL Server Configuration Manager.
Overview
When installing SQL Server Express for the first time, network protocols such as TCP/IP and Named Pipes are disabled by default.
This means:
- You can connect locally (on the same machine)
- But remote connections will fail
- This is mostly to keep your database safe, but can create problems for networks
However, to allow connections to SQL Server over a network, these protocols (TCP/IP) must be manually enabled.
Common symptoms of this problem include:
- Connection timeouts when connecting remotely:
- "Timeout expired. The timeout period elapsed prior to completion of the operation, or the server is not responding. The statement has been terminated.
- Errors like:
- “SQL Server not found or not accessible”
- “A network-related or instance-specific error occurred”
To solve this problem please follow the steps below:
Step 1: Open SQL Server Configuration Manager
- Press Start
- Search for:
SQL Server Configuration Manager - Open the application
Step 2: Navigate to Protocol Settings:
You may see something like this:
The protocols may have different names depending on what your instance was called during setup.
Step 3: Enable TCP/IP and Named Pipes:
Please select the correct protocol and
Right-click TCP/IP → Click Enable
Right-click Named Pipes → Click Enable (Optional)
Step 4: Restart SQL Server Service:
You will now have to restart the SQL service that is running.
Right-click on your server instance and click on restart.
Once the restart has completed, the new setting will take effect.
This is the most common issue when trying to connect to SQL Express without success and should be step 1 in solving the problem.
If this does not resolve the problem, it may be worth looking into the firewall settings.
Want to learn more?
Online Help Manuals - Click here for the latest version
Learning Management System - Click here to login or here to request access
Comments
0 comments
Please sign in to leave a comment.