What caused ActiveSync to be NOT accessible (or not seen) via Bluetooth?

In ActiveSync's connection settings I assigned it a (virtual) COM port provided by the Bluetooth stack on my Laptop (Win XP).

This works sometimes but more often than not, when I try to do sync my WM 6.0 device (HTC Touch HD) via Bluetooth the mobile device can not find the ActiveSync service on my Laptop (in such case it always offers a "Serial connection" only). Somehow, ActiveSync does not seem to grab or open the virtual COM port (or doesn't listen on it) on the laptop.

Why is this so damned brittle? I claim it is NOT the bluetooth stack causing the issue, because other connections via bluetooth (like object transfer, network sharing, and even audio transfer) work reliable. It's always only ActiveSync that is so shaky...

Michael

Todd Allcock wrote:
> Is the BT COM port selected in Activesync's connections options (on
> the laptop) as a connection? (There's a tick box and a drop down
> menu of all COM ports available on the PC- the BT virtual COM port
> needs to be selected.)

Yes, of course. Sorry, that I didn't even mention such "self-evident" details.

That's exactly what I don't get: That port is assigned to AS, but apparently it is not reacting on it...

I just deleted the Bluetooth pairing ("partnership"), deleted the device and then started all over, i.e. rescanned for new devices, paired and THEN ActiveSync was again shown as available service on the PDA. This will one day drive me nuts!

Michael