We are seeing the same issue as well. More and more now. Current version of PULSE is 18.104.22.1683
It only occurs when DNS is set to "Use Device Only" as that's the only setting that actually alters the DNS of the wireless interface. We changed ours to "Use Device first" and users no longer have the issue but that may not work for eveyone.
I have opened case 2018-0314-2209. They need me to capture the below logs. However the problem with that, is that I cannot re-create the issue. It happens randomly. The logs and debugging that needs to be turned on can not be left on. I need to be able to re-create the issue everytime or at least 25-50% of the time to capture the necessary logs. On both my Windows 10 machines, I am unable to recreate the issue. The client side logs are easy to capture, pending they are set to detailed.
you can understand why this is somewhat frustrating as it occurs randomly.
Logs from VPN appliance
- Policy Trace.
- IVE TCP Dump
- IVE Debug log with event codes
- System Snapshot.
- All IVE Logs.
Pulse (client side debug log)
Reference: KB17327 - How to collect the log file from Pulse Secure Desktop client?
.Open the Pulse client.
2.File > Logs > Annotate > Type the test without quotes “Secure-Logs”.
3.File > Logs > Log Level > Detail.
4.File > Logs > Save As.
To enable Policy Trace Logs on the IVE.
IVE TCP DUMP
IVE debug log and System Snapshot.
In the admin console, Maintenance--> Troubleshooting--> Monitoring -> Debug log.
Debug log size=50
Debug log level=10
Debug log event codes= ipsec,dhcp
Debug logging on.
In the admin console, Maintenance--> Troubleshooting--> System Snapshot click on the Take snapshot and save it.
In the admin console, Maintenance--> Troubleshooting--> Monitoring--> Save debug log.
To save ALL IVE Log file:
Given that reverting DNS settings to its orignal state is a client side functionality at least getting detailed level client side log and approximate time stamps should provide some starting point for support to see why the api/calls to revert DNS settings are failing.
I have seen this issue on W10 once in a while as well, does anyone know is has a solution been found?