topic Re: VPN Access to Microsoft SQL Server in SASE and Remote Access

VPN Access to Microsoft SQL Server

Rodrigo_Castell — Thu, 06 Dec 2018 17:23:53 GMT

Hi Guys,

I'm running into issues connecting directly to MSSQL instance using Management Studio after connecting to the VPN client.

Everything else seems to be working fine, has anyone ran into this issue ?

We have migrated to a new cluster, old one was R77.30 and it was working fine.

This is on new appliances R80.10 Mobile Access and Endpoint Security Client E80.84.

Re: VPN Access to Microsoft SQL Server

PhoneBoy — Fri, 07 Dec 2018 00:44:37 GMT

Define "issues."

What debug/logs have you taken?

A tcpdump/Wireshark of traffic from the affected client might also be beneficial.

Re: VPN Access to Microsoft SQL Server

Rodrigo_Castell — Wed, 12 Dec 2018 21:30:52 GMT

Hi Dameon,

It seems that when I get ping working when connected to VPN all services work correctly.

When ping is not working, some work (RDP) others dont (mssql).

Using fw monitor I see traffic flowing correctly in both scenarios (ping working and not working). ICMP requests and replies have the same flow.

Re: VPN Access to Microsoft SQL Server

G_W_Albrecht — Fri, 14 Dec 2018 08:51:13 GMT

Is this the behaviour in the first two minutes after RA VPN connection?

Re: VPN Access to Microsoft SQL Server

5f319058-606b-4 — Mon, 09 Sep 2019 18:07:52 GMT

I have the same issue.

How did you resolve it?

Re: VPN Access to Microsoft SQL Server

Tim_McColgan — Thu, 30 Jan 2020 15:33:03 GMT

Having this issue now as well, anyone solve this?

Re: VPN Access to Microsoft SQL Server

Tim_McColgan — Tue, 31 Mar 2020 14:21:43 GMT

I am still having this issue and hit up good old google again to troubleshoot and ended up back here.

I can't use sql server managment studio (ssms) to connect to a default DB instance, but it works fine when connecting to a name instance. Has anyone fixed this?

Re: VPN Access to Microsoft SQL Server

Pauwris — Thu, 13 Oct 2022 09:35:26 GMT

My workaround for this VPN Software issue on SQL Server is to force connecting to MSSQL with IPv6 instead of IPv4.
So SQL Server local default instance name "::1" instead of "."