Cannot connect to remote SQL Database with SQL Server Management Console (Error 53)

Question

I have opened up port 1433 on my firewall, but every time I try and connect to my remote SQL Database with SQL Server Management Console I receive (Microsoft SQL Server, Err

Answer 1

Here is the how to fix it and gain your connectivity back:

Click WindowsKey + R and enter services.msc Once Services opens scroll down and locate service SQL Server Highlight the service and click START Wait for the service to start and retry to connect to your MSSQL instance It should now work again and you will be able to connect to your MSSQL instance and run queries.

Answer 2

What you need to do is go into SQL Server Configuration Manager where SQL Server is installed.

In the Start Menu, under the Microsoft SQL Server folder, open the Configuration Tools folder and select SQL Server Configuration Manager.

In the Config Manager, click the arrow next to SQL Server Network Configuration, then click on "Protocols for {Instance}". {Instance} will be your install, if it's the default instance it will be MSSQLSERVER.

On the right side, make sure that TCP/IP is "Enabled". Double click TCP/IP, in the window that opens, change the drop down to "Yes".

Answer 3

I could ping my Virtual Machine SQL server but couldn't connect to it.
I disabled my wired and wireless NICs and then it connected !

Answer 4

https://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx

http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/

http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx

Enable remote connections for SQL Server Express 2012

Short Answer

• Check Firewall
• Check Service is Running
• Check TCP/IP is Enabled
• Check SQL Server Properties "Allow Remote Connections"
• Check if the SQL Server is on a restricted subnet

Then Run these if Those Do not Resolve

• Right-click on TCP/IP and select Properties.
• Verify that, under IP2, the IP Address is set to the computer's IP address on the local subnet.
• Scroll down to IPAll.
• Make sure that TCP Dynamic Ports is blank.
• Make sure that TCP Port is set to 1433.
• If you have a named instance then you must have the SQL Server Browser Service enabled
• The browser service runs on port UDP 1434 and this must be allowed through your firewall

Hail Mary Pass if this is Still not Resolved

• Go to the client machine, and run cliconfg.exe If named pipes is listed first, demote it, and promote TCP/IP.
• check if the firewall is blocking the named pipes port, which usually is 445

Answer 5

I have solved this problem. Please refer to this thread: http://social.technet.microsoft.com/Forums/forefront/en-US/d2624655-e6ff-4947-b1a8-a2edcffd8a21/denied-connection-netbios-session-protocol#68321990-4ac4-46fa-b7f8-9e0ded3234bb

In detail: I was receiving the following error from ISA when trying to connect from my SBS 2003 Server to my offsite MSSQL Database Provider via SQL Server Management Studio:

Denied Connection
Log type: Firewall service Status: A packet generated on the local host was rejected because its source IP address is assigned to one network adapter and its destination IP address is reachable through another network adapter. Rule: Source: Local Host ( 192.168.1.1:29859) Destination: External (...:139) Protocol: NetBios Session

I have figured this out. I had to add "Local Host" as one of the sources for the ISA Rule that I had initially created to allow SQL Server Management Console connections in the first place. That rule was allowing "Internal" sources but not the Local Host (127.0.01), which is needed for this scenario.

Answer 6

in SSMS while opening give the server name as your_Hostname\your_sqlservername (give both the names as applicable instead of local or just only servername) it works fine.