Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7518
  • Last Modified:

Exchange 2013 - cant connect Outlook to Exchange

Hi,

we have installed an Exchange 2013 that is co-existing with Exchange 2010. I've created an test-user that is placed on Exchange 2013 and I can connect with the user on owa intern. But when I try to connect this user to Outlook 2013 manually, it fails with this message:

Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.

Open in new window


I've checked that the SRV autodiscover dns record i pointing to the Exchange 2013 server and it looks fine.

When I type https://SERVERNAME/autodiscover/autodiscover.xml into my IE, it prompts me for login and when I type in my credentials, it shows me this:

<?xml version="1.0" encoding="UTF-8"?>
-<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">-<Response>-<Error Id="746590105" Time="08:28:27.1771287"><ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>

Open in new window


Which should be right. I haven't opened up for owa external yet.

What am I missing here? I just want it to connect to our Outlook.
0
Sum Wum
Asked:
Sum Wum
1 Solution
 
EddyvanOpdorpCommented:
The error number 600 in a browser is correct.
A browser cannot handle the autdiscover. If it shows that message (error code 600) it should work.

What is the result of this test ?
https://www.testexchangeconnectivity.com/
0
 
Sum WumAuthor Commented:
It fails. But isn't that because I haven't setup any external DNS? I want to wait with that until everything works intern.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
VirastaRUC Tech Consultant Commented:
0
 
EddyvanOpdorpCommented:
My link indeed fails if you have no external DNS setup...
0
 
Simon Butler (Sembee)ConsultantCommented:
You don't need an internal DNS record for Autodiscover unless the clients are on the LAN who are NOT members of the domain.
Autodiscover must work though - so you need to verify that to begin with.

You can do that with Outlook:
http://semb.ee/adt

Simon.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now