Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Storyteller
New Contributor

Microsoft Teams and VPN IPsec dialup

We have a VPN IPsec setted by wizard to use by forticlient.

It seems that split-tunnel is disabled. If I connect and then go to internet I navigate by company ISP (tested by whatismyip). 

The VPN works like a charm but we cannot make call by MS Teams. The chat works but non video/audio call. I found that there are some problem with Teams. I would know if I can exclude the Teams connection from the tunnel using ipv4-split-include/ipv4-split-exclude settings or if there is any workaround.

 

[Update 20-03-02]

Using a VPN Native windows without split tunnel Teams works, calls included. The problem is Forticlient.

 

[Update 20-03-11]

Using Forticlient on MAC it works, only windows does not work.

 

[Update 20-03-12]

Group calls works. P2P calls no. There's a bug in the recent version of FC. Use version 6.0.0.0067 to solve the issue. It works.

 

Regards,

Graziano.

 

1 Solution
3d1l

I had to open a case with Microsoft support for this issue and the official response is that Teams does not work with VPN unless you enable the split tunnel option, and even with split tunel we have some users that have problems with the VPN active. This is the official article but the microsoft support technitian told me that without split tunnel Teams is not going to work.

 

https://docs.microsoft.com/en-us/microsoftteams/upgrade-prepare-environment-prepare-network

 

VPN

VPNs provide a valuable service to many organizations. Unfortunately, they're typically not designed or configured to support real-time media. Some VPNs might also not support UDP. VPNs also introduce an extra layer of encryption on top of media traffic that's already encrypted. In addition, connectivity to the Teams service might not be efficient due to hair-pinning traffic through a VPN device. Furthermore, they aren't necessarily designed from a capacity perspective to accommodate the anticipated loads that Teams will require.

The recommendation is to provide an alternate path that bypasses the VPN for Teams traffic. This is commonly known as split-tunnel VPN. Split tunneling means that traffic for Office 365 won't traverse the VPN but will go directly to Office 365. This change will have a positive impact on quality, but also provides the secondary benefit of reducing load from the VPN devices and the organization's network.

To implement a split-tunnel, consult with your VPN vendor for the configuration details.

0 Links

View solution in original post

18 REPLIES 18
donpinpon
New Contributor

Workaround sharing desktop first works because in that case you are creating a meeting though microsoft public servers as those server are acting as gateway traffic doesn't go directly between vpn users and forticlient is bypassed.

 

Any news about fortinet support?

Greg
New Contributor

The same issue.

Test results:

FGT200D v6.0.9 b0335 (default IPS, AV, WF) - IPSec VPN + FTC 6.0.9.0277: Skype - failed, Teams - failed

FGT200D v6.0.9 b0335 (IPS only) - IPSec VPN + FTC 6.0.9.0277: Skype - failed, Teams - failed

FGT200D v6.0.9 b0335 (default IPS, AV, WF) - IPSec VPN + Native VPN Win10: Skype - ok, Teams - ok

FGT200D v6.0.9 b0335 (IPS only) - IPSec VPN + Native VPN Win10: Skype - ok, Teams - ok

FGT200D v6.0.9 b0335 (default IPS, AV, WF) - IPSec VPN + FTC EMS 6.2.6 b0910: Skype - failed, Teams - failed

FGT200D v6.0.9 b0335 (IPS only) - IPSec VPN + FTC EMS 6.2.6 b0910: Skype - failed, Teams - failed

FGT200D v6.0.9 b0335 (default IPS, AV, WF) - IPSec VPN + FTC VPN 6.2.x: Skype - failed, Teams - failed

FGT200D v6.0.9 b0335 (IPS only) - IPSec VPN + FTC VPN 6.2.x: Skype - failed, Teams - failed

 

FGT30E v6.0.9 b0335 (default IPS, AV, WF) - IPSec VPN + FTC 6.0.9.0277: Skype - failed, Teams - failed

FGT30E v6.0.9 b0335 (IPS only) - IPSec VPN + FTC 6.0.9.0277: Skype - failed, Teams - failed

FGT30E v6.0.9 b0335 (default IPS, AV, WF) - IPSec VPN + Native VPN Win10: Skype - ok, Teams - ok

FGT30E v6.0.9 b0335 (IPS only) - IPSec VPN + Native VPN Win10: Skype - ok, Teams - ok

FGT30E v6.0.9 b0335 (default IPS, AV, WF) - IPSec VPN + FTC EMS 6.2.6 b0910: Skype - failed, Teams - failed

FGT30E v6.0.9 b0335 (IPS only) - IPSec VPN + FTC EMS 6.2.6 b0910: Skype - failed, Teams - failed

FGT30E v6.0.9 b0335 (default IPS, AV, WF) - IPSec VPN + FTC VPN 6.2.x: Skype - failed, Teams - failed

FGT30E v6.0.9 b0335 (IPS only) - IPSec VPN + FTC VPN 6.2.x: Skype - failed, Teams - failed

 

FGT30E v6.2.3 b1066 (default IPS, AV, WF) - IPSec VPN + FTC 6.0.9.0277: Skype - failed, Teams - failed

FGT30E v6.2.3 b1066 (IPS only) - IPSec VPN + FTC 6.0.9.0277: Skype - failed, Teams - failed

FGT30E v6.2.3 b1066 (default IPS, AV, WF) - IPSec VPN + Native VPN Win10: Skype - ok, Teams - ok

FGT30E v6.2.3 b1066 (IPS only) - IPSec VPN + Native VPN Win10: Skype - ok, Teams - ok

FGT30E v6.2.3 b1066 (default IPS, AV, WF) - IPSec VPN + FTC EMS 6.2.6 b0910: Skype - failed, Teams - failed

FGT30E v6.2.3 b1066 (IPS only) - IPSec VPN + FTC EMS 6.2.6 b0910: Skype - failed, Teams - failed

FGT30E v6.2.3 b1066 (default IPS, AV, WF) - IPSec VPN + FTC VPN 6.2.x: Skype - failed, Teams - failed

FGT30E v6.2.3 b1066 (IPS only) - IPSec VPN + FTC VPN 6.2.x: Skype - failed, Teams - failed

 

Skype and Teams work with old version of FortiClient 5.6.6.

Any idea how to setup Fortigate IPSec VPN and FortiClient 6.2.x without tunnel split?

 

 

jasonbeebe

My company is having the exact same issues.  We are using Forticlient 6.2.6.  I have logged a support case with Fortinet.  I will post if a solution is found.

Greg

No solution from support. I found in FTC 6.2.3 Release Notes: "581852 Skype call does not work through FortiClient (Windows) dialup IPsec VPN". The "newest" version which works for me is 6.0.2.0128. No information from support why FTC 6.0.9 and FTC EMS 6.2.6 b0910 blocks Skype and Teams.

Forget about FortiClient for Windows IPSec VPN. Buggy since 6.0.3.

Workarounds:

- IPSec VPN tunnel split (I now - risky)

- Native Windows Client

- SSL VPN

So many months with no solution. Frustrating.

jasonbeebe

I can second that there is no solution from support.  The response from them was:

 

This is a newly reported issue, and affects FortiClient versions 6.0.3 to 6.2.6. The issue seems to only affect users on IPSec VPN tunnels, SSL VPN connections have no issue. There is currently no workaround at present.

st3fan
New Contributor III

Same issue here. I find it disappointing how Fortinet Support is handling this issue. And I don't feel quite comfortable downgrading to version 6.0.0.0067 to be honest.

HoTiCE
New Contributor

Stay tuned, something might be in the works, we're currently testing a fix internally, I'll report back once we have something concrete.

 

Rest assured this has very high visibility due to the high profile of Teams right now in our current context

st3fan
New Contributor III

Ok great, this is good news.

 

Just received the following from support: "... this issue is been reported as BUG #0621313 and engineering is working to fix the issue."

jimmyt234

Bug 621313 has been resolved in FCT 6.2.7 as per release notes:

 

https://docs.fortinet.com/document/forticlient/6.2.7/windows-release-notes/22791/resolved-issues