Solved

Internal Outlook / OWA / ECP not working post Exchange migration

Posted on 2016-10-09
6
17 Views
Last Modified: 2016-10-15
Hi all,

I've hit a minor road block with my exchange migration.  Currently, mail flow is 100%, and external OWA/AS devices all work fine.  Internally, OWA errors to 503 on https://mail.domain.com/owa and https://mail.domain.com/ecp (even when you enter in the ?v=15...).

When trying to configure a fresh outlook profile in testing, I get the error of 'The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action.'   The dialog then pops up with the GUID@domain.com, with the mailbox referenced of =SMTP:currentuser@domain.com.  I also generate an error of 'The action cannot be completed.  The Connection to microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action.'

Migration was from Ex2010 to Ex2013.  All is fully patched.  Ex2010 is complete uninstalled.  All the virtual directories have entries, all names resolve internally with NSLOOKUP.  I don't think split DNS is configured, but resolving these URL's and services was working with the prior exchange set up.

SRV, PTR etc. records exist for autodiscover, mail.domain.com records exist.

One odd stumbling block that I hit during the migration:  When I tried to apply the SAN cert to Ex2013 from Godaddy using the import method (not the generate CSR -> upload to godaddy ->download -> import method) from the ellipses - it would say it successfully imported...and not appear in the exchange page of available certs.  If you looked at the locally installed certs on MMC, it listed it with the correct thumbprint.  I couldn't get that to work at all, so I resorted to exporting the cert from Ex2010 and importing the CRX/PFX (sp?) to EX2013.  That worked successfully (but doesn't listed the most current names on the SAN, which I don't understand why that is).


Any further testing and ideas?
0
Comment
Question by:browningit
  • 4
  • 2
6 Comments
 
LVL 6

Expert Comment

by:No More
ID: 41836306
Have a look on your IIS bindings and recheck cert. also check MX records in DNS, is your local OWA working ? Was this migration done on same server ?
0
 
LVL 2

Author Comment

by:browningit
ID: 41836314
Note sure what bindings on IIS you would want to see/hear about.

Checking the cert - this particular cert gets used at another service, so I am hesitant to rekey and try it again, however, will do so if urged.  I certainly thing that is a sticking point, since I had an issue with the deployment at that step.

MX records are all good in DNS, mail comes in and out just fine.

Local OWA?  On the server I can load up the ECP link no issue.  I can't load OWA or ECP on client computers, or configure exchange, as noted in original post.  =/  Thanks David!
0
 
LVL 6

Assisted Solution

by:No More
No More earned 500 total points
ID: 41836322
1
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 2

Author Comment

by:browningit
ID: 41836323
Internal and external urls are configured.  Used the exchangeserverpro scripts, manually verified them all.  

As for the https redirect, that will be done, but wouldn't hinder what I'm working on so far (applying it now, because I might as well).  Great links either way, thank you.
0
 
LVL 2

Accepted Solution

by:
browningit earned 0 total points
ID: 41836691
Woke up this morning with a fresh mind at the task.

I ran another nslookup to see if maybe some reason it took DNS all night to propagate across servers/pc's.  Same result, found the new server @...122

Then I had the bright idea to PING the mail.domain.com...which was looking to the OLD server @...13

*sigh*

Guess who the IT guy is and edits his hosts file all the time when testing non production servers etc?  I completely forgot that I may have done that and chased my tail for a day instead of trying another PC, trying a ping, or checking my hosts file.

internal owa resolves fine since removing the record.  Outlook immediately resolves all information.

Giving 1/2 points to David as his links are clear, concise and well organized.
0
 
LVL 2

Author Closing Comment

by:browningit
ID: 41844871
Chased my own hosts file edit mistake from weeks/months prior.  Always check 'the IT pc' in your org (or another user computer) before you chase your own tail!
0

Featured Post

Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Easy CSR creation in Exchange 2007,2010 and 2013
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…
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…

758 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

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now