Linked Server over VPN not working

  • Hello all,

    I can't manage to set up a Linked Server on SQL Server (A -> default instance) to SQL Server (B -> default instance) via VPN.

    SQL Server (A) is located within our company's domain, while SQL Server (B) is not. In SSMS I can connect to SQL Server (B) without any problems.

    To create the Linked Server I use:

    - SQL login ("Be made using this security context: <credentials> ").

    - the "IP, Port" respectively just the "IP". Both works for direct connections via SSMS.

    I have tried various configurations for this Linked Server, but I always get the error messages (Microsoft SQL Server, Error: 53) or (Microsoft SQL Server, Error: 10060).

    Can someone explain to me how to configure this Linked Server correctly, or if the problem lies elsewhere (maybe Firewall, Kerberos, etc.)

    Thank's for your help in advance!

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • Couple questions about this:

    1. Is the VPN a "soft" VPN that uses a software client to make the connection, or a "site-to-site" VPN established through your router / firewall / network hardware?
    2. When you connect to Server B, are you running SSMS on your workstation locally, or on Server A?
    3. And, if the VPN is a software client connection, where is the client running, locally on your workstation, or on Server A?

    My suspicion is that you're using a software VPN on your workstation, which is why SSMS will connect, but Server A cannot.

  • @jasona.work:

    Thanks for your help !!!

    Blocked ports in the firewall caused the problem. We use a s"site-to-site" VPN.

    I have overlooked that with a "Linked Server" the connection is made from the server on which the SQL instance is running, whereas a direct connection via SSMS is made from my local machine on which SSMS is running.

  • Glad to help!

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply