cancel
Showing results for 
Search instead for 
Did you mean: 

Authentication Rejected By Server Error: 1308

Not applicable

Authentication Rejected By Server Error: 1308

Hello,

 

I've been reciving this error when trying to login via Pulse. I'm not seeing anything in the logs on my end.

 

Any ideas?

 

Thanks!

5 REPLIES
Super Contributor

Re: Authentication Rejected By Server Error: 1308

Hi,

 

I understand the issue, suspect the issue with pulse and host checker, not sure whether you  have enabled  Hostchecker however the below two knoeldegebase links has more or less majority of pulse issues covered, please go through this. I am sure it will help you. 

 

http://kb.pulsesecure.net/InfoCenter/index?page=content&id=KB26427&smlogin=true

 

http://kb.pulsesecure.net/InfoCenter/indexpage=content&id=KB21443&actp=search&viewlocale=en_US&searc...

 

if the above KB's not resolving your issue, its important for us to look in to user access logs on IC and pulse client side logs.


Note: If I have answered your questions, you could mark this post as accepted solution, that way it could help others as well. Kudo will be a bonus thanks!

 

Regards,
Kannan

New Member

Re: Authentication Rejected By Server Error: 1308

If someone is facing this issue again in Jan 2018 on windows OS, you need to uninstall latest security update from microsoft, which is following. 

  1. 2018-01 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4056895)
  2. 2018-01 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 on Windows 8.1 and Server 2012 R2 for x64 (KB4055266)
New Member

Re: Authentication Rejected By Server Error: 1308

Any windows OS ?  Or Windows 10?

New Member

Re: Authentication Rejected By Server Error: 1308

Would updating to the newest Pulse client fix the issue? We had similiar issues and updating the client fixed the host checker rejection.

Highlighted
Occasional Contributor

Re: Authentication Rejected By Server Error: 1308

The problem is with WIndows 8.1 and Windows 10 machines that have updated to Microsoft's January 3rd updates and the Pulse Secure uses Host Checker at realm or role level.  It stops the Host Checker call out to happen and rejects connection.

 

What we did:

Downloaded the 5.3.4.1183 Pulse Secure desktop client installer package

uploaded to our MAG2600 (running 8.2R9 (build 58917))

Advised all clients to connect to their Pulse Secure desktop clients for the upgrade.

-- then advised if it failed, they needed to uninstall and redownload the Pulse Secure desktop client from our VPN home page.

 

Worked for our folks.