03-09-2012 12:30 PM
Can you connect to the Exchange server using RPC over HTTP with your Outlook client from your desktop? That would ensure that the certificate is available and the protocols are working. If that doesn't work, then there are server/certificate configuration issues. If it works then it really has to boil down to the Playbook settings. Can I assume that you're testing on a local wireless connection to the LAN first to avoid any external firewall issues (at least until after it's proven to work locally, that is)?
I am on AT&T. Please edit your Personal Profile with your DEVICE TYPE, DEVICE OS and Carrier
03-09-2012 12:36 PM
ca1879 wrote:Can you connect to the Exchange server using RPC over HTTP with your Outlook client from your desktop? That would ensure that the certificate is available and the protocols are working. If that doesn't work, then there are server/certificate configuration issues. If it works then it really has to boil down to the Playbook settings. Can I assume that you're testing on a local wireless connection to the LAN first to avoid any external firewall issues (at least until after it's proven to work locally, that is)?
Outlook and EAS use two different conenction but are similar in their connections. many time people use the exchange server name instead of the published DNS name and it will fail to work.
Your playbook setting should match that of any other EAS device that you do have working unless the exchange admin is only allowing certain devices or is forcing passwords on the device.
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
BESAdmin's, please make a signature with your BES environment info. SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
04-21-2012 12:55 PM
I have exactly the same issues, any other devices I have used can connect without any problem (Android & iOS). Hope this can be solved soon.
04-25-2012 10:32 AM - edited 04-25-2012 10:35 AM
I have had the same problem.I have had Playbook starting OS 1.0 which I regulary upgraded to a newer versions.Starting verry first OS 2.0 release I was happy to find ActiveSync support and immediately tried it - well I was not surprised in how it was unstable for me. There are 2.0.x releases have happend since then but neither one fixed my problems - activesync was behaving totally wrong - unable to connect message and no emails for last few days have been normal for me already. Sometimes connection was not working (yellow sign in messages app), sometimes emails were synchronizing but not for last five days or around this value (I really cared to set sync interval to 30 days).
Eventually, accidently, I have noticed main screen of my collegue's playbook with the same OS installed - and it was curious to find that it was looking totally different. Main screen had diffrent background, there were fast shortcuts of Messages/Contacts/Browser/Calendar/App World - my Playbook had this area empty. Main menu was supporting left/right swiping - while my Playbook was alligning all shortcuts in the same vertically scrollable screen of main menu. Just for a second I imagined what else didn't take effect after F/W upgrades.
After that I instantly did a security wipe of a device - I even decided to not recover device settings I had in backup and do all settings from zero. After wipingv was done the look and feel was pretty much the same I saw on other device.
I tried to set one of 2 MS Exchange we have in enterprise with ActiveSync enabled (we have OWA enabled as well, but it is not supported by PB) - and voila! It has succefully synced all my emails including those I got a few minutes ago. I was almost happy, than I tried to set second Exchange server but it ididn't work - firstly saying "Checking for supported services and policy information" for about 10 minutes, and afterwards showing strange failure "Your Playbook is connected to a network, but the Internet service is not available. Check your network settings". I even believed this message for a second and checked is Web Browser is working - it was working... Aforementioned failure was so misinformative that I spend a very few hours to figure out that those second MS Exchange server doesn't require SSL. After I disabled SSL button in connection settings all Calendar/Emails were synchronized without problems.
I hope this will help some of PB users to avoid such a long path I have went through. If you have ever gone through F/W upgrade - just do security wipe and see what happens.
Regards, Ivan
04-25-2012 10:53 AM
Agree with the previous comment. I have found (and many I correspond with have the same experience) that it works best to do a complete de-brick when implementing updates on the Playbook. I have not had issues shortcutting the process if the only point of the update is a security plug for Flash or some such thing, but when the core programs are going to be modified, just wipe and reinstall, and you'll be much happier for it, I think.
08-05-2012 12:25 AM
09-16-2012 05:33 PM
I experience the zame problems. My company moved from exchange 2003 to 2010. Since then im not able to configure my exchange active sync. It reports that the server is not reachable. I already cleared my playbook by a factory reset wipe, and started greenfield.
My samsung galaxy android workes fine with 2010, and connects fine to the same server, to which the playbook cannot connect.....
Any suggestions?