iPhone 2.0 Exchange over WiFi Does Not Work (Now It Does)

I recently upgraded my iphone to the new version 2.0, almost entirely for 1 reason: exchange syncronization.

After some minor issues setting up, I got things working correctly and it worked great.  But, as soon as I connected to a wifi and tried to do anything with exchange it fails.

I first experienced this at work where we use 802.11 WPA-PEAP, so we were eager to take advantage of 2.0s support for WPA-PEAP.  We installed the profile and were browsing at fantastic speeds… but no email was coming through.

I couldn’t send or receive any email.

We tried using the admin tools to look at the iphone console messages and they talked about some ASxxxxxx errors, error code 451 came up a lot.

I hoped it was something with our work network, but when I got home I found that once again, I couldn’t send or receive anything.

Fantastic.

I’m hoping I am not the only one with this issue and someone else will read this and have more to add.

Update: It seems that the cause, for some unknown reason, is related to the profile that our network administrator is able to create with some new administration tools from apple.  Apple provides a tool to create profiles so you can send a config file to an iPhone and it will setup everything (email, wireless access etc).  When this profile (even if only for access to 1 wireless network) is on my iPhone, all exchange communication over our WiFi failes.

Update 2:  Ok maybe there is something else going on here.  I have removed the profile and I still can’t send / receive from my home wifi.  I tried it at my parents house too and I get the same result.

Here are some keywords/error messages that I am getting:

Exchange Account Verification Failed

Cannot Send Mail.

An error occurred while delivering this message.

Update 3:  Alright, it appears we have it working now.  There were some settings across a few of our exchange proxy servers that might not have been updated, and also there are some activesync settings that allow you to configure an “inside” url and an “outside” url.  After much poking around, I think Mike Driscoll got it figured out.  Thanks Mike.

Setting up WPA-PSK on Cisco Aironet 1100 APs

I know what you are thinking…

Setting up WPA on an AP is so easy even my mom could do it!

Well, Cisco APs give you 1001 options and no clear way of setting up WPA-PSK.

To configure these devices here is what you need to do:

1) Express Security: Setup the SSID with Encryption of “None” and not WPA (yea I know…).

2) Under SecurityEncryption Manager, select to use a Cipher and pick the option for TKIP.

3) Under SecuritySSID Manager, select your SSID, and then pick “Open Authentication” with “No Addition”.  Then change Key Management to “Manditory” and select the “WPA” checkbox.  Enter a WPA Pre-Shared Key.

I ignored the other billion options.

 

The alias ServerName could not be opened…

Have I mentioned how much I don’t like working with Macs?

I have some friends who like them, so I won’t go as far as some Mac fanboys to claim that Macs suck and everyone is better off with an XP computer (but that is pretty much how I feel).

I bought a Mac for my wife a year ago, because at school there are still people emailing around clarisworks files, and from time to time we want to do something that would require accessing a shared folder on the network.

Problem is: it never works.

“The alias ServerName could not be opened because the original item cannot be found”

Searching google turned up 101 different ways to connect to a network share, and they all failed in different ways.

Last nigiht I found myself trying to get it to work once again, but this time I happened across a solution.

After hours of wasting my time, I finally found the solution here.

Windows 2003 Servers encrypt their communications, Macs can’t deal with this.  Problem solved.

Forced Security

The world is full of idiots.

Because so many of these people have wrecked their servers by accidentally installing malware, MS now feels they have to force hightened security on the rest of us.

So I have wasted 30 minutes trying to get an activeX control installed on a server.

IE won’t let me do it, even though I marked the site as Trusted, and even though I went through every ActiveX option in advanced tools and turned them all to Enabled.  Nope, still nothing.

I then decided to try changing the default security levels… oh wait, they won’t even LET me do that.  Are you kidding me??

I finally found a link to download an install.

Now IE tells me “Your security settings do not allow this file to be downloaded.”

Do I seriously need to go install firefox to just get this damned flie downloaded??

No, because thankfully I was able to open up the page source and go find where the activeX is getting pulled from, and realized it was coming from a different subdomain (which of course is not apparnet to any normal users).

Adding that subdomain manually to my trusted sites fixed the problem.

The whole thing is just stupid.