Sql – Can’t Open Port 1433 on Window Server 2008 (attempting to connect to SQL Server 2008 Express)

sqlsql-server-2008windows-firewallwindows-server-2008

I'm trying to open Port 1433 on windows firewall but not having much luck.

I've added a new Inbound Rule (attempting to open TCP 1433) which looks okay and appears to be on but when I run netstat -an the server doesn't appear to be listening on Port 1433.

I've gone through the motions of setting SQL Server Express to not use dynamic ports (I looked down the list of IPs in the config manager and enabled the servers external IP, removed "0" from dynamic ports and added 1433).

I feel that this is an issue with the firewalling and wondered if anyone had any pointers on where I may be going wrong.

Many thanks,

Andrew

Best Answer

You should leave blank 'TCP dynamic port' field and add 1433 to 'TCP Port' field to disable dynamic port allocation for SQL Server Express instance.

Have you restarted SQL Server express after your configuration changes?

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

Firewall – SQL Server 2008 Remote Access

Check with your CoLo provider, they may be blocking access to port 1433. Many CoLos started doing this after the SQL Slammer went around a while back.

It's also recommended that you not try and access SQL Server's directly over the internet. Instead setup a VPN between the CoLo and your office and access the servers over this secure connection instead of over the public internet.

Best Answer

Related Solutions

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

Firewall – SQL Server 2008 Remote Access

Related Topic