KB40375 - Always-On VPN Feature
KB40562 - VPN Only Access with Pulse Secure Desktop (Windows)
KB29805 - Pulse Connect Secure: Security configuration best practices
KB44417 - Best practices to configure split tunneling to exclude Office365 applications
TSB44404 - Important Information on How to Increase Remote Users on a Pulse Connect Secure Appliance
KB43612 - Details on why an IP address can be reused quickly by another user for a VPN connection
KB22509 - What server side logs will be required when I open a Network Connect (NC) or Pulse client case?
SA44328 - 2019-12: Out-of-Cycle Advisory: Vulnerability could allow attackers to sniff or hijack VPN Connections (CVE-2019-14899)
KB40791 - Windows Store is not reachable through a VPN tunnel from a domain-joined machine when Windows firewall is enabled for Domain profile
KB22889 - What PCS configuration is required for the VPN tunneling client to obtain an IP address?
What would you like to know?
< Back to search results
KB44402 - Bandwidth Management policy does not get enforced for VPN tunneling users.
Last Modified Date
3/18/2020 7:53 PM
This article describes an issue with Bandwidth Management not getting enforced for VPN Tunneling users.
Problem or Goal
Bandwidth Management policy does not get enforced for VPN tunneling users.
This issue affects all PCS versions.
This is caused due to an issue in the Traffic Control Rules.
The fix for this issue is tentatively expected in the July 2020 PCS 9.1R8 Release.
Was this article helpful?
Please tell us how we can make this article more useful.