Exchange 2013 issue / OWA time-out and WiFi/Cell problem.

Question

Hi everybody,
I'm having some issues with an Exchange 2013 server.
When some users try to logon to the OWA page it keeps loading the page and ends with a time-out.
This only applies to 6 or 7 users, other users can login and open the page.
I tried to replace the signed certificate to solve this problem, and did a online analyzer check, most tests come out good.
I can't seem to find the source of this problem.
There are also multiple users that are having trouble to receive e-mail through the wifi on phones and tablets at home but when they switch to 3g it works fine.
You might need more information, just ask.. i don't know where to search anymore.
I tried inheritance on the AD, disabled SSL in the IIS, restarted the server, replaced the signed cert. etc.
Update:
I set the selfsigned cert in the IIS default web page,, to check if it responds to the certificate and it does, so the issue doesn't come from the certificate.
This issue probably came up after CU1, and i've read something about healthboxes..
I'm going to install CU6 and hope for good result.
Kind regards,
Tim

Answer 1

I've installed CU6, only one of the six users have gained access to OWA or ECP.
Al the other users won't get a logon screen, just a blank page.
So there is no option to insert a username or password to login, the page keeps loading and ends with "the page cannot be displayed"
But on my working spot i can open owa or ecp without any issues.
I've recreated the virtual directory for ECP and OWA with powershell, and checked the certificate.
I checked if the same certificate was connected to the back-end port 444, and this is set correct.
I even reconnected the cert on 444 with the following.
Open the Command Prompt
Run-
netsh http show sslcert
This will show the certs, copy and paste this information into notepad.  Under     IP:port   : 127.0.0.1:443, note the certificate hash and application ID.
Run this command-  (Yes, I know there is no :444 listed in the output from the earlier command.)
netsh http delete sslcert ipport=0.0.0.0:444
Run this command.  Replace certhas with the certificate hash and appid with the application ID you saved in notepad.
netsh http add sslcert ipport=0.0.0.0:444 certhash=123123123123123 appid="{123123123123-1231231235}"
I used powershell to set the login authentication,
et-Owavirtualdirectory -identity "YourMailBoxServerName\owa (Exchange Back End)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
set-Owavirtualdirectory -identity "YourCASserverName\owa (Default Web Site)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
and iisreset /noforce
I unchecked the "require SSL" on the default website and left it enabled on the owa and ecp etc.
Checked if HTTP over Proxy is installed, but this one is need to install exchange 2013.
I've checked all ECP/OWA directories in in the IIS, the directories point to the Exchange V15 folders, this should be correct.
Something is really broken, i really can use the help..
I'm going to try to install Exchange 2013 SP1, but i don't know if this one is needed when CU6 has been installed.
The strange thing is, it seem to be location based, not user based.
I can login perfectly, but when i try this at one of the employees, it ends up blank.
When i try to connect on a location dat does not work, at the exact time i press the enter-key to open the page, the eventviewer logs the following:
Event 4634 - An account was logged off.
For the issue on the smartphones and tablets, everything worked fine a few months ago, and happens to users on different ISP connections.
I already checked the inheritance settings on the users in the AD.
Kind regards,
Tim