Ok, I'm drifting from the original thread, as I have a similar problem with
mine (Motorola Q w/ WM5, SBS2k3, can't sync over air or corded).
Here's the setup:
1. Work computer has SBS 2003, with exchange, dummy ip address. It is behind
a hardware firewall router, with a static ip address. Port forwarding is set
to forward port 443 to the server.
2. My isp has an "A" record to point the hardware router's public static ip
address to the internal dummy address of the SBS server. There is a
commercial security certificate issued by a third party, and the
corresponding cert is installed on the cellphone.
3. On a remote computer, I can type https://servername.company.com in a web
browser. I get the Welcome to small business server 2003, with the options :
My Company's Internal Web Site, Network Configuration Wizard, Remote Web
Workplace,
Information and Answers. Clicking on remote web workspace gives a second
login panel, and then sends me to
https://leonserver.etexaslawyers.com/Remote/default.aspx which has Read my
company e-mail, Connect to my computer at work, Download Connection Manager,
Configure your computer to use Outlook via the Internet, View Remote Web
Workplace help. Clicking on read my company email sends me to the familiar
OWA.
4. On my Q, I have the server name as servername.company.com, the domain as
mydomain, etc. The phone will report that it is synching folders, but no
synch actually occurs. I finally wind up with the dreaded 0x85010014 error.
I've reset the q to factory, reinstalled the security cert (confirmed with q
support that it's the correct cert, and properly installed) and still no
luck.
I'm assuming that this is a misconfig on the SBS server (which is why this
is crossposted), but I'm completely stumped.
Please help!
David L. Leon, P.C. - 31 Jul 2006 04:55 GMT
And then one day David L. Leon, P.C. said,
> Ok, I'm drifting from the original thread, as I have a similar problem with
> mine (Motorola Q w/ WM5, SBS2k3, can't sync over air or corded).
[quoted text clipped - 34 lines]
>
> Please help!
OK, an interesting follow up:
I reran IECW, and it failed at about 90% completion. The log revealed that a
temp file couldn't be deleted. This now causes
https://servername.company.com/echange to give a 440 error, and /OMA to
state that "A System error has occurred while processing your request.
Please try again. If the problem persists, contact your administrator."
I was just about to give up hope when I looked down at my phone
and...activesync was dutifully synchronizing folders (!)
Ok, having /exchange working is secondary (no one uses it) but I'm downright
stumped that AS is working when /oma reveals an error. Should I bother
trying to fix any of this or should I just leave well enough alone?