Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Outlook clients can't access Exchange 2013 server

Posted on 2014-04-25
4
Medium Priority
?
602 Views
Last Modified: 2014-06-03
We are migrating from an Exchange 2007 environment to Exchange 2013 and have a huge problem.  Once a user's mailbox is moved over to the 2013 server they can no longer reach their mailbox.  OWA works fine, its just Outlook.  

I can manually create a profile for the user and it validates the servername and user but the mailbox won't open.  

The message the user sees is something like Outlook is unable to open your default folders.

There is just a single Exchange 2013 server with all the roles installed on that machine.  All the Autostart Exchange services are running.  The RPC over HTTP Proxy service was not installed by the Exchange installation but I have since installed that feature.

Thanks for your help.

Bill
0
Comment
Question by:labdunn
  • 2
4 Comments
 
LVL 24

Expert Comment

by:DMTechGrooup
ID: 40022888
Did you set up a new exchange and then move the the mailboxes or upgrade an existing machine?

If you set up a new machine and moved the mailboxes did you leave the original machine on?  

The way outlook knows to move is it try to connect to the original machine and then is updated to the new machine.

Also check this recent KB article.

http://support.microsoft.com/kb/2934750
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40023072
If you entering the server configuration manually then things are not working correctly.
You must use Autodiscover. The server name will change to a GUID. If that doesn't, then the move didn't go through correctly or the domain hasn't replicated the change.

Just to be clear here: AUTODISCOVER IS NOT OPTIONAL.

The only method of connecting it Outlook Anywhere, therefore you need to ensure that the configuration of that feature is correct. Do you have a trusted SSL certificate? Have you configured the URLs correctly?

Simon.
0
 
LVL 1

Accepted Solution

by:
labdunn earned 0 total points
ID: 40099531
Problem was an IIS setting on the new server.  Had to call MS for a resolution
0
 
LVL 1

Author Closing Comment

by:labdunn
ID: 40108049
Required call to MS
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

Question has a verified solution.

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

Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
Steps to fix “Unable to mount database. (hr=0x80004005, ec=1108)”.
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
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

782 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