When Pulse Desktop Client is connected with DENY split tunneling policies only configured and the route table is modified after tunnel is created, end user may notice that they are unable to connect to external resources, but resources through the tunnel continue to work.
This issue is applicable only to:
- Split tunneling polices are configured for DENY only
- Pulse Desktop Client (Windows) 9.1R3 to 9.1R6
- Pulse Desktop Client (Windows) 9.0R5 to 9.0R6