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.
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
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
I am experiencing the same issue with Teams running through a full tunnel with Windows. The calls will not connect. If I disconnect the FortiClient VPN the calls function properly. Did you ever find an answer to this issue?
Kevin,
there's a bug in recent version of Forticlient for W10, using MacOS the issue disappear.
You can workaround the issue using FC version 6.0.0.0067.
I've tested today with success and I'm doing a massive downgrade.
Regards,
Graziano.
Same issue... Where can FC version 6.0.0.0067 be downloaded from?
Hi, what firmware version are you running on your fortigate? we have a 1000c and are on 5.6.10 buiuld1677 (GA) and that is the highest version we can go up to.
I have tested multiple versions and the error first appears in version 6.0.3.0155 as when using version 6.0.2.0128 it works, we are going to log a support call with forti regarding this major issue.
Hi tarnend. I'd love to know what FG Support recommends. A downgrade for us is not possible at this time. I am not sure if we can get around it by using a split tunnel. I was going to test that when we hit a maintenance window. Or switch everyone to a Windows Native setup which in testing allows Teams calls to go through.
We are having this problem as well.
What works.
[ol]What does not work.
[ol]Here is an interesting work around.
In a 2 person chat (connected over VPN), you can click "Screen Sharing" first.
Once it connects, the user can then connect audio and/or video successfully. (and optionally stop screen sharing)
Anyone any update on this? I have logged this with Fortinet support but not having any luck with them.
Hi - I have the same problem with IPsec VPN. When I use SSL VPN instead it works
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
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1712 | |
1093 | |
752 | |
447 | |
231 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.