Solved

Trouble with Outlook Anywhere and Exchange 2007

Posted on 2009-04-07
11
480 Views
Last Modified: 2012-05-06
I'm having issues connecting to our exchange server. The client I'm connecting is not a domain member.
I created a public dns entry autodiscover.domain.com. I tested this by going to https://autodiscover.domain.com/autodiscover/autodiscover.xml which displayed a login prompt and after login gave my an xml file with an ErrorCode: 600 Message: Invalid Request. I think this is the right output for directly requesting the xml file.
Any idea what this error could be? Or where I can find a log file to give me more details other than server unavailable?
OAW-1.jpg
OAW-2.jpg
OAW-3.jpg
OAW-4.jpg
0
Comment
Question by:DuNuNuBatman
  • 7
  • 4
11 Comments
 
LVL 65

Expert Comment

by:Mestha
ID: 24089879
To me, that looks like autodiscover is working, but it is giving back the wrong information. That "=SMTP:" is certainly wrong.

Is this a migration off Exchange 2003 by any chance?

Simon.
0
 

Author Comment

by:DuNuNuBatman
ID: 24090572
It is. Right now all of the mailboxes except the Test User account is still on the Exchange 2003 server until I can get the 2007 server working. Once I get it working, I'll move the mailboxes over.
0
 
LVL 65

Expert Comment

by:Mestha
ID: 24092696
Have you run the best practises tool against the environment? You will find it in the toolbox on the Exchange 2007, but run it against both servers.

I am wondering if there is an issue with Recipient Policies on Exchange 2003 as they are interpreted by Exchange 2007. The best practises tool should flag if there is an issue there.

Simon.
0
 

Author Comment

by:DuNuNuBatman
ID: 24092810
I ran the tool and did get issues that I hadn't before.

Unknown schema extension version: Active Directory Forest The Exchange schema extensions are from an unknown version. Schema version detected is 11116.

Unrecognized Exchange signatureDomain: DOMAIN Active Directory domain 'DOMAIN' has an unrecognized Exchange signature. Current DomainPrep version: 11221.

I'm going through the help links they provided to fix these issues.
0
 

Author Comment

by:DuNuNuBatman
ID: 24102665
I don't get the issues running the tool that I had before. I decided to try syncing my phone with the new server and it worked. So OWA works as well as ActiveSync for the phone. The only thing I can't get working is Outlook 2007. Is there a way to get more verbose logging information for the Add New E-mail Account wizard? The message they are giving me is not helpful at all.
0
Do email signature updates give you a headache?

Constantly trying to correctly format email signatures? Spending all of your time at every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

 
LVL 65

Accepted Solution

by:
Mestha earned 500 total points
ID: 24109416
If this is for external clients then run it through the test on Microsoft's test site:
https://testexchangeconnectivity.com/

Simon.
0
 

Author Comment

by:DuNuNuBatman
ID: 24110616
That's a cool tool. I wish I had know of it before.
I get this error:
Testing SSL mutual authentication with RPC Proxy server
Failed to verify Mutual Authentication

The certificate common name webmail.domain.com, doesn't validate against Mutual Authentication string provided msstd:mail2.domain.com
0
 

Author Comment

by:DuNuNuBatman
ID: 24110623
Where can I find the reference to mail2.domain.com so I can change it?
0
 

Author Comment

by:DuNuNuBatman
ID: 24111453
I found that and changed it. Now I get another error. The name on the certificate does not match the name webmail.domain.com
0
 
LVL 65

Expert Comment

by:Mestha
ID: 24111847
Well you need to ensure that the DNS for that name points to the right IP address. In a browser outside your network go to https://webmail.domain.com and see what happens. If you get a certificate prompt then that is a hard failure.

Simon.
0
 

Author Comment

by:DuNuNuBatman
ID: 24112324
You are right, it is a dns issue. We're using register.com and our dns entry hasn't updated yet. It is still pointing to our old server. I think I've just about wrapped it up. Thanks for your help. That tool was a life saver!
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Utilizing an array to gracefully append to a list of EmailAddresses
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

746 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

12 Experts available now in Live!

Get 1:1 Help Now