Windows – Microsft Exchange 2013 on Server 2012 OWA shows blank page

exchange-2013windows-server-2012-r2

I have a standard Server 2012 installed and installed Exchange 2013 onto it. On the RDP I can access OWA and it shows me the mailbox for the user currently logged in.

When I navigate my browser to my domain.fancy/owa from an external computer I just get a blank page in Chrome and Forbidden in IE.

If I try the ECP I get a server error. Does anybody know how to fix this problem?

Best Answer

Figured it out with various other post on the internet.

You have to disable SSL if you don't have HTTPS certificates. It tries to redirect the login to https://youserver.com and fails. That is why I got weird server errors, and forbidden.

Untick Require SSL on the Default Website and click Apply

enter image description here

^{It is best to get a SSL certificate if you running business or production.}

Related Solutions

Windows 2012 Server: Enable .NET 3.5

Never mind. It turned out that I needed a 'Windows Server 2012 R2' ISO because that's what the target server was; I was trying to a regular 'Windows Server 2012' ISO and that was throwing the 'source not found' error. I downloaded an 'eval' copy of the R2 ISO from Microsoft site, 'mounted' it on the target server and, voila, the following command ran fine and now .NET 3.5 is enabled!

Thanks!

dism /online /enable-feature /featurename:NetFx3  /all /source:d:\sources\sxs

Windows – Failed Authentication Against Windows Server 2012 R2 RADIUS Using PAP

For anybody who stumbles on this and for which this may be helpful...

It turns out the problem was in my network policy. An optional part of creating a network policy is, on the "Conditions" tab, creating a "Client Friendly Name" that matches a RADIUS client you've set up (which, along with the network policy, is also done under "Network Policy Service"). You are allowed to use wildcard characters so that a "Client Friendly Name" can be made to match several RADIUS clients.

However, it seems you can use the wildcard character "*" only at the end of the "Client Friendly Name".

As an example, assume I have two RADIUS clients set up: Dave-Desktop-Home and Dave-Laptop-Home. If in my network policy I specify a "Client Friendly Name" of "Dave-*-Home", Windows Server 2012 will create an event log saying I successfully authenticated but will actually send me a RADIUS access-reject message.

On the other hand, specifying a "Client Friendly Name" of "Dave-*" works just fine to match both RADIUS clients. Both can perform a successful RADIUS authentication.

Best Answer

Related Solutions

Windows 2012 Server: Enable .NET 3.5

Windows – Failed Authentication Against Windows Server 2012 R2 RADIUS Using PAP

Related Question