Remote Access - Third Party VPNs

Please note this article is specifically written in reference to 3rd parties ONLY 

Please review our Remote Access article for the explanation on remote access that is included with all MDS subscriptions.


Types of 3rd Party VPN scenarios:


Type A) Site-to-Site (Always on VPN) via MDS:

Some vendors establish connections to enable the customer to access hosted resources via a VPN tunnel (i.e. Azure, Amazon, other hosting environments etc.).  This is considered a 3rd Party Site-to-Site VPN tunnel.

MDS can enable customer to connect with 3rd party site-to-site connections but only with the follow pre-requisites met.

#1 -Multisite is required for 3rd party VPN integration

#2 - Vendor and/or customer will facilitate all needed information and send into MDS support well in advance.  This allows for a timely to review for MDS to go over 3rd Party Vendors requirements and to allow ample time to identify any possible adjustments needed to successfully terminate the client behind MDS to their 3rd party tunnel vendor.


Type B and C: Client Based VPN access via MDS providing access to an external resource

This is accomplished by the customer using a vendor provided application such as Cisco AnyConnect or other on-demand access type solution.  Please review the 2 types of versions of 3rd party client based VPNs.

B) - Source: MDS Client & Destination: Not on MDS: Yes, MDS does allow for the use to outbound VPN connections. MTU may need to be adjusted on client. Security Bypass entry can be added to trusted destination VPN server so that MDS security does not “interfere” with the connection

C) - Source: MDS Client & Destination: MDS Client (2 diff companies): Yes, MDS does allow for connections between sites via our included Remote Access. This must be enabled for the target MDS subscription/client site. If partner is hosting their own VPN services and using port forwarding via MDS, that is up to the partners configuration.


Special note on (C), if both MDS subscriptions are on the same node there may need to be some adjustments to get this to work properly.  I.E. if its many to one (Many clients on MDS connected to single partner subscription on MDS) then we would move the target subscription to a different node.

Have more questions? Submit a request
Powered by Zendesk