We've suddenly started getting reports of users getting a "User input timeout. (Error:1382)" when trying to connect with Pulse. We use certificate based authentication so normally the user does not need to respond and there are no other pop-ups before the error message. In the logs on the appliance I can see the host checks (which include a machine certificate check) being passed successfully but then there is nothing. For one user I pointed the Pulse client to test realm using AD ID/password and this works without issue. It seems to be machine specific as the same user can connect on a different machine. We've tried re-issuing certificates, re-installing Pulse, recreating the connections and connecting to a different box but nothing seems to work. Any ideas? Most reports are coming from Asia (Korea and Vietnam). We are running version 8.1R3.2 with Pulse Client 5.1.3 (56743) on Windows 7 machines.
... View more