Got a smart phone with wm5, got a exchange 2003 server, got AS 4.2 on the desktop.

Plug phone in via USB: phone sits syncronising for half hour without doing anything. Dunno whats happening there...

Sync over wifi: Server doesnt like my SSL certificates, tried a free one I made and the SBS one too.

- Disable SSL on the phone: server dont like it.
- Hack the phones reg: server wont take my user/pass.
- Take the 443 port out the default web settings = waiting for server response or something.

Its crap. Cant make a proper certificate cos theres no dns name for our OWA doo-dah and I cant make a certificate with an IP address cos Im a phone newbie.

Anyone here deal with them? Otherwise, just call this a rant.

I do - send me a PM and I can sort you out

omg thanks, you want me to outline our whole system?

 :bowdown:

Ill do it right after work.

K, I gotta get this fixed for brownie points.

Heres what I got -

Connecting via usb;

device: 169.254.2.1
pc: 169.254.2.1

Device says "unable to obtain a server-assigned IP address. Try again later or enter an IP address in Network Settings." - I think this is the Wifi bitching cos the Windows PC syncs but MS exchange doesnt.

I get:    

---------------------------
Microsoft ActiveSync
---------------------------
The server could not be reached.  This can be caused by temporary network conditions.Support Code:80072ee2
---------------------------
OK  
---------------------------


Connecting via WIFI:

Result: You have an incorrect SSL Certificate common name in the Host Name field.

Support code: 0x80072F06.


Server setup:

SSL certificate no.1 (SBS server generated):

CN = server.company.local
CN = companyweb
CN = gtisbs
CN = localhost
CN = gtisbs.company.local

SSL certificate no.2:

CN = company.co.uk


- Problem here is our OWA is on an IP and it doesnt have a DNS name (afaik from doing a reverse lookup) so the common names dont match in the certs.

I need to either hax0r the cert to get that IP address in or I need to disable the SSL. Basically I just need the f**ker to sync over wifi.

Ive seen theres a WM5 emulator available form MS but it needs visual studio - can I use VS express for it?

How the hell can MS make something thats worse than Blackberry? The MS phone is a piece of flaky poo.

What handset is it?  There may be an upgrade around to WM6.1 which is much better.

Quite an old one I think; http://www.etccomms.co.uk/orange_spv_m600.htm

dump the crap self signed cert - you will need to fiddle around and imnport the chain into WM5 to get it working

use free trial certs from rapidssl.com

import the ENTIRE chain into WM5 - right back to the CA

The cert must be legitimate - ie the friendly name must match the url of your OWA server to avoid errors

WM6 will be useless as well, as youre using a sh*tty self signed certificate - you will still need to import your CA

edit: godaddy do certificates for OWA that also work - you could buy a domain and use that as your owa address - that would be the better solution if you dont have an authoritative domain name server for your organisation.

rather than a hash up, do it RFT - do you have a valid public address space that you can use an IP out of

You can also do it dirty and not require a secure connection, thus enabling you to synch over wifi - you could introduce basic security here by restricting access to the NATd address of your OWA server to the IP pools used by your mobile service provider.

it would maybe also be better to build up a frontend exchange box for owa and give that your public ip. Having a valid address associated with an sbs Wouldnt be the best ! What firewall sits at the edge ?

I dunno yet.

How would I set it up to not need a secure connection?

in the security settings on the properties for the exchange virtual dir in IIS,uncheck require ssl connection

Defnot advised - and double definately not advised if you have a public IP NATd directly to your SBS server

Quote from: soopahflyWhat handset is it?  There may be an upgrade around to WM6.1 which is much better.

I only have one complaint with WM6.  They have crucified the bluetooth stack.