Link to home
Start Free TrialLog in
Avatar of Laszlo Denes
Laszlo DenesFlag for Canada

asked on

URGENT! New Exchange 2013 (migrate from 2007) and BES 12 no longer works for users email send/receive Activesync error port 443

We migrated all of our users from Exchange 2007 to Exchange 2013 (two servers load balanced Microsoft failover with 1 DAG) and it went well. No issues for users using Outlook 2013 and OWA. However, as soon as we moved our Blackberry users (all Z30 Blackberry 10 version to the new Exchange 2013 and repointed the BES server to the new Exchange 2013 (new mail profile, but the same issues if we just repoint the old profile to the new IP) their Blackberry devices (connected to a single Blackberry Server Version 12.5.1) started acting odd and did not receive or send email anymore from their Z30 devices. We had to generate and export a BES certificate to the new Exchange 2013 and vice versa for mail to flow. However, then we noticed that users who had their Blackberry off during the migration could not get email. Only users who were ON and connected (to Blackberry) throughout the entire migration process could continue to send/receive email from their Z30’s. Anyone who restarted their Z30 or changed their network password (the one specified on the Z30) or if we try to deploy (using the standard process via the BES -> create account, send verification code, etc.) a new Z30 we run into the same no email issue. During the deployment the entire process from the Bes to the Z30 works and a workspace is created (visible and can be used) without issues, just like before, but when you get to the last item (when you enter the network password for the user so it can authenticate and download emails, calendar, etc.) it fails with the error shown hereafter. The 2007 Exchange did not have these issues and I can only speculate that it is an ActiveSync related authentication issue in that something is preventing the password from being transmitted successfully. Any users who restarts their Z30 also drops off and no longer gets email. We have tried with ISP (Rogers) connection, internal Wi-Fi, new users, existing users but to no avail. Some users continue to be able send/receive
“The server for account activesync : work (, port: 443) can't be reached. The settings might be incorrect or the server could temporarily offline. Check your settings and try again.”
Please help as all BB users are Executive team members!!!
Avatar of jmac44
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Laszlo Denes


Tried that already with several accounts sadly no difference...
On what server did yo install Ex.2013?
Try checking TLS settings as suggested here

also still want to know Server type you installed on.
Exchange 2013 is installed (cluster with failover) on two 2012 R2 virtualized (VM 6) servers!
Will try suggestion!
I've got bad news bud. According to this link
2012 R2 is an unsupported OS for Exchange 2013.

OK, I called Microsoft and found I had much much bigger issues. I installed Exchange 2013 on Server 2012 R2. This is an unsupported operating system. I will need to do a reinstall of exchange and try again.
LMAO thanks but I find that hard to believe as we are working with an Exchange expert from a Microsoft Gold partner Vendor... not trying to be cheeky... but
also comment was made in 2014... so 3 years later now...
Lost in Windows  Jan 30, 2014 at 7:49 AM  

Computer Rescue is an IT service provider.

OK, I called Microsoft and found I had much much bigger issues. I installed Exchange 2013 on Server 2012 R2. This is an unsupported operating system. I will need to do a reinstall of exchange and try again. (groan).
No that's cool. This link from MS
confirms it is w/SP1.

Should looked harder before I posted that. My fault.
the tls suggestion also had no effect
Have you tried enabling "windows authentication" in IIS under ActiveSync? I read where iPhones where having connection issues and that resolved their problem.
that looks interesting and although we do not have iphones will try... thanks...
Did you bind port 443 in IIS?
not the cause... interestingly enough all other uses work now except for two...
Try resetting there password in active directory. I know it's a pain to have the user come to you and have them reset it at a terminal on the server but I have had success in other instances where this worked. Might be worth a shot.