?
Solved

Cannot open your default e-mail folders. Microsoft Exchange is not available.

Posted on 2014-04-30
8
Medium Priority
?
3,661 Views
Last Modified: 2014-05-08
Hi guys
Before I pull my hair out, let’s see what the experts can help with.

I am a complete Exchange newbie. Previously worked with SBS where everything was easy and straight forward. The Company has now, rightly so, decided to upgrade MS Server 2012 with Exchange 2013, some VMs clusters and all things new to me.

I have built a test server to learn the new environment before the new equipment arrives and I have to install and implement it.

I have installed Server 2012 evaluation version with AD, DNS, DHCP and added 1 user other than the Administrator.
I have then installed Exchange server 2013 and setup – send connector, accepted domains, default address policy.

The created user is able to access mail via OWA and send emails to outside recipients and to the administrator but when I generate an account in Outlook I get the following error:
“Cannot open your default e-mail folders. Microsoft Exchange is not available. Ether there are network problems or the exchange Computer is down for maintenance”

I have spent countless hours trying different solutions found on the net, each time restoring the server from backup when the solution has not worked. Now I am asking for your assistance.

We have a lot of public holidays in South Africa at the moment so it might take me a few days to test and get back to you guys on success.
0
Comment
Question by:Deon-YCG
[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
  • 3
8 Comments
 
LVL 36

Expert Comment

by:Kimputer
ID: 40031736
I suspect some DNS problems ? (Because OWA doesn't depend on DNS that much).
When you add the account to Outlook, and you press Check Username, does it work (i.e. the username changes to full name, and underneath will be the line)?
0
 
LVL 1

Author Comment

by:Deon-YCG
ID: 40031751
Yes, it populates with the server and users full names.
servername.domain.local
user@domain.co.za
0
 
LVL 31

Accepted Solution

by:
Gareth Gudger earned 2000 total points
ID: 40033570
Are you using a self signed certificate for Exchange? If so, does your test client OS trust this certificate? Any certificate errors when using OWA?
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
LVL 1

Author Comment

by:Deon-YCG
ID: 40041491
I have created a self signed certificate without changing anything from the defaults.
When opening OWA I get the following error:

Error in IE when accessing OWA.

I have viewed and installed the certificate on the laptop I am using for testing.
Another note that might change thinking - the laptop I am testing with is registered on a different domain.
0
 
LVL 1

Author Comment

by:Deon-YCG
ID: 40041505
Some more searching.
I have  I have assigned the certificate to the “Trusted Root Certification Authorities” area.
I can now open OWA without any Security Alert.
Still get the same response from Outlook though.
0
 
LVL 31

Assisted Solution

by:Gareth Gudger
Gareth Gudger earned 2000 total points
ID: 40041864
Yes, if it is in a different domain and it is a self signed cert you definitely would have gotten that error. Glad you got the certificate error resolved.

With regard to Outlook, if it is in a different domain, it likely can't contact the Exchange server via DNS.

Can you ping the Exchange server from the computer running Outlook by host name or fully qualified domain name? Does the correct IP come back?

The easiest solution for testing would be to put the client PC in the same domain as the Exchange server.

Otherwise you would be to configure Autodiscover and split-brain DNS.

This should allow your Outlook client to connect from anywhere.
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/

This article is for 2010, but the same namespace principles apply to Exchange 2013. See section 5 towards the bottom on configuring split-brain DNS.
http://supertekboy.com/2014/04/07/migrating-exchange-2003-2010-part-iii/
0
 
LVL 1

Author Closing Comment

by:Deon-YCG
ID: 40049803
Thanks
After putting my laptop on the new domain I was able to connect outlook to Exchange.
Now on to the next learning curve.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40050226
Awesome!
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

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

In-place Upgrading Dirsync to Azure AD Connect
This article describes how to import an Outlook PST file to Office 365 using a third party product to avoid Microsoft's Azure command line tool, saving you time.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses
Course of the Month12 days, 22 hours left to enroll

777 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