KB43897 - After connecting with Pulse Secure Desktop client 5.3R6 and 9.0R2, the list of available wireless networks appears empty

« Go Back

Information

Last Modified Date	12/19/2018 4:27 AM

Synopsis

This article describes an issue where the available wireless network list appears empty after connecting with Pulse Secure Desktop client.

Problem or Goal

After connecting with a Pulse Secure Desktop (PDC) client on Windows, the available wireless networks are empty when clicking on the wireless network icon in the system tray. When viewing the System Services, the Network List Service service has been disabled.

This issue impacts the following versions:

Pulse Secure Desktop 5.3R6
Pulse Secure Desktop 9.0R2

Cause

This issue occurs due a change that was made in Pulse Desktop client 5.3R6 and 9.0R2 where the Network Location Awareness (NLA) service was being restarted after the tunnel was set up. The Network List Service (NLS) is dependent on NLA and is therefore gets disabled and restarted with the restart of NLA. Under certain scenarios, the NLS service fails to restart and stays disabled.

Solution

To resolve this issue, please upgrade to the following releases:

Pulse Secure Desktop 9.0R2.1 and above
Pulse Secure Desktop 5.3R7 and above

Note: The following code change is client-side only and is not necessary to upgrade the Pulse Connect Secure (PCS) server version.

Workaround:

Set the Network List Service service to manual and start the service from the Services menu.

From Windows, navigate to the Services MMC
From the right pane, find Network Listing Service (netprofm)
Double-click the Network Listing Service service
Modify the Startup type from Disabled to Manual

Check the service status and if it stopped, click Start.
Click Apply
Click OK

Related Articles

KB43897 - After connecting with Pulse Secure Desktop client 5.3R6 and 9.0R2, the list of available wireless networks appears empty

Information

Workaround:

Feedback

Was this article helpful?