Wireless DNS settings are not reverted after logging out from Pulse

[Guapista]

For certain users on Win7, it has been detected that after logging out from the VPN (using split tunneling and Search device DNS only setting) the Wireless adapter is not taking back the proper settings for DNS (to dynamic but remains static) and and user is not able to browse over the Internet.

The DNS setting for the Wiresless adapter changes to static when connected to the VPN, but remains in static mode after logging out. That's the problem.
If we manually changed them to DYNAMIC, then the problem gets fixed.

I have seen some problems with the network adapter for Win8 or Win10 when using Jabber. In our case, we are using Win7 but maybe there are also some issues we may need to take into account.

This issue is not happening all the time for the end users, and of course, not for all the users.

Can anyone help?

Thanks!
Elena

[josemartinezadm]

Hi,

I've been having the same issue with multiple computers mostly Windows 10. The same behavior DNS settings on the wireless settings.

Did you manage to get any help from support or a solution to this problem?

Thanks,
Jose

[Filbert]

Did anyone come up wih a solution for this? We are now seeing the same issue.

[zanyterp]

What version of Pulse?
Does it happen only with search device DNS only?
Is the session being logged out or is the system being turned off?

[[email protected]a.com]

We are seeing the same issue as well. More and more now. Current version of PULSE is 5.3.4.1183

thank you

Sean

[zanyterp]

Can you please open a case with support so we can look at this further with our development team?
Are you seeing it only with search device DNS as well?

[Filbert]

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. 

[[email protected]a.com]

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.

1. In the admin console, choose Maintenance > Troubleshooting > User Sessions > Policy Tracing.
2. In the User field, enter the IVE username of the user you want to trace.
3. In the Realm field, select the user’s realm.
4. Under Events to log, select the types of events you want to <select> to the policy trace log file & also select Pre-Authentication, Authentication & Role-mapping.
5. Click Start Recording.
6. Login as the user to sign into the IVE after you have started recording.
7. Click View Log to see the log entries.
8. Click Stop recording when you have obtained enough information.

IVE TCP DUMP

1. In the admin console, choose Maintenance > Troubleshooting > Tools > TCP Dump.
2. Delete the Dump file if you already find any.
3. If we are using both external and internal interface, enable both the IVE ports on which you want to sniff network packet headers.
4. If we are using only internal port, make sure enable internal port to sniff network packet headers.
5. Turn off Promiscuous mode to sniff only for packets intended for the IVE.
6. Click Start Sniffing.
7. Click Stop Sniffing to stop the sniffing process.
8. Click Download to download the file to a network machine

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:

1. In the admin console, choose System > Log/Monitoring > Select Event.
2. Click Save All Logs, navigate to the desired network location, enter a file name and then click Save to manually save the log file.

thank you

Sean

[ruc]

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. 

[EdwinF]

Hi all,

I have seen this issue on W10 once in a while as well, does anyone know is has a solution been found?

Best Regards,

Edwin