Pulse 9.0.3 1667 - Authentication window is not displayed

[aalmeida]

Hi,

I have been using pulse secure for 3 months, with no issues. 

Then, since a week ago, when I click connect, the authentication window is no longer being displayed. It opens only on the sistem tray and it is not possible to maximize it. So, I get timeout error and can't complete connection.

I've tried to update to a newer Java version, updating some network drivers and reinstalling pulse secure. Error persists.

Could someone help me on this issue?

Thanks,

Alex.

[zanyterp]

unfortunately, that is not something we have seen
can you work with your IT team to open a case with our support team to investigate further, please?

[[email protected]]

Hi Alex,

As @zanyterp mentioned, please create a support ticket with us for further investigation.

If possible, please share the step-by-step screenshots of the exhibited behaviour for our reference.

Thanks,
Ray.

[aalmeida · Accepted solution]

Hi,

Thank you very much for your suggestion.

I did not have time to investigate this issue. As it happened only in my notebook, I chose to format it.

Now it is working again.

Regards,

Alex

[[email protected]]

Hi Alex,

Glad to know that the issue was resolved. Thank you for updating the thread.

Thanks,
Ray.

[shawn925008]

Folks, 

I'm having the exact same problem here. The authentication windows doesn't pop-up but shows on my tray, which makes my session time-out as I can't input my credentials. 

Can you help? 

Thanks, 

Shawn 

[[email protected] · Accepted solution]

Open task manager, go to process tab, find the Pulse Secure tray process where you will find the authentication window child process.

Right click and choose bring it to front or maximize and see if that brings the window.

[shawn925008]

Thanks. Problem solved. Much appreciated. 

[adinozaur1]

Hello

Could you please advise what is actually causing this strange behaviour?

Is this a Pulse application error? Or is it influenced by other factors like: WIN? Linux systems?

We recently have faced this problem in our organization and it is creating a high number of incidents.

[[email protected]]

Unfortunately, we are not able to find out the root cause for this issue, since it happens only once on the user machine i.e. prior following the workaround which makes it hard to get reproduced and gather debug data.