Testing new Exchange 2003 URL prior to Exchange 2010 upgrade
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?
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?
ASKER
"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?
"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?
ASKER
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.
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.
check the Exchange Virtual Directory that the default domain is blank, then try again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It was the load balancer. They didn't have port 443 open, I think.
How are you entering the username? Try DOMAIN\username as well as USERNAME and USERNAME@domain.local