This is definitely an obnoxious bug. I just focused in on one user with the issue. One a Windows 10 machine, Pulse client, that user logs in to the PCS5000 and then can not pass traffic to anywhere in the ip network the appliance is configured to give him access to. As soon as he disconnects the session, he has working access to that network again. If I login to the appliance, on the same machine, I have no problem accessing the mentioned network. His broken access, versus it working for me, could not be corrected by anything, including removing the Pulse client completely from the machine, rebooting and reinstalling it. Problem remained. Clearing the user's session from the appliance side made no difference. If the user connects to the appliance from another Windows machine, he has no trouble at all, on that one, or from a Macintosh, as well. It's only when he connects to the appliance from his own machine, and it's only when he connects, not when someone else uses the same machine and their own credentials. I'm inclined to believe there's an issue on the appliance side where it's got something cached that tied to this user, from this machine, based on something it picks up from the Pulse client, which persists even after completely wiping out the client install and reinstalling from scratch. As far as I know, this issue wasn't cropping up before the 'upgrade' on the appliance from 9.1R1 to 9.1R2. I'm strongly feeling like just rolling back to 9.1R1 and hoping the developers will find and fix whatever's going on by a later release. Is roll back as simple as it appears, in the admin interface? -John
... View more
