KB43776 - Domain profile does not get assigned once Pulse VPN tunnel is connected.
KB22889 - What PCS configuration is required for the VPN tunneling client to obtain an IP address?
KB22977 - Pulse Secure Mobile support for VPN Tunneling profile proxy settings
KB44678 - Pulse Client users are being disconnected when Host Checker Re-evaluation or Dynamic Policy Re-evaluation is enabled
KB26796 - Is it possible to specify a port range in the VPN Tunneling split tunneling policy?
KB43874 - Session end script is not being executed for WSAM/VPN tunneling
KB19294 - Hosts file is modified/accessed when a VPN Tunneling client is launched
KB21644 - Is there a VPN Tunneling Access Control List (ACL) limit and how can it be calculated and optimized?
KB9232 - How proxy logic is applied with VPN tunneling
KB12536 - How to set up the Pulse Connect Secure to assign a VPN Tunneling IP address based on LDAP attribute
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
2/5/2021 6:37 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.
To resolve this issue, please upgrade to Pulse Connect Secure 9.1R8 and above.
Was this article helpful?
Please tell us how we can make this article more useful.