Reset Search
 

 

Article

KB43703 - DNS client restart after VPN launch is not done on Windows 10 RedStone 3 and above

« Go Back

Information

 
Last Modified Date12/19/2018 4:30 AM
Synopsis
This article describes an issue were DNS client restart after VPN launch is not done on Windows 10 RedStone 3 and above.
Problem or Goal
On Windows 10 RedStone 3 and above, DNS client fail to restart after VPN launch.
This issue applies to both Network Connect and Pulse Secure Desktop client.

Network Connect and Pulse Secure Desktop client restarts DNS client service to prevent DNS resolution issues.  
This helps prevent DNS caching issues when hostnames resolve to different IP addresses in a pre VPN tunnel (external) vs post VPN tunnel (internal) scenario.
 
Cause
Windows 10 RedStone 3 and above has disabled manual start/stop of dnscache service.
When the Network Connect and Pulse Secure Desktop client is trying to restart the dnscache service, it is getting "Access denied error".
Solution
Pulse Secure has replaced dns client restart logic with "ipconfig /flushdns". 

Fix will be included with below builds:
  • Pulse Connect Secure 8.3R6 and above.
  • Pulse Connect Secure 9.0R2 and above.
  • Pulse Desktop client version 5.3R6 and above.
  • Pulse Desktop client version 9.0R2 and above.
Related Links
Attachment 1 
Created BySha Hussian

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255