The problem is with WIndows 8.1 and Windows 10 machines that have updated to Microsoft's January 3rd updates and the Pulse Secure uses Host Checker at realm or role level. It stops the Host Checker call out to happen and rejects connection. What we did: Downloaded the 18.104.22.1683 Pulse Secure desktop client installer package uploaded to our MAG2600 (running 8.2R9 (build 58917)) Advised all clients to connect to their Pulse Secure desktop clients for the upgrade. -- then advised if it failed, they needed to uninstall and redownload the Pulse Secure desktop client from our VPN home page. Worked for our folks.
... View more