TLS Error - Logging on to 365

[GreyFox]

Hi guys,

 

Apologies if this isn't the right forum to post this in, it could fall under a few categories. We're having some intermittent issues some random PCs and laptop, where a user tries to log onto the Office 365 portal, it hangs for ages, then pops up with the following message:

 

"This page can’t be displayed

 

Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such as RC4 (link for the details), which is not considered secure. Please contact your site administrator.

 

Change settings" (being a link)

 

The above are all turned on. Any assistance would be greatly appreciated.

 

Thank you

 

Grey Fox

[mrwoberts]

Hi Grey

 

I spotted these two commands recently (below), added to the Active Setup\Installed Components registry area. I believe they appeared following an update.

I'll see if I can find out which update is responsible so you can see if you have that update installed...

 

Anyway, try these commands then restart the affected PC before you see if it has resolved the issue.

C:\Windows\System32\ie4uinit.exe -DisableSSL3
C:\Windows\System32\ie4uinit.exe -EnableTLS

 

FYI, my file version of ie4uinit.exe is 11.0.9600.18500, modified 30/09/2016

 

It's also worth double checking if those PCs have an accurate time/date set - synced with the server.

 

EDIT:

Here are my findings, but I don't think these are responsible for those entries, I think an IE11 update has added them...

KB3080079  Update to add RDS support for TLS 1.1 and TLS 1.2 in Windows 7
KB2977292  Security update for Microsoft EAP implementation that enables the use of TLS: October 14, 2014
KB3154518  Support for TLS v1.2 included in the .NET Framework 3.5.1

 

EDIT2::

 

Aha!

KB3038314, which disabled SSL 3.0 by default in Internet Explorer 11

However, that particular updates would almost certainly be included with the most recent IE11 Cumulative Update KB3185319, so I would install that if you haven't done so already.

 

Might be worth waiting for a few others to reply first though, just to make sure I'm on the right track; I may be way off and this is an easier fix that I'm suggesting

Edited October 25, 2016 by mrwoberts

[GreyFox]

Hi MrWoberts,

 

Thank you for your response. I've passed that information on to my colleague. We'll have to wait for another PC to act up now, then investigate.

After being brought back to our office yesterday, the latest PC to have the above error now works...Nothing changed on it, just moved physical location. Yet other PCs in the same office have been, and are still fine.

 

Thank you

 

GreyFox

[GreyFox]

Hello again MrWoberts,

 

Unfortunately none of that appears to have made a difference our end Thank you for the suggestions anyway, every little helps.

I'll wait to see if anyone else has any ideas.

 

Thank you

 

Grey Fox

[Steve21]

Are you using Autodiscover to get to the pages? We found we have the same thing sometimes, when it decides to autodiscover to HTTPS it breaks as there is no HTTPS and redirects to HTTP, and then other times it goes to HTTP and works fine.

 

As you said that TLS/SSL error says to enable stuff, yet it's all enabled/disabled as requested and it doesn't make a difference between two machines with the same setup.

 

Still never got to the bottom of it, but seems so infrequent I've kinda not tried much if I'm honest. Only started noticing it happen since Smoothwall was in place though, so not sure if it is linked to anything with that regards. (Could just be luck that I noticed it then though )

 

Steve

[GreyFox]

Hi Steve21,

 

Thank you for your reply. I can't speak for other people, but the issue has just started occurring on my PC. I'm not using Autodiscover.

It certainly seems to be a network issue, rather than computer configuration one though. We've not got Smoothwall, but that is due to be installed next week. So we'll have to see if that changes things for us.

 

Thanks

 

Grey Fox

[Steve21]

And by any chance at the same time do you get a schannel error 36888 in event logs? (Might show as fatal 10 too)

 

Steve

[GreyFox]

I can't find any of those errors in my event logs, sorry.

 

Grey Fox

[GreyFox]

Well, we've just found a strange work-around for this issue... Start an RDP session to the ADFS server, then try again. It then lets us on. We've tried with two PCs/users with this issue, both work. Our OnceDrives, which also wouldn't connect, now do as well...

 

My earlier comment about AutoDiscover was incorrect, we do.

 

Grey Fox

[Farwell]

Grey Fox

Did you ever find a solution to this issue? We have been getting the same problem. Have also found that RDP to the ADFS server allows connection and changing the clients ip address will also allow connection.

thanks

Farwell

[GreyFox]

Hi Farwell,

 

Kind of...we've got a new firewall. We've gone from a Dell Sonicwall solution, to Watchguard. I've not seen the TLS error since, although we've had a few other ones since swapping.

 

Thanks

 

Grey Fox