KB44202 - macOS Catalina (10.15) support
SA40005 - Details on fixes for OpenSSL "Heartbleed" issue (CVE-2014-0160)
SA44101 - 2019-04: Out-of-Cycle Advisory: Multiple vulnerabilities resolved in Pulse Connect Secure / Pulse Policy Secure 9.0RX
KB9218 - What client side logs are required when I open a Network Connect (NC) or Pulse Secure Client VPN case?
KB29135 - Unable to pass traffic through Pulse Secure Mobile Client on iOS after upgrade to Pulse 184.108.40.206105
KB44113 - Pulse iOS client : Unable to connect using Pulse Secure Mobile client for iOS 220.127.116.11829 & above
KB44312 - Pulse Desktop Client end users are unable to reach resources via proxy server after upgrading to macOS 10.15
KB19298 - End user Frequently Asked Questions (FAQ) for Pulse Mobile Client for Android
SA40312 - September 22 2016 OpenSSL Security Advisory
KB43785 - Pulse Mobile for iOS is intermittently disconnecting and end users are unable to connect after upgrading to Pulse Mobile for iOS 18.104.22.168583
What would you like to know?
< Back to search results
KB44347 - Unable to reach resources through tunnel when using Pulse Mobile iOS Client version 9.0.0 (Build 79839)
Last Modified Date
1/17/2020 10:00 PM
This article describes an issue where Pulse Mobile (iOS) users are not able to access resources via tunnel when using Pulse Mobile (iOS) version 9.0.0 (Build 79839)
Problem or Goal
After upgrading to Pulse Mobile (iOS) Client 9.0.0 (Build 79839), users are unable to access resources via tunnel.
The issue is not observed when connecting to Pulse Connect Secure running 9.0 or 9.1 releases
The issue is applicable when all conditions are met:
Using Pulse Mobile (iOS) Client 9.0.0
Connecting to Pulse Connect Secure device running 8.3R7 and below
Split tunneling is disabled
This does not impact:
Pulse Connect Secure devices running 9.0RX and above
Split tunneling enabled
This issue is fixed in Pulse iOS Mobile Client version 9.0.1 build 79931 and is now available on the Apple App Store.
To workaround this issue, please upgrade to the latest versions.
For those who are using MAG series, please use the following workarounds :
1. Enable split tunneling for the particular role with a single deny policy(can be any dummy IP) which will create an *:* allow policy and will route all traffic via tunnel like full tunnel mode.
2. Enable split tunneling for the particular role with allow policies to resources under split tunneling networks.
Was this article helpful?
Please tell us how we can make this article more useful.