Has anyone experienced blue screen of death with the latest Pulse Secure running on windows10?
We also have the symptom (possibly related) where all packets fail to get transfered to the wire. The leads to the user appearing to have a fully up tunnel but after a period of time the tunnel drops due to the server not receiving anything.
This happens on multiple machines but only a sub 5% of the 4000 win10 user base
I am also experiencing BSOD's but i am on Version 9.1r12.0 (b10249). This only happens when i have two connections connected.
I have several connections define on Pulse Secure (FIPS). One connects to our corporate network and another one to a Pulse secure gateway located at one of our DC's. If i connect to the corporate network only, everything is fine and the same when i connect to the DC only. If i connect to the secure gateway at the DC and then to the corporate network while connected to the DC, it connects without a problem, but soon afterwards i get the BSOD.
@ChristodeBeer I believe there's a known BSOD issue with PDC below 9.1R12 version wrt NET BUFFER corruption, hence please upgrade the PDC to 9.1R12 or above and check the behavior.
I suppose i should have started a new topic. As i mentioned in my first post i am running 9.1R12, but i will see if i can get hold of 9.1R13 and if that fixes the problem.
I seem to recall that two simultaneous connections have been allowed since version 9.1.3, and i have been connecting to two sessions simultaneously ever since. I have only been experiencing BSOD's for the last 3 months.
According to Pulse Secure Technical Publications. Overview of Pulse Secure Desktop Client.
"L3 and Pulse SAM Coexistence. L3 and Pulse SAM coexistence (supported on Windows only) enables the user to establish Layer 3 connection to Pulse Connect Secure and Pulse SAM connection simultaneously. This feature is available from 9.0R3 onwards."