Last night in my house I witnessed a prolonged discussion between two people of different
Problems connecting to your newly installed SQL Server instance? Did you happen to create a named instance (e.g.
Microsoft SQL Server named instances use dynamic TCP ports and rely on the SQL Browser service to provide the port number to the client in order to establish a connection. In a lot of cases I have seen people trying to connect to their new SQL Server named instance (e.g. sql01) and assuming that SQL Server was listening on port 1433. They open the Windows Firewall to allow inbound TCP traffic in on port 1433 but still cannot connect. Some even specify the port in the connection string if they can.
There are two options – rely on the SQL Browser service or change the named instance to operate on a fixed port.
Using the SQL Browser service
You need to be able to connect to the SQL Browser service (which is often not running) which operates on UDP port 1434. Even then, if your local Windows Firewall on the server hosting SQL Server does not allow inbound traffic on whatever TCP port is being used, then you won’t be able to connect remotely.
Make sure the SQL Browser service is running also, which you can configure in the SQL Server Configuration Manager.
Configuring SQL Server to listen on a fixed port
On the SQL Server, open up the SQL Server Configuration Manager, and navigate to SQL Server Network Configuration > Protocols for