To workaround this issue, use IP-based split tunneling instead of FQDN split tunneling if the problem is occurring for reboot scenarios.
- Sleep/hibernate scenarios are fixed only in Pulse Desktop Client 9.1R6 and above.
- An additional fix is planned for Pulse Desktop Client 9.1R7.1 (tentative for the week of July 20th) to address an issue where DNS settings are not properly restart during a reboot or restart scenario. The DNS restore process is abruptly stopped and the DNS restore is unsuccessful before reboot or restart occurs.
To help root cause the issue, please create the following registry entries for debugging purposes:
// Check the DNSRestoreNumTries value from registry and set the retry count, set this value to 10 (Decimal).
// "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Pulse Secure" : "DNSRestoreNumTries"
// Check the DNSRestoreLog *value from registry and enable the DnsRetry.log. Set this value to *1
// "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Pulse Secure" : "DNSRestoreLog"
By default, the number of DNS restore attempts is 5. Please try to increase to 10 and see if this improves the results. If not, please add a registry entry for the to enable the DNSRestoreLog
, replicate the issue and gather the Pulse Client logs to Pulse Secure support for additional review.