Solved

Activesync issue on Exchange 2013

Posted on 2013-06-29
7
558 Views
Last Modified: 2013-07-01
We are migrating from Exchange 2007 to Exchange 2013 and are having a problem with the smartphones and tablets syncing e-mail.  We have moved the users' mailboxes over to the E2013 server.  We have moved the pointers in the firewall to point to the new server.  OWA is working fine over port 443.  There are now certificate errors.  The activesyncvirtualdirectory is pointing to mail.contoso.local and the DNS entry for mail.contoso.local is pointed to the E2013 server.

Smartphones with existing accounts are not able to send or receive mail.

When we try to setup a new account on a smartphone the account sets up fine but then there is an error when it tries to sync messages.

Thanks for any ideas.

Bill
0
Comment
Question by:labdunn
[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
7 Comments
 
LVL 34

Expert Comment

by:Shreedhar Ette
ID: 39287698
Hello,

Have you installed proper certificate on Exchange 2013?

The Public url should be mail.contoso.com not mail.contoso.local.
0
 
LVL 1

Author Comment

by:labdunn
ID: 39288343
Yes.  We've installed a SAN certificate with both mail.contoso.com and mail.contoso.local.
0
 
LVL 34

Expert Comment

by:Shreedhar Ette
ID: 39288815
Pleased run Exchange ActiveSync at https://www.testexchangeconnectivity.com/ and post output here.
0
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 
LVL 1

Author Comment

by:labdunn
ID: 39288903
The Microsoft Connectivity Analyzer is testing Exchange ActiveSync.  
  The Exchange ActiveSync test failed.
 
 Test Steps
 
 Attempting the Autodiscover and Exchange ActiveSync test (if requested).
  Testing of Autodiscover for Exchange ActiveSync failed.
 
 Test Steps
0
 
LVL 34

Accepted Solution

by:
Shreedhar Ette earned 500 total points
ID: 39289123
Please run test without autodiscover and post the error.
0
 
LVL 1

Author Comment

by:labdunn
ID: 39289671
That might have been the enabler to fix the issue.  The results of that scan gave me some steps to take and that seems to have fixed the problem.  Its early here so it may be a few more hours before I get feedback from the effected users. I post an update when I hear.

Thanks

Bill
0
 
LVL 1

Author Closing Comment

by:labdunn
ID: 39291002
The remote connectivity analyzer identified the problem and gave me the steps to fix the obscure little SOB.

Thanks

Bill
0

Featured Post

Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

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
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data‚Ķ
This video discusses moving either the default database or any database to a new volume.

729 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