?
Solved

OWA authentication issues with Exchange 2003

Posted on 2006-05-31
3
Medium Priority
?
314 Views
Last Modified: 2010-03-06
We just installed a new Exchange server in our site. We're running Windows 2003 Server and Exchange 2003. I moved my mailbox as a test and everything is working fine.

The issue I have is with OWA. When I go to mail.company_name.com to access my web based email, the authentication box for the old server somes up. After I authenticate, the authentication box for the new server comes up. I login and I'm able to access my web based email.

When I logout from OWA, the authentication box comes up again (for the new server). In order to logout from OWA I have to authenticate again.

Is there anyway to clean up this process?

John

0
Comment
Question by:rocklin_rebel
  • 2
3 Comments
 

Author Comment

by:rocklin_rebel
ID: 16802098
I fixed one of the problems. I'm able to log out of OWA without being prompted for authentication. I unchecked the box to enable forms based authentication in Exchange System Manager under Protocols, HTTP, properties for Exchange Virtual Server.

Still have one more problem. It would be nice if mail.company_name.com would automatically redirect me to the new server immediately for OWA.
Thanks,
John
0
 
LVL 104

Accepted Solution

by:
Sembee earned 2000 total points
ID: 16803555
If these are two separate servers without a frontend server then that would appear to be Exchange working correctly. By hitting the first Exchange server you need to authenticate. Exchange basically says "not here, try there" and then the second server asks you to authenticate. The second server doesn't know anything about your first authentication attempt.

The usual reason for authentication being required on log off is that anonymous authentication is disabled on the /exchweb virtual directory in IIS Manager. Enable it again.
FBA only works if you are using SSL.

if you are going to run two servers then you have two choices...

1. Expose both servers to the internet and tell the users which one to hit.
2. Use a frontend server, which sorts out where your email needs to be pulled from automatically.

Simon.
0
 

Author Comment

by:rocklin_rebel
ID: 16808540
Again, thank you for your precise answer. We're probably going with solution #1.

John
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Question has a verified solution.

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

Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
In this video we show how to create an email address policy 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…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses
Course of the Month15 days, 21 hours left to enroll

850 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