I'm a MAC user and have the same issue. MAC OS HighSierra 10.13.4 and version of PulseSecure is 5.3.5 (1491). I have tryied on macbook air and iMac with the same versions of software (iOS and PulseSecure). Tryied also with other Wifi sources (Hotspot from mobile devices, router wi-fi). Reinstalling application does not work also. I'm using Gemalto token with certificate, and before we migrate from Enpoint VPN client to Pulse Secure everything worked fine. Token drivers are embeded in macOS and I have izentpe card manager. After typing my PIN code for token connection returns error User input timeout. (Error:1382). On windows the same token and settings works fine. Please, help, because each time I have to run virtual machine with windows to connect my VPN.
Thanks in advance!
Does anybody check what is posting here, because there is no reply to my previous post???
Hello there, many posts do see a rapid reply, both from other community members, and from our engineers. In this case, it seems to be an older thread (2016), so it may help to post as a new thread, especially with the new information.
However, this seems to be very specific problem, so if you have a problem that needs immediate attention, we encourage all our users to raise a support call so we can track urgent problems.
Thank You pwallace, for answering to me!
I tought here is the right place for posting this issue, no matter if this problem was reported before 2 years. The problem is the same, error is the same. I already provided actual information about my operation systems, token, authentication, version of PulseSecure and so on. If additional information is needed I will provide it with pleasure.
If it's necessery I can open a new discussion about the problem, but there will be two topics with same subject.
ok - this is an informal community, and responses are not guaranteed - but if you raise a support ticket, then the support team aims to respond within a certain time, and to track to close.
Meanwhile, you might also check the "official" support knowledgebase on http://kb.pulsesecure.net: I found this article over there, which looks like it might be relevant to your problem:
This KB should be able to help: