Hi Cabal
Have you tried what Belkin Technical Support asked me to try? I know my USB Bluetooth dongle is a different make to yours, but the solution should still work!
My version of ActiveSync is 4.2. but this solution should work with any version with Windows XP (Home or Pro.)
Is it the virtual Bluetooth COM ports your ActiveSyc cannot see? If so, the solution is very simple and I have been tearing my hair out for over two weeks trying to fix the problem I had!
Assuming you are running Windows XP Home with Service Pack 2, what you need to do is:
1. First "Stop" your Bluetooth device from the Windows System Tray (the bunch of icons near the clock.) Right-click your Bluetooth icon and choose "Stop The Bluetooth Device" (or whatever your desktop or laptop PC Bluetooth software shows.)
2. Unplug the Bluetooth device from the USB socket.
3. Press CTRL+ALT+DELETE to bring up your Task Manager.
4. Choose the Processes tab.
5. Find the process named WCESCOMM.EXE (this is the ActiveSync application filename for version 4.2. Your one should have the same name if you are using a different version.)
3. If you place your mouse arrow over the ActiveSync icon in the System Tray, it should disappear immediately. If you don't, nothing happens! Don't ask me how or why this works -- it just does!
(This works on my Dell home desktop PC and Windows XP Home Service Pack 2, not sure if it will work on your sysem.)
4. Plug your Bluetooth dongle back in and restart it (right-click the Bluetooth icon in the system tray and choose "Start The Bluetooth Device" or whatever your software says.)
5. Restart ActiveSync from your Start menu and choose "Connection Settings".
6. Check which COM port comes up. It should show the original Bluetooth COM port you set up. In my case it is COM4.
7. Then try to connect via Bluetooth from your PDA or mobile phone and it should connect first time.
Sorry all of this is long-winded, but it works for me every time and it's quicker than rebooting (which never worked anyway!) or (worse) reinstalling my Bluetooth software and ActiveSync for the umpteemth time (which did not fix the problem either!).
Hope this helps.
Alastair C Parker