Problem connecting iTouch to Exchange Server

[Azure]

I input all the settings correctly, at least according to the instructions on the Apple site, and it verifies them properly, but it says connection to server failed whenever I try to download email.

Any solutions?

[sclitheroe]

Do other iOS users at your location have it working? There are myriad reasons why it could be broken.

[Azure]

Nope. I'm the only one that has tried. I suppose I could test it on one of their devices.

Exchange Server is 2003.
iTouch 3rd Gen with 4.3.3 firmware, and it is jailbroken.

[Rathji]

What do your IT people say?

[mykalberta]

I know there was a 4.2.1 bug with EX03

I assume its EX03 SP2 ?

[Azure]

I'm not sure what the SP is. I'll have to ask.

From what I've read updating is the best bet, so I'll have to pass that on.

[Bill Bumface]

[cough]iPod Touch[/cough]

[Barnes]

In the Domain box, I think mine didn't work when I had "lmnop.com" only "lmnop" worked. Try that?

Check to see which mailbox is being pushed in settings > mail > YourAccount... Maybe it's trying to push some weird folder...

I dunno, it's pretty straight forward to get it to work on the phone side.

[Rathji]

Just for kicks I tried mine, cant get it to connect either, but exchange 2007.

Nevermind was a typo in server address. Connected without issue to Exchange 2007 with an iPod Touch 3rd Gen, 4.3.3

[Azure]

Originally Posted by Barnes

In the Domain box, I think mine didn't work when I had "lmnop.com" only "lmnop" worked. Try that?

Check to see which mailbox is being pushed in settings > mail > YourAccount... Maybe it's trying to push some weird folder...

I dunno, it's pretty straight forward to get it to work on the phone side.

Domain box is optional but I tried both options and neither worked.

At this point I'm thinking the Exchange Server may need to be updated to the latest service pack based on what I've read.

[Azure]

So we're actually running Windows Server 2003 for Small Business, and SP2 has been installed.

Apparently only minor updates haven't been installed. Stuff like .NET framework, etc, etc.

They are running them now so I'll check and see if it fixes anything.

Any other ideas?

[Barnes]

Can you run the CEICW (Configure Email and Internet Connection Wizard) on the server and see if Outlook Mobile Access is enabled? Setting up Exchange and ActiveSync is the same for iPhone as it is for Windows Mobile devices so maybe you can find some help online through MSDN etc...

[sclitheroe]

Use this as a baseline check that ActiveSync is going to work:
https://www.testexchangeconnectivity.com/

There is also a free ActiveSync tester app on the app store that you should grab and see what it reports.

[Azure]

Thanks for the help guys.

Some more updates were run, so I'll check to see if anything changed.

[Azure]

So after all the updates were installed I installed Active Sync Tester from the App Store and the result was that ActiveSync IS available, but certificate problems were detected.

"The Exchange Server is setup correctly for mobile email but the certificate provided by the server is not valid. Typically this occurs because the certificate has expired, has the wrong name, is self signed, or was issued by an untrusted CA."

[Rathji]

Do you have a SSL cert for the server?

[sclitheroe]

Certificate errors are the number one cause of issues with ActiveSync, so far in my experience supporting the devices. Unfortunately, it's something your IT people need to fix, its nothing that you can work around on your end.

[Yeah_Baby]

Originally Posted by hulkrogan

[cough]iPod Touch[/cough]

I wish I could thank this twice.

/Pretentious Hipster Mac User.

[TorqueDog]

Originally Posted by Azure

So after all the updates were installed I installed Active Sync Tester from the App Store and the result was that ActiveSync IS available, but certificate problems were detected.

"The Exchange Server is setup correctly for mobile email but the certificate provided by the server is not valid. Typically this occurs because the certificate has expired, has the wrong name, is self signed, or was issued by an untrusted CA."

I've seen that a lot of smaller businesses use a self-signed certificate to save money. Problem is, the amount saved is moot compared to what a UC certificate goes for on GoDaddy, and self-signed certificates introduce a myriad of problems elsewhere, particularly where Exchange ActiveSync and Exchange Web Services (in newer versions of Exchange) are concerned.

That said, you can apparently get iOS to play nicely with Exchange ActiveSync that does not have a valid third-party signed certificate by using these instructions (Yes, it says Exchange 2007, but this only involves the certificate and as a result this could work with any version of Exchange, from 2003 to 2010).

I haven't tried them, so I can't say with 100% confidence that they're still valid on the latest iOS version.


I'm kind of disappointed in this thread, I was hoping I could be uber-nerd and talk at great lengths about Exchange Web Services and the importance of properly configuring Autodiscover. There goes my opportunity to be a massive nerd one more time before I go on vacation.

[cKy]

Originally Posted by Yeah_Baby

I wish I could thank this twice.

/Pretentious Hipster Mac User.

It isnt that it is pretentious, it's that Logitech owns the iTouch name.

... sigh - i still call mine an iTouch.