Unable to connect to remote SQL database using SQL Server Management Console (error 53)

Question

I opened port 1433 on my firewall, but every time I try to connect to my remote SQL database using the SQL Server Management Console, I get (Microsoft SQL Server, error: 53)

Answer 1

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
• Launch Validation Service
• TCP / IP Verification Enabled
• Check SQL Server Properties "Allow Remote Connections"
• Check if SQL Server is included in the restricted subnet

Then run them if they don’t allow

• Right-click on TCP / IP and select Properties.
• Make sure that in IP2, the IP address is set to the IP address of the computer on the local subnet.
• Scroll down to IPAll.
• Verify that TCP Dynamic Ports is empty.
• Verify that the TCP port is set to 1433.
• If you have a named instance, you must have SQL Server Browser Service enabled
• The browser service starts on UDP port 1434, and this should be enabled through your firewall.

Greetings Mary Pass, if not already allowed

• Go to the client computer and run cliconfg.exe. If named pipes are specified first, uncheck it and forward TCP / IP.
• check if the firewall is blocking the named pipe port, which is usually 445

Answer 2

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

From the Start menu in the Microsoft SQL Server folder, open the Configuration Tools folder and select SQL Server Configuration Manager.

In Configuration Manager, click the arrow next to SQL Server Network Configuration, then click "Protocols for {Instance}". {Instance} will be your installation, if this is the default instance, it will be MSSQLSERVER.

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

Answer 3

You can add. \ To the name of your server. For example, if the server name SQLEXPRESS changes it to. \ SQLEXPRESS will solve your problem.

Answer 4

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

Details: I received the following error from ISA when trying to connect from my SBS 2003 server to my remote MSSQL database provider through SQL Server Management Studio:

Connection rejected
Log Type: Firewall Service Status: The 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 accessible through another network adapter. Rule: Source: localhost (192.168.1.1:29859) Purpose: External (...: 139) Protocol: NetBios session

I get it. I had to add the Local Host as one of the sources for the ISA rule that I originally created to primarily allow connections from the SQL Server Management Console. This rule allowed the use of internal sources, but not the local host (127.0.01) needed for this scenario.

Answer 5

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

Answer 6

I could ping my SQL Virtual Machine server, but could not connect to it.
I disconnected the wired and wireless network adapters and then connected!

Answer 7

Here's how to fix it and get connectivity:

Press "WindowsKey + R" and enter services.msc. After the services open, scroll down and find the service. SQL Server Highlight the service and press "START". Wait for the service to start and retry connecting to your MSSQL instance. Now it should work again, and you can connect to the MSSQL instance and execute the queries.