So far, it is suspected a problem with the netshim driver getting properly inserted into the network stack (at the interaction level between Pulse Secure virtual adapter and Windows 10).ġ) Downgrade to any 2017 Windows 10 patch.Ģ) Disconnect from Pulse every 10 – 15 minutes. In order this setup, MTU of the Pulse Client adapter should be lower than the ExpressVPN adapter, as the encrypted data need to be passed through the ExpressVPN which will be get encrypted again and sent out through the physical Interface. OpenConnect is not officially supported by these network vendors (Cisco Systems, Juniper Networks, Pulse Secure, or Palo Alto Networks), However, if you’re using a Linux machine with no official or limited support, you should look at OpenConnect SSL VPN client instead to help you connect to your company’s VPN gateway. ![]() This is out of Juniper control as the SRX is doing properly its job.Ĭurrently, Pulse Secure is investigating the problem, and their developers have solicited to ATAC for time (over a week) as line code 5.1 is legacy for them and they are not familiar with the code. There are lists of reports about this problem recently in the past months, and it is due to interoperability between Pulse Secure client v5.1 and Windows 10 latest patches. ![]() Unfortunately there has been no real update for a few weeks now, but still hoping they will have a fix soon.įor me personally, I need a few logins before I get a fully functional tunnel but when it does connect, it's pretty much stable. ![]() Yes, I also have a case pending and they say Pulse is investigating the Legacy Code.
0 Comments
Leave a Reply. |