[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Exchange 2013 OWA Issue

Posted on 2014-07-18
8
Medium Priority
?
626 Views
Last Modified: 2014-07-26
Hello Experts,

I have two Exchange servers, both setup (as far as I can tell) identically to one another, both running CAS and Mailbox. However, they are each at different locations and subnets. When I browse to OWA on MailServer1, I get prompted with the normal windows prompt for username & password and I can log in just find.
prompt1.jpg
When I browse to MailServer2, I get the OWA login prompt and am unable to login. I get the "user name or password isn't correct" message.
prompt2.jpg
The only difference I can see on each of the servers is that OWA virtual directory for MailServer1 states that it's version "Exchange 2010" and for MailServer2 it is "Exchange 2013". Could this be the issue? Please help!

Thanks.
0
Comment
Question by:nreich
  • 5
  • 3
8 Comments
 
LVL 19

Expert Comment

by:Adam Farage
ID: 40204857
Where is the mailbox located when you attempt to login, Exchange 2013 or Exchange 2013. This very well could be a proxy / redirection issue, and since the first screenshot looks like its not FBA (Basic authentication) you might have to change the Exchange 2010 OWA virtual directory from NTLM authentication to FBA.

Let us know where the users mailbox sites first, and then we can go from there.
0
 

Author Comment

by:nreich
ID: 40205051
Both Exchange servers are in a DAG and the mailboxes currently reside on MailServer1 (with a copy on MailServer2). Authentication for the Default Web Site's OWA directory is Windows Authentication and for the Back End it is Anonymous and Windows Authentication; set on both servers.
0
 
LVL 19

Expert Comment

by:Adam Farage
ID: 40205077
Can you explain this a tad bit further then, because I am not following:

The only difference I can see on each of the servers is that OWA virtual directory for MailServer1 states that it's version "Exchange 2010" and for MailServer2 it is "Exchange 2013". Could this be the issue? Please help!
0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 

Author Comment

by:nreich
ID: 40205094
I've posted this pic below to help explain further visually...
owaConfig.png
0
 
LVL 19

Expert Comment

by:Adam Farage
ID: 40206231
The first screenshot, where does that OWA virtual directory sit? Is it an Exchange 2010 server or 2013?
0
 

Author Comment

by:nreich
ID: 40208768
Both servers are running Windows 2012 with Exchange 2013 SP1 CU4. Here are the OWA paths...

MailServer1

Default Web Site: c:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa
Back End: c:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa

MailServer2

Default Web Site: c:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa
Back End: c:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa
0
 

Accepted Solution

by:
nreich earned 0 total points
ID: 40209253
After digging much more, I discovered that the directory "auth" under the virtual directory owa on MailServer2 was set to Form Authentication. I wasn't allowed to modify the setting in this section - kept getting a message "This feature has been locked and is read-only". So I copied the web.config file from my owa path of MailServer1 and performed and IIS reset. Forms Authentication is now disabled and I'm able to log into Webmail/OWA on MailServer2 just fine.
authperm.png
0
 

Author Closing Comment

by:nreich
ID: 40221112
My own solution.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
Steps to fix error: “Couldn’t mount the database that you specified. Specified database: HU-DB; Error code: An Active Manager operation fail”
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
Suggested Courses
Course of the Month20 days, 13 hours left to enroll

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question