Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Firewall Port 1433 not opening

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 SQL Server remote connection on, followed the following steps....

1.Created Inbound and outbound rules for tcp port 1433.

2.In sqlserver configuration manager ,all is set for IP address and POrt no properties.

3.Set the SqlServer instance for remote connections.

But still its not working.

Also when i checked port 1433 for tcp on local computer it is shown closed.

thanks in advance.......

like image 203
Rohit Avatar asked Nov 09 '12 07:11

Rohit


People also ask

Why is port 1433 blocked?

Port 1433 disabled on the MS-SQL Server In previous versions of MS-SQL server, port 1433 was enabled (open) by default, but as a hardening procedure implemented to improve security of the MS-SQL server, port 1433 is disabled in current versions of MS-SQL Server.

How do I check if port 1443 is open?

Simplest way to do that is probably (on the server, in a cmd window) netstat -an | find "1443" and see what you get back. Second, if it's a TCP connection you're looking for, you may be able to telnet <hostname> 1443 and see if you get a connection.

Could not open connection to the host on port 1433?

- If you get 'Could not open connection to the host' then this is network problem. SQL Server: - Check to see if your SQL server hostname, username, and password is correct. - Check there is no firewall rule blocking TCP connection to port 1433.


3 Answers

  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
  1. 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

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

enter image description here

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

enter image description here

  1. 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.

enter image description here

like image 200
Friend Avatar answered Nov 04 '22 22:11

Friend


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/

like image 33
jmorris Avatar answered Nov 04 '22 23:11

jmorris


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

like image 45
twoleggedhorse Avatar answered Nov 04 '22 23:11

twoleggedhorse