Sql-server – Firewall blocking SQL Server named pipes

named-pipessql serverwindows-firewall

If I turn off the firewall on Windows SBS 2011, I can connect to my SQL Server 2008 non-default instance by name (which I presume means it's using named pipes) without incident. After I turn it back on, I can't. I have unblocked incoming TCP and UDP ports 135, 139 and 445.

What am I missing?

Best Answer

Here is a link that explains what you could do to resolve this issue

http://msdn.microsoft.com/en-us/library/ms175043.aspx

Related Solutions

Firewall – Remote connection sql server not working but if firewall disabled it does

Probably you forgot to execute this command:

 netsh firewall set portopening TCP 1433 "SQLServer"

You could try out the new "Fix it" feature of this Microsoft support article: How do I open the firewall port for SQL Server on Windows Server 2008?

The page also contains a script, delete the lines, if you don't need SQL Service Broker, debugger, https etc.

@echo =========  SQL Server Ports  ===================
@echo Enabling SQLServer default instance port 1433
netsh firewall set portopening TCP 1433 "SQLServer" 
@echo Enabling Dedicated Admin Connection port 1434
netsh firewall set portopening TCP 1434 "SQL Admin Connection" 

...

netsh firewall set portopening UDP 1434 "SQL Browser" 
@echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK)
netsh firewall set multicastbroadcastresponse ENABLE

SQL Server 2008 R2 – Resolving Named Instance Connectivity Issues

Try disabling your firewall, as it might block port 1434 for SQL Browser

Best Answer

Related Solutions

Firewall – Remote connection sql server not working but if firewall disabled it does

SQL Server 2008 R2 – Resolving Named Instance Connectivity Issues

Related Topic