06-08-2009 03:27 PM
06-08-2009 04:23 PM
On the CWA side is windows authentication disabled and defaulting to Form-based authentication?
06-08-2009 04:47 PM
Disable forms based and see if it connects.
06-08-2009 04:50 PM
I made the change, but still get the same error. I'm on the phone with AT&T support and trying to work through this with them. I've spoken to two reps so far that haven't even known what Enterprise Messenger is (they're confusing it with Enterprise Paging). I'm currently waiting for them to connect me to BlackBerry which I would assume would give me a better chance of success. To be honest, it's not something that I expect will be resolved (maybe I'm a pessimist), but if they do figure it out I'll definitely post the solution.
Thanks for your help so far. If you have any other suggestions, I'll gladly give them a shot.
06-08-2009 05:05 PM
Since you have made the changes have you restarted your BES or at least restart the colobaration service?
06-09-2009 03:46 PM
I did restart the server when making the changes, it didn't make a difference. I finished up with AT&T tech support and they told me it's a RIM issue (which makes sense). I don't have a support contract and it's not worth it to me to do a pay-per-issue case on this right now. If we have to do without it, we'll do without it. I'd just like to solve it to satisfy my own personal nerdy curiosities.
I'll continue to try most anything you come up with.
06-09-2009 05:57 PM
Give these a review:
Also, make sure the collaboration service is enabled for the user ... also, verify that the user can login via CWA