Avatar of patc7004
Flag for Australia asked on

Can't log into EAC


I have a fresh install of Exchange 2013 SP1 that I'm having an issue with.

I can't log into EAC with the domain\administrator account. It keeps saying incorrect username and password.

I'm currently installing 2012r2 VMs to replace an SBS 2003 machine but rather than continuing on with their current domain (theirdomain.local) I decided to create a whole new forest instead, theirdomain.com.au to comply with new SSL CA rules. Once I have mirrored AD and copied everything else over the old domain will go.

I suspect the issue may have something to do with the internal domain being the same name as the public domain? Maybe a DNS issue? Though pinging mail.theirdomain.com.au replies from correct internal IP as I have set DNS forwarders to do so.

I have never used the public domain as an internal domain so I'm learning as I go but I'm stuck at this problem. I have however successfully installed Exchange 2013 on server 2012 r2 before and the only things different is the domain name and I've enabled Windows Server Essentials.

Initially I couldn't open shell so I ran the trick of changing the virtual directory path which worked.

I've tried creating a new user and placed in both Organization Management and Administrators group. I've also tried recreating the ECP virtual directory and have even purchased an SSL cert for the domain. Still can't log in.

Some other troubleshooting I've tried:

- tried logging in with using these methods: administrator@theirdomain.com.au, NetBIOS\administrator, theirdomain.com.au\Users\Administrator (just for kicks!)

- Created a new user mailbox via shell (this is the account I placed into Organization Management Group). Mailbox and user is created. When I try to logon to OWA it looks successful but goes to https://mail.domain.com.au/owa/auth.owa but says Webpage cannot be found "This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage". When I try to access EAC with this account it says incorrect username and password.

- Tried disabling and enabling the mailbox for the administrator. Did nothing.

I hope someone can help.

If you need more information please do ask.

Thank you in advance

Avatar of undefined
Last Comment

8/22/2022 - Mon
Kanti Prasad


heck if the user is  is  a member of the "Organization Management" role group
Get-RoleGroupMember "Organization Management"

And try append your url with      ?ExchClientVer=15

Or look at the below steps to see if it will help


Thanks Kanti

I have also tried the ?ExchClientVer=15 method but does the same thing.

Administrator and the account I created are both in Organization Management group.

I have already run the steps in the link you provided but I ran it again just in case it may trigger something new but nothing. Still the same issue.

I'm thinking this problem is related to permissions. I just need to be pointed in the right direction.
Kanti Prasad

Your help has saved me hundreds of hours of internet surfing.
Simon Butler (Sembee)

First - Exchange 2013 is very old.
A new installation should be either CU8 or CU9. The cumulative updates are the complete product, so you can just download and run the setup.exe to install Exchange. I would start by bringing the server up to date.

The domain shouldn't matter. You should be able to browse to https://localhost/ecp on the server, ignore the SSL error and be able to login with domain\username - using the account that was used to install Exchange.

Do you get a popup box for authentication or the forms page?


Hi Kanti

Thanks for finding that post though his solution was exactly that link you provided me in your first comment, which again I tried just a few minutes ago. Still getting the same thing.

Instead what I will do is rebuild the entire server again, bring it all up to date as Simon suggested, and I'll come back to this post.

Thank you for all your help so far guys.
Kanti Prasad

Hi Pat

Yes sometimes re-boots and re-install will be easier than trouble shooting...
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

I didn't have time to troubleshoot any further so went with my plan B.