Solved

Testing new Exchange 2003 URL prior to Exchange 2010 upgrade

Posted on 2011-03-24
7
552 Views
Last Modified: 2012-08-13
I am trying to test the redirect to the legacy servers prior to cutting to Exchange 2010.  I have put in a DNS entry for legacy.domain.com to point to the original server which still has the name webmail.domain.com.

OWA pops up for both when I try them in my browser.  However, I can't logon to the new URL, it won't allow me to authenticate.  Any thoughts?
0
Comment
Question by:liquid101
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
7 Comments
 
LVL 74

Expert Comment

by:Glen Knight
ID: 35208799
the authentication should be identical, it's the same server.

How are you entering the username? Try DOMAIN\username as well as USERNAME and USERNAME@domain.local
0
 
LVL 1

Author Comment

by:liquid101
ID: 35208870
"webmail"'s login works without the domain... it's just USERNAME

"mail" doesn't respond to either of the login options above.

It just acts like I'm logging in with a bad username or password with the new url.  Do I have to add the URL to something in IIS or Exchange 2003?

0
 
LVL 1

Author Comment

by:liquid101
ID: 35208875
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 8

Expert Comment

by:GundogTrainer
ID: 35208890
Can you confirm this is external facing or are you doing in on the internal network.

If your doing it internaly and expecting the integrated authentication to work then the URL needs to be in the intranet or Trusted sites zone in internet explorer to automaticaly pass your credentials - However if this is externaly then ignore this as it shouldnt care as long as the domain\username and password are correct.
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 35208906
check the Exchange Virtual Directory that the default domain is blank, then try again.
0
 
LVL 1

Accepted Solution

by:
liquid101 earned 0 total points
ID: 35208960
It's only internal at the moment.  I added it to "trusted sites" to no avail.  Same issue.  However, the "mail" name is a new DNS entry pointing to a VIP on our load balancer.  Could the LB be messing up the logon somehow with the cookies?
0
 
LVL 1

Author Closing Comment

by:liquid101
ID: 35239111
It was the load balancer.  They didn't have port 443 open, I think.
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

This article explains how to install and use the NTBackup utility that comes with Windows Server.
In-place Upgrading Dirsync to Azure AD Connect
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

751 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