- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FortiClient telemetry connection to EMS breaks MSTeams
Hi everyone,
I am facing a strange issue here:
One of our laptops has bad network quality on MSTeams as soon as FortiClient is connected to EMS.
The issue seems to appear only on WLAN, when Ethernet is connected via dockingstation (usb-c) everything works fine.
But as soon as the user moves to another location and uses WiFi MSTeams has lot of dropouts when on a call. I tried disabling all security profiles but the issue still appears.
Only thing that help is disconnecting the client from EMS in the zero trust telemetry section from FortiClient.
I also tried the versions 7.0.x and 7.2.x.
Any ideas?
The affected device is a Dell Precision 7680 with an Intel(R) Wi-Fi 6E AX211 card... I have found some older issues (2 years old) with FortiClient and Intel wifi cards but nothing related to MSTeams...
Solved! Go to Solution.
- Labels:
-
FortiClient EMS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So after hours of testing the issue has something to do with the users router at home.
It is a "tenda nova" device. Seems like this devices breaks FortiClient telemetry somehow and generates bunch of funny issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Have you checked if there are any VPN split traffic, ZTNA, or Inline CASB rules enabled for Microsoft Teams or other Microsoft traffic? Additionally, have you verified the on-net and off-net profiles in EMS?
Regards
Mahesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did disable all policies and rules, no further connections like VPN were used.
Have found nothing that could potentially block MSTeams.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So after hours of testing the issue has something to do with the users router at home.
It is a "tenda nova" device. Seems like this devices breaks FortiClient telemetry somehow and generates bunch of funny issues.
Created on ‎01-22-2025 06:08 AM Edited on ‎01-22-2025 06:09 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How did you confirm this "tenda nova" device is causing the issue?
Created on ‎01-22-2025 06:16 AM Edited on ‎01-22-2025 06:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The cable from the internet provider went directly into the tenda nova device so it worked as a router.
After plugging the cable from the internet provider directly into the users laptop and established a connection via PPPoE on the notebook everything went fine.
The user bought another router which now is sitting between the internet cable and the tenda nova devices. Now everything is working fine -> This was the moment when we realized the tenda nova device breaks something.
WLAN works fine now too via the tenda nova devices, the issue only appears when the tenda nova device runs as a router.
