I connect to work network via Cisco VPN from my work laptop, which is on AD.
I am using SQL authentication to connect from Server A to B; in scenario #1 I can connect. I can even connect from localhost to Server B. So, I'm wondering why I can't establish linked server connection when I use connect to Server A via SSMS and then try to setup the linked server connection.
I do have a sneaking suspicion the issue with trying to create connection via SSMS might be the VPN/firewall since I can establish the linked server connection when I RDP into server A.
- RDP into Server A (on same AD as my work laptop)
- use SQL Server 2005 Management Studio and estable Linked Server connection to Server B (on same AD)
- I am able to successfully test the Linked Server connection to Server B from Server A
Connect to Server A's SQL Server using SQL Server 2005
Try to establish linked server connection from Server A to Server B inside SSMS
The connection fails and throws the following error message:
Named Pipes Provider: Could not open a connection to SQL Server . OLE DB provider
"SQLNCLI" for linked server "" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.". (Microsoft SQL Server, Error: 5)
Questions Any ideas why? Is there something on my laptop that is blocking the linked server connection? The reason why I need a linked server connection is so that I can run internal desktop applications; my workaround is to RDP into another server so that I can establish linked server connection