Firewall Port 1433 not opening

Question

I am using MS Server 2008 with MSSQL 2008-R2 as database server.

Each time for some work i have to login to server via Remote connection.I tried to configure the S

Answer 1

If you're trying to connect to an SQL Server Express instance as is my case right now... it doesn't use port 1433 by default. One must check the IpAll => TCP Dynamic Ports in Sql Server Configuration Manager. Mine is 52848.

After entering the correct port 52848 in DbSchema app (the one I'm trying to use), it connected successfully.

Check the following screenshot:

This is the way to go:

The default SQL Server express installation does not enable TCP network protocols, so here are some steps to take to be able to communicate with SQL Server Express. These steps should be similar for MS SQL Server Express 2017, 2016, 2014, 2012, 2008, and 2005.

1. Launch the SQL Server Configuration Manager. It should be in the Start -> Programs -> Microsoft SQL Server 2005 -> Configuration Tools start menu option.

2. Select the SQL Server 2005 Network Configuration tab. There should be a Protocols for SQLExpress option, and one of the protocols should be TCP IP.

3. Enable the TCP IP protocol if it is not enabled.

4. The default port for SQL Express may not be 1433. To find the port it is listening on, right-click on the TCP IP protocol and scroll all the way down to the IP All heading. There should be a section called TCP Dynamic Ports. This should list the port SQL Express is listening on. You can then put this value into the port field when adding the connection profile via RazorSQL.

Make sure to restart SQL Express before trying to connect.

Text kindly reproduced from: https://razorsql.com/docs/support_sqlserver_express.html

Answer 2

I had multiple NICs in my server. When I went to SQL Server Network Configuration -> TCP/IP and right clicked for properties there was a list of the NICs and at the bottom was the open port for my SQLEXPRESS. It was not 1433..... I do not know if there is a default but mine was in the 49,000 s.

Answer 3

1. Probably port 1433 is disabled, so enable it using MS WIndows firewall.

or just use

netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = SUBNET profile = CURRENT

2. Probably MS SQL Server Browser Service is not running. So go to Services and start it.

or just execute under Run menu

%windir%\system32\services.msc

3. Probably TCP/IP channel is disabled under SQL Server 2008/2014 Configuration Manager. SO go there and enable all TCP/IP options.

4. Just in case at the same place (SQL Server 2008/2014 Configuration Manager) make sure you have 1433 port.

5. Make sure that SQL server is configured to allow remote connections. Use MS SQL Management Studio and right click on the top node which server itself.

Answer 4

If named pipes and TCP/IP access are already enabled in SQL Server Configuration Manager, then you need to either add a rule for UDP port 1434, or a rule for sqlbrowser.exe so that the SSMS client can talk to the SQL Server Browser service.

I actually see people having this problem surprisingly often so I wrote up an explanation here: http://blog.dereenigne.com/microsoft-sql-server-dynamic-ports-windows-firewall-and-you/

Answer 5

In the SQL Server Configuration Manager->SQL Server Network Configuration->Protocols, check that named pipes and tcp/ip are enabled.

If that doesn't work then it may be your firewall blocking it, try this link: http://msdn.microsoft.com/en-us/library/cc646023.aspx

This may be useful too: http://support.microsoft.com/kb/287932