I have a HTC Fuze on AT&T running the 6.5 Energy Rom. I also had this issue when running stock 6.1.
My work network is configured primarily for Blackberries, as that is what they provide for certain privileged employees. The policy is that that employees may sync their personal devices with the Exchange server, however their is no support provided. Everything was working fine until their security certificate recently expired. I contacted the network guys about this and they assured me that they would be renewing the certificate... eventually. There is no rush for this to happen and it could very well take months.
I am unable to sync my mail or calendar currently, as WM 6+ apparently does not give you the option of ignoring an expired certificate. I DO have the certificate installed, as everything was working fine before.
Does anyone know of a way to disable certificate "validation" on WM 6+? I have tried some of the tweaks and such mentioned for earlier versions, but it appears they are not valid on 6+
thanks
I apologize for bumping this, but I still have not been able to find a solution to this. I have found posts here and there referring to an inability to ignore expired certificates in WM 6 and later. I am hoping this is not the case. Any thoughts?
Bump. I could use a solution as well.
Related
Both of these apps worked on the previous version of the software for me, but now neither is for different reasons.
"Mail By Google" returns the error:
"Your phone doesn't support end-to-end secure connections (reason: Cause unknown). In order to protect your data, Mail By Google for mobile cannot be used at this time.
"GMail" returns this error:
This program required a data connection. Please contact your carrier, or visit the GMail for mobile FAQ on your ocmputer for more info.
The proxy has been disabled, both by running the CAB and by running KaiserTweak, and other browsers work fine, both Pocket IE and others that I have installed to play around with.
The phone is an AT&T Tilt, and it has the official ROM released a few days ago.
P.S. - I am willing to try one of the cooked ROM's if it'll work with AT&T's network right out of the box.
I'm having the same problems, please if anyone has suggestions please let me know. I'll even revert back to the original ROM if I could find it anywhere.
Same issue here as well using a cooked ROM. I've seen T-mobile related posts on blogs saying this is an issue with the GPRS settings but I've reset mine back to default to make sure and still having the same issue.
I am having the same problem since updating to the latest AT&T firmware. It worked fine with the shipped ROM (just got the device yesterday), but doesn't work with the new one.
You might need to unlock CAPTCHA on that email account, here's a good write up: http://www.mydigitallife.info/2008/...dentials-or-web-login-requires-failure-error/
NOTE: For Google Apps user, visit https://www.google.com/a/yourdomain.com/UnlockCaptcha instead, with yourdomain.com as the valid domain name.
Hello everyone,
Eventhough I have BB Conn on my AT&T 8525, my company would not help me get it paired with our BES, so I had them get me an actual BB. Now I'd like to just pull the SIM card put it in my 8525 and use BB conn. From what I have read, this should not be an issue; but I understand that the device type will show up on the BES. Now I doubt they have someone monitoring with such a fine comb, but since They will not let personal devices on, oh yeah, nor would they let me get a TILT as a BB, is there a way to spoof the device type on the BES or is this something someone would be interested in looking into as my programming skills are long gone. Thanks in advance for all your replies.
As far as i know there is no way of spoofing the BB device so that the BES sees your WinMo device as a BB.
Also i think it would be necessary for you to redo the Enterprise Activation anyway, as from the BES's point of view you would be a new device, this would require the assistance of your BES Admin.
This same solution worked for me.
But I am using BBC 2 on my Wizard.
All I had to do is to get a good (that is: BBC compatible) ROM version(I hacked it) and AKU value in the registry (hacked that as well).
I was then able to connect my WM device to the BES using the BBC desktop software. The BBC desktop software seems to push the device PIN (which is different on the WM device than on the BB device) to the BES.
Works flawlessly. BBC has some drawbacks BTW: I cant cope with big mail or calendar archives, so you have to clean up your Exchange account once in a while. BBC 2 is a memory hog as well (and it seems to have a memory leak). But a weekly / bi-weekly softreset fixes hat.
I am still curious to get BBC 4 on my device. This new version seems to have more difficult catches.
A how to guide on hacking the OS in order to rum BBC is in the development & hackng forum.....
That's as maybe, but if the BES admin has set it up so that only an allowed list of devices are allowed then BBC will not connect.
Also as there is an existing embargo on personal devices could it be against company policy and thus disciplinable to circumvent things?
As a BES Admin I can confirm that non BBs show up as something different. We have a Nokia Communicator running BBC on our BES and it shows as a Nokia RA-6
jrosaly said:
Hello everyone,
Eventhough I have BB Conn on my AT&T 8525, my company would not help me get it paired with our BES, so I had them get me an actual BB. Now I'd like to just pull the SIM card put it in my 8525 and use BB conn. From what I have read, this should not be an issue; but I understand that the device type will show up on the BES. Now I doubt they have someone monitoring with such a fine comb, but since They will not let personal devices on, oh yeah, nor would they let me get a TILT as a BB, is there a way to spoof the device type on the BES or is this something someone would be interested in looking into as my programming skills are long gone. Thanks in advance for all your replies.
Click to expand...
Click to collapse
I ended up doing exactly what you have done due to corporate policy. However I have never even unboxed the BlackBerry they posted me. I had to call the helpdesk to get them to create a password for the Enterprise Activation but that was it. I then installed BBC (4.0.0.97) and just did the activation and it all worked.
I tried version 4.0.0.100 but it didn't work for some reason so I ended up using the slightly older version as I had seen various reports of it working. I think our IT department must know I am using a HTC Kaiser, however I think as long as I don't start asking for support they are OK with it.
When they created the password for enterprise activation it lasts for a day or so and then can't be used and you have to request another activation. I can see this being a pain if you want to play about installing new ROMs.
HTH
Andy
Ok, I got my G1 a couple days ago and it's absolutely one of the coolest things I've ever used... I loved my Wing and MDA that I've used the past few years but this just absolutely blows them away. As soon as it gets an exchange connector and longer battery life(!!!!!) it will be perfect. (I've had it for 2 days and have had to fully charge it 4 times.. and the GPS and Wifi are normally off).
Anyway, to the point, I have a couple of email servers that I run with self-signed certificates over secure imap (port 993). It allows me to choose secure imap but apparently does not appreciate the certificate I created since it comes back and tells me its invalid (because of the unrecognized certificate authority although it doesn't state that specifically). I haven't dug down into it much yet (hoping somebody might already know the answer) but there has to be a way to tell it to accept the certificate anyway (just like any other email client on the planet). Ive opened up 143 so I can at least get email (and it works beautifully!) but I would really much rather have an encrypted connection.
So, if anyone out there might know, I'd appreciate a push in the right direction.
Thanks!
self signed email server certificates solution
bytesniper,
A recent arcticle on http://www.androidinmymobile.com has information about the new experimental fork of the mail client called K-9, and it works with self signed certificates. At last secure imap
Dazza
self signed certs
Not only does it support self-signed (and other, e.g., mismatched hostname) certificates, but webdav (a.k.a. Exchange) support will be available shortly. I'm already running a developer version of it on my g1, and it works nicely.
Hi Everyone-
My company recently upgraded to Exchange 2007 and I cant synch up anymore. I have reset my device and tried a few other things but the only thing that works is that it enforces the security policy on my phone.
I cant synch with Exchange 2008 and keep getting the error code "0x85010013" on my titan.
I am running The ScottCrosler ROM that is built of DC 3.2.6.
It worked just fine with Exchange 2003.
Please note that I work 50,000 employee company so I cant ask the exchange administrators to change their settings. But I am hoping there is something I can do on the Phone to correct this.
Thank you!
Exchange 2003 -> 2007 isnt a rolling upgrade so you've got to add a server and junk...a lot of configuration...which means there is much that can go wrong...
...there probably isnt anything wrong with your phone. Its much more likely that the Exchange "upgrade" isnt playing. Surely there is someone in IT who you can talk to.
If not...please let us know who you work for so we can be sure to never ever do business with them.
HAHA---
I worked with IT and they fixed it by creating a new security profile for me "only" and now it works.
Looked like the security policy in Exchange 2007 does not work well with the cooked ROMs.
Hi all,
We have some HTC Hero's in my office and they have been connecting fine to the MS Exchange Servers for our e-mails fine through active sync.
But yesterday the IT Guys updated the Security Certificates and now we get an error message telling us that the site is not trusted anymore.
We have been sent some updated certificates for windows mobile phones, they are .p7c file, and some files called certificate.cer and intcertificate.cer.
My question is do these files work ok on the android O/S and they arent going to mess up the phone?
Thanks for any support you can offer,
I've not had a problem like this following our exchange certificates being updated. They've just worked
Only thing I could suggest is that you have SSL turned on in your exchange account settings on the Hero.
Hi,
In my organisation, the certificate for OWA is signed by a self signed CA. The first time I synched my Hero, it told me the certificate was invalid. I clicked on the Allow button, it never bothered me again.
I didn't find anyway to import external certificate (CA or server), but it doesn't seem to be needed.
Hi,I have the same question about sync to exchange2007.
At first ,you choice the allow button,it not bother you only at the live session.
If you restart you Hero, it told again, It's so unconfortable.
How to join the .cer file in the android? If the system believe the .cer,maybe it's working well.
Does anyone know the answer to this one?