SQL Remote Connection Problem
-
I have been trying forever to set up access to SQL Server on my home server. I again followed all of the instructions here: [https://medium.com/developer-diary/how-to-enable-remote-connections-to-sql-server-dc5b6c812b5\](https://medium.com/developer-diary/how-to-enable-remote-connections-to-sql-server-dc5b6c812b5) Windows Firewall is off. When I try to connect remotely I get
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)
This message mentions 'Named Pipes'. Named pipes is enabled, although from what I can see, Named Pipes are for inter-process communication to occur among processes running on the same machine, so I'm not sure what this is part of the error. At this point I'm out of options. I've tried eveything I can think of. What could possibly be wrong here??
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I have been trying forever to set up access to SQL Server on my home server. I again followed all of the instructions here: [https://medium.com/developer-diary/how-to-enable-remote-connections-to-sql-server-dc5b6c812b5\](https://medium.com/developer-diary/how-to-enable-remote-connections-to-sql-server-dc5b6c812b5) Windows Firewall is off. When I try to connect remotely I get
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)
This message mentions 'Named Pipes'. Named pipes is enabled, although from what I can see, Named Pipes are for inter-process communication to occur among processes running on the same machine, so I'm not sure what this is part of the error. At this point I'm out of options. I've tried eveything I can think of. What could possibly be wrong here??
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
What do you mean by "remotely"? Something else on the same LAN, or something outside of your network? Check which client protocols are enabled on the computer that's trying to connect. If it doesn't have the SQL configuration tools installed, you'll need to run
cliconfg.exefrom bothC:\Windows\System32\(64-bit) andC:\Windows\SysWow64\(32-bit). Also check your connection string to make sure you're using the correct server and instance name. For example, ".\SQLEXPRESS" won't work from a remote computer.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
What do you mean by "remotely"? Something else on the same LAN, or something outside of your network? Check which client protocols are enabled on the computer that's trying to connect. If it doesn't have the SQL configuration tools installed, you'll need to run
cliconfg.exefrom bothC:\Windows\System32\(64-bit) andC:\Windows\SysWow64\(32-bit). Also check your connection string to make sure you're using the correct server and instance name. For example, ".\SQLEXPRESS" won't work from a remote computer.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Remote from my office to my home server. I connect using my IP addrss.
Richard Deeming wrote:
Check which client protocols are enabled on the computer that's trying to connect. If it doesn't have the SQL configuration tools installed, you'll need to run
cliconfg.exefrom bothC:\Windows\System32\(64-bit) andC:\Windows\SysWow64\(32-bit).Well, that did it!!! Wow, I've been trying on & off again for MONTHS to get this to work. THANK YOU!! I've set up SQL Remote access before, and I don't remember ever having use 'cliconfg.exe' before. Is this documented somewhere?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Remote from my office to my home server. I connect using my IP addrss.
Richard Deeming wrote:
Check which client protocols are enabled on the computer that's trying to connect. If it doesn't have the SQL configuration tools installed, you'll need to run
cliconfg.exefrom bothC:\Windows\System32\(64-bit) andC:\Windows\SysWow64\(32-bit).Well, that did it!!! Wow, I've been trying on & off again for MONTHS to get this to work. THANK YOU!! I've set up SQL Remote access before, and I don't remember ever having use 'cliconfg.exe' before. Is this documented somewhere?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I can't see an MS documentation, but there are various blogs describing the tool - for example: How to setup and use a SQL Server alias[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I can't see an MS documentation, but there are various blogs describing the tool - for example: How to setup and use a SQL Server alias[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Awesome, thanks!
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
What do you mean by "remotely"? Something else on the same LAN, or something outside of your network? Check which client protocols are enabled on the computer that's trying to connect. If it doesn't have the SQL configuration tools installed, you'll need to run
cliconfg.exefrom bothC:\Windows\System32\(64-bit) andC:\Windows\SysWow64\(32-bit). Also check your connection string to make sure you're using the correct server and instance name. For example, ".\SQLEXPRESS" won't work from a remote computer.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Well, I'm back to this again. You helped me get remote access working, and now I can't connect again. Again, I'm not 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)
I have not made any changes to either the server or the client. UPDATE> I take all this back. As soon as I posted I thought, I'll give it one more try - and it connected :confused::confused::confused:
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Well, I'm back to this again. You helped me get remote access working, and now I can't connect again. Again, I'm not 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)
I have not made any changes to either the server or the client. UPDATE> I take all this back. As soon as I posted I thought, I'll give it one more try - and it connected :confused::confused::confused:
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:
I take all this back. As soon as I posted I thought, I'll give it one more try - and it connected
Isn't that always the way it goes? :laugh: Glad you got it sorted.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
