SQL Remote Connections
-
I had SQL Remote Connections working on a clien't server. For some reason I can no longer connect. I'm getting
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
The network path was not found
I can remote into their server, I just can't connect to the DB either with SSMS or through my app. The ports are open, and SQL is configured for remote access. I've tried all the usual debugging techniques, [like this](https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine?view=sql-server-2017), but I can't get in. Anyone have any other ideas?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I had SQL Remote Connections working on a clien't server. For some reason I can no longer connect. I'm getting
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
The network path was not found
I can remote into their server, I just can't connect to the DB either with SSMS or through my app. The ports are open, and SQL is configured for remote access. I've tried all the usual debugging techniques, [like this](https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine?view=sql-server-2017), but I can't get in. Anyone have any other ideas?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Kevin Marois wrote:
provider: Named Pipes Provider
If you're using named pipes, you'll need to open port 445: Direct hosting of SMB over TCP/IP[^] Alternatively, configure the server and client to use TCP/IP: Configuring Client Network Protocols | Microsoft Docs[^] SQL Server Configuration Manager - SQL Server | Microsoft Docs[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Kevin Marois wrote:
provider: Named Pipes Provider
If you're using named pipes, you'll need to open port 445: Direct hosting of SMB over TCP/IP[^] Alternatively, configure the server and client to use TCP/IP: Configuring Client Network Protocols | Microsoft Docs[^] SQL Server Configuration Manager - SQL Server | Microsoft Docs[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Named Pipes is disabled in SQL Config Mgr. [I followed this to set up Remote Access.](https://www.top-password.com/blog/how-to-enable-remote-connections-in-sql-server/) I also opened ports 1433 and 1434 in Windows Firewall. Again, no joy
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Named Pipes is disabled in SQL Config Mgr. [I followed this to set up Remote Access.](https://www.top-password.com/blog/how-to-enable-remote-connections-in-sql-server/) I also opened ports 1433 and 1434 in Windows Firewall. Again, no joy
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
But your error message says you're using named pipes. Have you checked the client protocol configuration, as well as the server config?
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Kevin Marois wrote:
provider: Named Pipes Provider
If you're using named pipes, you'll need to open port 445: Direct hosting of SMB over TCP/IP[^] Alternatively, configure the server and client to use TCP/IP: Configuring Client Network Protocols | Microsoft Docs[^] SQL Server Configuration Manager - SQL Server | Microsoft Docs[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
In Server Explorer/Database Explorer click Connect to Database.
In the Choose Data Source dialog box, select Microsoft SQL Server, and then click OK.
Select a server name from the drop-down list, or type the name of the server where the database you want to access is located.data science with python online training data science online training
-
I had SQL Remote Connections working on a clien't server. For some reason I can no longer connect. I'm getting
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
The network path was not found
I can remote into their server, I just can't connect to the DB either with SSMS or through my app. The ports are open, and SQL is configured for remote access. I've tried all the usual debugging techniques, [like this](https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine?view=sql-server-2017), but I can't get in. Anyone have any other ideas?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Presuming you are NOT using named pipes and in fact the server is remote (different box) then the way to test connectivity is as follows. 1. Log in to the client box 2. Use telnet to access the other box 3. If telnet works then you have connectivity. If not then no connectivity. To use telnet you must have the 'host' (name or ip) and the 'port'. Telnet doesn't need to do anything other than connect. That is the entire test. If you do NOT have connectivity then one or more of the following is true 1. host is wrong 2. port is wrong 3. server is not up 4. server is not configured for the port you used (but see 1.) 5. Network is blocking traffic. This can include firewalls. If you do have connectivity then you have an incorrect assumption. For example your test used the wrong host/port or your application is using the wrong host/port.
Kevin Marois wrote:
For some reason I can no longer connect.
If it fact this is true. It worked at the install site and no longer does, then it suggests something changed in the install. For example 1. Configuration changed 2. Someone changed the stack. For example installed or changed a firewall. Don't forget the always wildly popular - the server just simply is not running.
-
But your error message says you're using named pipes. Have you checked the client protocol configuration, as well as the server config?
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Well, I have checked & rechecked all the settings.. Named Pipes s disabled everywhere that I can see. Still getting this error
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
