FortiClient
FortiClient proactively defends against advanced attacks. Its tight integration with the Security Fabric enables policy-based automation to contain threats and control outbreaks. FortiClient is compatible with Fabric-Ready partners to further strengthen enterprises’ security posture.
jkoay
Staff
Staff
Article Id 350582
Description

This article describes how to identify process names involved to be excluded them from the VPN tunnel. Application-based split tunneling allows the definition of high bandwidth-related applications or specific traffic applications to be excluded from the VPN tunnel, instead having it routed out via local network adapter.

Scope

FortiClient 7.4 and above, v7.2 and above. v7.0 and above.

Solution

In this example, there is a requirement to exclude any traffic from the local application 'SplashtopSOS.exe' towards the VPN tunnel.

 

Picture1.png

 

To identify process names involved in establishing network connections externally when SplashtopSOS.exe is launched, open Task Manager -> Performance -> Open Resource Monitor.

 

Expand the Network section and verify the process name that is launched and running with SplashtopSOS.exe. In this case, SplashtopSOS.exe is not establishing a network connection, but rather it is SRManagerSOS.exe.

 

Picture2.png

 

With the correct process name identified, access to FortiClient EMS console -> Endpoint Profiles -> Remote Access -> Edit the affected profile -> VPN tunnels -> Edit VPN tunnel -> Split Tunnel -> Application-Based.

 

Enable Application Based

Type: Exclude

Local Applications -> Add

 

Picture3.png

 

Picture4.png

 

Picture5.png

 

Select the Save button and Save again to commit changes.

 

Results:

'SplashtopSOS.exe' application traffic is not forwarded to the SSL VPN Virtual Adapter interface. Instead, traffic is forwarded out through an Ethernet adapter. 

 

Picture6.png

Contributors