Unable to Verify account info after OS4

It seems hit and miss for me, sometimes it works fine on wifi, sometimes it doesnt. Same for wifi off, very inconsistant. I spent 4 hours on the phone with ATT and Apple on the 23d about this and we only got as far as "when you reset network settings it will work"... but only for a few minutes and then back to either it will or it wont.

Toggling "airplane mode" on and off one or more times seems to fix the problem with Exchange Activesync connectivity via Wi-Fi. Don't know if it's a permanent fix or will need to be repeated. I am working with an Apple Expert on the problem and have made them aware of this fix in hopes it will help diagnose the problem.

My Exchange host tells me they have had a rash of these complaints in the last few days. They believe it is related to how iOS 4 works with Activesync, but it also seems to be impacting OS 3. I suddenly had the problem on both my iPhone 4 with iOS4 and my iPhone 3G with OS 3x. This "airplane mode" toggle fixed the problem on both devices, but again I don't know if it will be permanent or will need to be repeated. Hope this helps.

I wiped a test phone and tried the "new iPhone" method and still could not get the phone to work properly via WiFi internally at any of our business units. A few interesting thoughts here. The phone works correctly if we use the "internal" IP for our Exchange 2007 servers in the server area of the Exchange setup on the OS4 phone. It works from my residence via WiFi as well. This leads us in the direction of DNS and SSL certificate validation. This issue looks almost the same as the Entourage / SSL issues that we experienced on our MAC clients. I will reload 3.13 on all of our Version 3 iPhones until this issue is fixed. Our iPhone Version 4 phones will simply have to wait for the OS4 fix.

I'm using an iPhone 3GS, and I can sync my email both internally via wireless, and externally via 3G and VPN. We had a user that could not though, and after looking at our settings, we seemed to be identical. We checked the accounts on the exchange server, identical, then I added the port to the end of the mail server address, so it read something like this "mail.mailserver.com:443"...

This allowed him to sync internally and externally... This resolved our issue, but when speaking with an Apple rep, we asked if having the port in the address would make that big of a difference, he couldn't answer the question, but said it shouldn't...

Who knows if it does or doesn't, we got ours working that way... maybe it'll fix yours. 🙂

Scynthyace wrote:
I'm using an iPhone 3GS, and I can sync my email both internally via wireless, and externally via 3G and VPN. We had a user that could not though, and after looking at our settings, we seemed to be identical. We checked the accounts on the exchange server, identical, then I added the port to the end of the mail server address, so it read something like this "mail.mailserver.com:443"...

This allowed him to sync internally and externally... This resolved our issue, but when speaking with an Apple rep, we asked if having the port in the address would make that big of a difference, he couldn't answer the question, but said it shouldn't...

Who knows if it does or doesn't, we got ours working that way... maybe it'll fix yours. 🙂

Thanks for the heads up. I'll give that a shot next time mine acts up. It shouldn't make a difference, but you never know.

Yesterday, Apple released an article for a fix for this. They claim it fixes it but all it does is allow you to change the default timeout before the sync gives up. I tried the fix along with a co-worker at my office and this did not resolve our issue on iOS4. Of course we can still connect to Exchange on 3G or external Wi-Fi but not on internal Wi-Fi, which is the problem. Here's the link to the article and fix, maybe it will work for you:

http://support.apple.com/kb/TS3398

Just out of curiosity, have you checked your wireless settings? Maybe check to see if a laptop can sync via outlook over the wireless... Or make sure your wireless network has the proper routes to talk to the Active Sync server...

I'm out of solutions though, ours work, and I can't find a big difference in our config and what I have read here.

That definately sounds like name resolution to me. Check to make sure that your DNS points to the correct place, and that the route is good. If you are having issues sending it to ip.ip.ip.ip, try it with :443 on the end.

You can also try adding the domain structure, ie. mail.mailserver.domain.com:443

Hope this helps. 🙂

I've tried pretty much everything suggested here - i reset network setting, wiped and restored, wiped and initialized clean, deleted and re-entered my account information, downloaded the new timeout profile... regardless, my previously working configuration does not work (unable to verify, unable to connect).

I can access the exchange host (a godaddy server) via Safari and everything else works. Only my previously working Exchange account is inaccessible.

Anything else? I am going to have to go buy a new phone if this keeps up more than a day or so longer. This used to work so well (pre IOS4)!

Seeing as it's a go daddy server, I would contact them and request the following --

A direct IP Address to the exchange server
That Port 443 is open on their end
Where your mail server's DNS Name points to (The route)

Then I would try to use the direct IP they provide, if it doesnt work try that IP with :443 on the end... Ask them if they have had other people report any issues with email thats hosted on a server through them.

We host all of our servers on-site, but we always start with the host first, even with it being us. 🙂

Hope they can help some.

A direct IP Address to the exchange server
That Port 443 is open on their end
Where your mail server's DNS Name points to (The route)

I've done this and it does appear to work, but I got a certificate error. I accepted the certificate even though it's untrusted. would this cause any issues?