Exchange user cannot log in to EAC or OWA

dss ds 531 Reputation points
2022-06-05T07:26:16.713+00:00

I am experiencing issues with logging on to EAC and OWA as users created

this is kinda wired one..

Under VM if I install Exchange on the same as AD/DNS (I know, not recommended, but its seems to be ok as a test environment), and I add user mailboxes from EAC, I can login in no problem

Trying to increase performance, I later decided to install AD/DNS on one VM, leaving Exchange 2013 for a seperate VM..

Both are running same Windows server 2008 R2, AD/DNS has 2 Gig, while Exchange 2013 has 8Gig

When I attempt to login to OWA/EAC via user, I get a loop (basically the same symptom as incorrect credentials, except there is no error. displayed"

How is this even possible when the only difference between the 1st and later methods is just DNS pointing rather than 127.0.0.1 ?

There is something a miss. and I do not think its just due to exchange being on a seperate VM that's causing this.

Any ideas ?

It seems to only affect Users created in EAC/OWA, as Administrator can access no problem

Tried this on Server (AD/DNS) as well as Exchange VM and same issue.. Only Admin can log in..

As I said, strange how this only happens when Exchange is on seperate VM..... so something strange is happening.

Exchange | Exchange Server | Management
{count} votes

2 answers

Sort by: Most helpful
  1. T. Kujala 8,766 Reputation points
    2022-06-05T17:15:52.92+00:00

    Hi @dss ds ,

    You could check the username format, depending on the settings it could be just USERNAME, DOMAIN\username, or username@keyman .com.

    0 comments No comments

  2. dss ds 531 Reputation points
    2022-06-06T01:22:37.22+00:00

    Its forms-based Domain/Username. Although this wouldn't explain why it only affects created users only as this is a global setting..

    for, example Admiistrator can log into owa and ecp just fine

    Checking under User on ECP, Outlook web access is "enabled", so still unsure why at this point.

    I can log into Windows as User in AD just fine as well, so its exchange specific..

    I'll keep this around, but at this point i'm liable to just set up another VM with it all on, so i can get on with what i need to do, while i sort this in addition. only because i would wanna know the reason.

    Tried Chrome, Firefox and even IE

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.