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, 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 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:, NetBIOS\administrator,\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 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
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Kanti PrasadCommented:

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
patc7004Author Commented:
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 PrasadCommented:
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Simon Butler (Sembee)ConsultantCommented:
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?

patc7004Author Commented:
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 PrasadCommented:
Hi Pat

Yes sometimes re-boots and re-install will be easier than trouble shooting...
patc7004Author Commented:
Hi. Sorry I hadn't gotten back to this in a timely fashion, been busy with the migration.

Basically the re-install with all updates didn't resolve anything, I was still getting the same issue with authentication. I didn't have time to mess around with it after that so instead I joined the new 2012 R2 VM to the existing domain, uninstalled Exchange 2003 from the SBS and installed Exchange 2013 on the 2012 R2 vm.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
patc7004Author Commented:
I didn't have time to troubleshoot any further so went with my plan B.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.