Exchange 2013 with Exchange 2010 - outlook 2010 not setting up

I've installed Exchange 2013 with Exchange 2010.  

The install worked great, the 2013 server is up, and OWA is working great.

But Outlook 2010 will not auto connect to it.  Either when I setup a new profile, or after I move a mailbox on an existing profile.

If I go in an manually setup the HTTP settings, outlook will connect.

Any ideas on why outlook will not connect?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Does your autodiscover record in DNS point to the 2013 CAS?
erikwhitewayAuthor Commented:
Autodiscover Cname to the 2013 host name for internal DNS.

Both servers have an external name of - so I just changed the internal DNS to point mail. at the new server.
erikwhitewayAuthor Commented:
Moving mail. to the new 2013 server seemed to make outlook connect.  But it's putting up a login prompt to users.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Simon Butler (Sembee)ConsultantCommented:
Autodiscover doesn't work in the same way internally.
What do you get from this command?

get-clientaccessserver | select identity, AutodiscoverServiceInternalURI

If you are migrating to Exchange 2013 then I would probably have the same URL on both servers, pointing to the Exchange 2013 URL, or a host name that resolves there which is also on the SSL certificate.

Authentication prompts can be an indication of an SSL certificate issue. Do you have a trusted SSL certificate on the Exchange 2013 server?


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
erikwhitewayAuthor Commented:
Each server has it's self as the autodiscover (internal full dns name).

Another issue:


On the old server - only shows the old server - does not list the new one.

Same with the autodiscover list.
erikwhitewayAuthor Commented:
Also have issue that the test moved mailboxes can't send mail to boxes on the old server:

Diagnostic information for administrators:
Generating server:
Receiving server: (
Remote Server at ( returned '400 4.4.7 Message delayed'
9/13/2013 12:09:01 AM - Remote Server at ( returned '451 4.4.0 Primary target IP address responded with: "451 5.7.3 Cannot achieve Exchange Server authentication." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was'
erikwhitewayAuthor Commented:
I've found the command to reset Autodiscover to  And in DNS that points to the new 2013 server.

I also made a receive connector in 2010 just for the 2013 server.

Things seem to be working better now.
erikwhitewayAuthor Commented:
needed setup on both servers
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.