Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

Exchange Remote Connectivity Analyzer interrmittent failures in 2003/2010 coexistence

Got a strange one here. I have an Exchange 2003/2010 environment in coexistence.

I moved a user from Ex2003 to Ex2010. That user that can connect to Outlook Web App, Outlook and ActiveSync no problems.

I have other users on Ex2003. They can connect through the Outlook Web App redirection to the 2003 OWA backend just fine.

However, when I try to connect to those 2003 users with ActiveSync it fails. I tried the ActiveSync test on EXRCA.COM and I get the following end result.

"The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response."
 Additional Details
 
The Response element in the payload was null.
 <?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006" />
HTTP Response Headers:
Persistent-Auth: true
Content-Length: 382
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Sat, 20 Sep 2014 00:23:22 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
Elapsed Time: 816 ms.  


Now if I retest the 2010 user, they pass the ActiveSync EXRCA test no problems. They are also working on ActiveSync as we speak so passing the test as that user is to be expected. I am testing both users from the same device as well.

Nothing odd with the users AD objects. Such as security inheritance. ActiveSync is enabled on the 2003 accounts.

If I go to the autodiscover URL as the 2003 user I get the expected result and can see the XML file.

So, not sure if this is truly an autodiscover issue.
0
Gareth Gudger
Asked:
Gareth Gudger
  • 6
1 Solution
 
Gareth GudgerAuthor Commented:
Looks like the same exact issue was reported here as well. Just that they ended up moving all the users quickly. Basically didn't deal with fixing it.
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27570776.html
0
 
Gareth GudgerAuthor Commented:
0
 
Gareth GudgerAuthor Commented:
Fixes here didn't help either.
http://support.microsoft.com/kb/817379
0
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.

 
Gareth GudgerAuthor Commented:
Hmm.... to muddy the waters, seems like SharePoint may have been installed on here at one point.

Oddly, the Default Web Site gets a page not displayed internally. But externally things like OWA works fine. Same issue with internal IP as well. So, not a DNS issue. No firewalls in play on the server itself.
0
 
Gareth GudgerAuthor Commented:
Drawing dead here. Verified I have all the right hotfixes, permissions and what not on the 2003 side. IWA and Basic enabled in ESM on 2003. Verified they show up in IIS as well. This is a single server, so no front end/back end, so tried creating the extra VDir with SSL disabled. No help their either.

Despite EXRCA.COM saying it is autodiscover, my 2003 users can access the autodiscover XML file just fine. Plus, if I check the IIS logs on the 2003 box I see ActiveSync redirects coming from the 2010 servers internal IP. So, I believe the 2010 server is fine. Especially with the 2010 ActiveSync users working just fine.
0
 
Gareth GudgerAuthor Commented:
I ended up disabling Form Based Authentication on the 2003 server and now ActiveSync works for both 2003 and 2010. It breaks OWA redirection, but I will just have my users go directly to the Legacy URL. Phones are far more important than OWA access.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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