Hello,

I've been working on this one for days

We have an exchange cluster here on a private LAN. I am using ISA 2003 as the 'middle man' between the Internet & our private Lan.

This has enabled us to get Outlook web access from the Internet, so that part works fine.

I can also get OMA working from the Xda too, via the browser.

However I can't get the unit to Activesync. I get the error :
I'm assuming I've got the ISA server publishing the Exchange cluster correctly as OWA and OMA are both working.

I've overcome the issues with getting self generated certificates onto the Xda & making the name match the server's name, but can't get any further.

Googling results in people who encounter this error after Activesync has been working for a period of time, but not on their first attempt to get it working.

Activesync does work on the Xda when sitting it it's cradle & talking to a local copy of Outlook, but that is not what I am trying to achieve here.

I have read that I may need to do a hard reset on the device, the Xda belongs to my boss, I was hoping not to have to go via this route.

Another option was to turn on verbose logging for ActiveSync. I have done this, and according to Microsoft the log file should be sitting in the Windows\Activesync folder - but there is no log file there! Does the Xda put log files somewhere else?

Another option was to enable logging on the exchange cluster, however this article refers to Mobile Information Server, which was used before Exchange Server 2003 came on the scene, so I do not know if it applies anymore.

Can anybody offer any suggestions? I've searched for days, and can't seem to get any further. I don't have another device to test it from, if necessary I am happy to create a test mailbox, and provide login details so somebody else can try, if you are willing.

HELP!!

Don't suppose their is some online testing web site somewhere is there? Like there are many online DNS testing web sites, would be good if there was an activesync online testing site!

I had the same exact issue when I stumbled accros this board by searching google for the same error msg.. However I just resolved mine by changing the network domain name name to upper case as opposed to lower..which is actually how it is displayed....it now works ...go figure.