VPN Access to Microsoft SQL Server

[Rodrigo_Castell]

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.

[PhoneBoy]

Define "issues."

What debug/logs have you taken?

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

[Rodrigo_Castell]

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.

[G_W_Albrecht]

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

[5f319058-606b-4]

I have the same issue. 

How did you resolve it?

[Tim_McColgan]

Having this issue now as well, anyone solve this? 

[Tim_McColgan]

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? 

[Pauwris]

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 "."