I'm using - Dell laptop with integrated Dell bluetooth, XDA2 with original 1.03 rom, ActiveSync 3.7.1, Windows XP+SP2. I *AM* able to: synchronize fine with USB cradle, synchronize with IR, and beam files directly to the XDA2 from the laptop via bluetooth.
I have successfully: removed all traces of Widcomm, removed and reinstalled the plain old XP/SP2 BT drivers, have removed the pairings and re-created the device pairings successfully, removed and re-created the incoming COM port, renumbered my incoming COM port to 3, set ActiveSync to 'allow serial connection' to COM3, turned off XDA infrared, tried out "Pocket Bluetooth Tools" too, disabled my firewall. I moved my modem from COM3 to COM13. All the devices are 'working properly' according to control panel. Bluetooth switched to 'On' on XDA, once already paired. Bluetooth Devices/Options/Connections/Allow BT devices to connect is ticked.
Now I have tried to connect as documented in the many webpages on this subject, including GeekZone:
A. On the desktop - ActiveSync/File/Get connected... gives the message 'looking for mobile device on IR and COM3' but then nothing happens. After failing, it shows the list, and COM3 is 'available'.
B. On the XDA2 - Start/Settings/System/Bluetooth settings/Start activesync setup - gives message 'Please bond with device supporting serial port' - then takes me to the bonding screen. But I am already bonded successfully!
C. On the XDA2 - ActiveSync/Tools/Connect via BT with 'Laptop' - gives the message 'Cannot start communications with the desktop computer, critical error 608'.
As the pessimistic bobopopo recommended, I tried doing these last things repeatedly in every possible order!
Possible clues as to the problem:
1. I can't get the bluetooth icon to come up in the system tray. It comes up temporarily if I uninstall and reinstall the XP-SP2 drivers, then goes away next time I reset - even though the item 'Show the BT icon in the notification area' is always checked.
2. The first time I make a pairing, the word 'connected' appears below the icon for my XDA2 in the "Bluetooth Devices" dialog, on XP. Once it goes away, thereafter I am unable to get it to say 'connected' again. How can I get it to connect?
3. First time I bonded I got the Pocket Bluetooth Tools profiles dialog on the XDA2 - and ticked all the boxes, including serial port. Now I can't seem to get that screen back again?
4. On the XP machine, if I go to Control panel/Bluetooth Devices/Devices, select the XDA2 that is paired, then Properties/Services, I get only 'Dial up networking', and no exciting stuff like COM, OBEX, audio, PAN etc. - is this right?
5. If I go to Control Panel/Bluetooth Devices/COM ports/Add/Outgoing, and put Browse.., it searches for a while then says 'Windows cannot find any Bluetooth devices. Make sure it is switched on' etc.. although the device is clearly visible. So I can't create an outgoing COM port.
6. Can't beam files from XDA2 to Laptop: though XDA can see the other machine when you try to pair, it can't see it when you go to File/Send To/Infrared recipient - just empty dialog 'Searching...' forever. ('Accept incoming beams' is on and Bluetooth is on.)
????? Is it me or is it Microsoft ?????
mate,
reading through your post (although don't consider me an expert on this) it appears that you have the same problems i had before. bottomline? i discovered that windows xp service pack 2 screws up installation of bluetooth software. took me ages to figure this out but what i did was uninstall sp2 and went for sp1 instead. i've read several posts here and in other sites that sp2 doesn't really do well for bt apps...not sure if this is the same for the other chaps but it sure was for me. anyway; i uninstalled all bt software, uninstalled sp2; installed sp1 (reboot, etc), and from there proceeded with reinstalling my bt and activesync apps. from there i followed the guide given in geek zone and presto bt activesync.
the items you described in 1-6 definitely remind me of the sp2 trouble i had.
hope that helps.
cheers mate
I found that if I use the cradle to link to activesync this will create the partnership, then use the bluetooth next time and it will work, it seems you cannot get an original partnership over bluetooth.
I don't think its SP2 itself thats the problem. Its the Microsoft bt stack built into SP2.
You can actually run SP2 and the Widcomm bt stack. If you install Widcomm before SP2, then it won't install the Microsoft bt stack. I had the same problem and this resolved it.
The Microsoft bt stack in SP2 is Microsoft's first attempt at bluetooth. Looks like they still have work to do.
JD
Bluetooth activesync is easy IF YOUR NOT in Windows XP SP2!!! best thing to do is to downgrade to SP1.. unfortunately for me im stuck with SP2 in my desktop... but upon discovering this problem i never upgraded my laptop to SP2.. i left it with SP1 nd everything works in harmony...
MORAL LESSON OF THE STORY: NEVER UPDATE TO XP-SP2 if your using bluetooth activesync. :wink:
I've had no problems syncing over BT with SP1, SP2 MS stack and widcomm.
Here's how.
First of all delete any pairings on both PC and XDA.
Sync over USB then on the computer use connection settings to select the correct BT com port.
On the XDA goto Settings->System->Bluetooth->Start
Now repair your device and select ok till you get back to today screen
Goto activesync and then tools->sync over bt
Always has worked for me. If you're still having problems its quite possible that you haven't got the right ports setup on the PC.
YUP! it's all about the COM ports... SP2 gives out extremely high COM ports that activesync doesnt recognize...
Is your PC using...
1. SP2 + MS bluetoooth stack
2. SP2 + Widcomm bluetooth stack
I've followed the method laid out by fruitloaf many times, and only the 2nd combination works for me.
You might also want to consider upgrading from rom 1.03 if you can.
JD
fruitloaf said:
I've had no problems syncing over BT with SP1, SP2 MS stack and widcomm.
Here's how.
First of all delete any pairings on both PC and XDA.
Sync over USB then on the computer use connection settings to select the correct BT com port.
On the XDA goto Settings->System->Bluetooth->Start
Now repair your device and select ok till you get back to today screen
Goto activesync and then tools->sync over bt
Always has worked for me. If you're still having problems its quite possible that you haven't got the right ports setup on the PC.
Click to expand...
Click to collapse
Fruitloaf, is yours an original Orange machine? I've heard this works with SP2 + MS stack, but the O2 Xda II doesn't.
JD
I had this problem constantly with my XDA II and a Toshiba Laptop. All routes of advice came to nought.
The answer for me was to install Pocket Bluetooth Tools, a BT connection manager which has a specific Activesync Profile. Using this has enabled me to use BT A/S with my Win XP Tablet SP2 PC without problems. You have to initiate the Activesync process from the XDA though.
Once you have installed BT Tools, and created an A/S profile using the cradle, go back to the XDA and delete all existing BT Pairings. Then go through the "Bluetooth / Paired Devices/ New routine again. After finding your PC, continuing will give a new Dialogue box with available pairing options. Select "Activesync" and finish. Do a soft reset.
From there, go to Start/Activesync, then tap Tools/Connect via Bluetooth and all should work.
I recommend using PBT Tols version 1.0.1.2 not the newer version, as the later version causes some power management problems with the XDA II.
Available Here
bluetooth virtual com port too high for activesync
I have a Belkin F8T001 v2 BT USB dongle. BT was working under win xp sp2 and could transfer file etc from PC to XDA IIs and back.
However I tried setting up a BT active sync connection and had the problem that the virtual com port picked by the belkin supplied widcomm BT driver was too high for activesync, it was com20. I followed this thread but could not uninstall the driver and use the driver from SP2 as it doesn't seem to support my belkin USB BT dongle. So I had to go back to the driver supplied by Belkin. I thought I was stuffed until I came across a post that sorted the problem, I'm afraid I dont have it to hand to give author the credit. But here is what he/she said to do.....
1. Disable bluetooth in device manager and remove the high numbered com port from device manager.
2. Then use regedit to change
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\COM name arbiter"
I followed the instructions and changed the first 3 entries in theComDB field to be "0f".
3. Enable Bluetooth in device manager
4. Use bluetooth settings -> local servies to add a new COM port, then set it to autostart in the profiles section.
This time it came up as com5, and bingo activesync could find it and I was off....
Hope this helps others with this problem, usual disclaiamer when fiddling with registry back it up and dont blame me if it doesn't work or your equipment goes up in smoke
Good luck, Wayne
http://www.geekzone.co.nz/content.asp?ContentId=3163
this guide works just fine for me
Marc MD said:
YUP! it's all about the COM ports... SP2 gives out extremely high COM ports that activesync doesnt recognize...
Click to expand...
Click to collapse
That's is my problem, the high COM ports are not recognised by ActiveSync! I think i have 2 downgrade to SP1 and then upgrade again to SP2, hopefully that will work.
The BT drivers is not my problem but it's impossible to select the com port in activesync (but the com ports are visible in the device manager!).
Thanks to this forum for geving me hope , now i know what the problem is.
If you read my post with the registry change above I think you will find it will solve your problem, as I stated this was the only problem I was having with the BT driver.
This is a lot simpler than downgrading to SP1 etc.
AT last I done with this help and use widcomm Bluetooh Software 1.4.2 bulid 10 now my active snc work great with winxp sp2and wm2003se ..
just flow the thats:.....
This issue may occur because the Bluetooth drivers that are provided by Microsoft support a different set of profiles than the drivers that are provided by some third-party vendors. The Microsoft-provided drivers are also signed and will therefore be installed instead of a third-party driver for supported Bluetooth adapters. The Windows XP SP2 Setup program will try to detect if a third-party driver is present. If the third-party driver is installed, the Microsoft-provided Bluetooth drivers will not install. This action makes sure that an existing configuration is not modified. If both provided drivers were installed, and the Bluetooth Radio were connected to the computer, the Microsoft-provided driver would load because it is signed.
If the missing functionality is critical, you may restore the third-party support. To do this, follow these steps.
Note The following steps assume that the third-party software is installed. If it is not, install the software according to the manufacturer's instructions. Then follow these steps from the point in the installation process where the adapter is connected to the computer.
1. Click Start, and then click Run, type devmgmt.msc, and then click OK.
2. Locate and then expand Bluetooth Radios.
3. Right-click the Bluetooth adapter, and then click Properties.
4. On the Driver tab, click Update Driver.
5. Install the updated driver manually by using the Have disk option in the wizard. Locate the manufacturer's installation files, and then find the .inf file that is required to install the driver.
6. Complete the manufacturer's software installation steps.
At this point, the third-party provided drivers should work. If at any point you re-enumerate the Bluetooth adapter, the Microsoft driver will be reinstalled, and you must repeat the procedure. This issue will occur only if the third-party driver is removed or if another model adapter installed.
thats link is for bluetooth software v 1.4.2.10
http://asia.giga-byte.com/Communication/FileList/Driver/btd01.v.1.4.2.10.zip
i've tried everything but it still gives out high COM ports...
Marc MD said:
i've tried everything but it still gives out high COM ports...
Click to expand...
Click to collapse
Go to device Manager, find those high Com Ports, choose Properties - Advanced and at the COM port number choose a low one, Like COM3 etc. Don't bother if it say that it is alreaddy in use...
The go to Active Sync and in the Connection Settings choose from the drop down menu COM 3...
Go to the Activesync in you XDA, in the Options choose connect using Bluetooth and the... click on Connect via Bluetooth from the XDA...
You're done...
I have an O2 Xda II Mini (Magician) and I am using an XMicro Dongle on my laptop (Win XP with SP2) and ActiveSync3.8. Initially syncing with BT was a problem but now its not a problem at all.
To reduce the COM port nos. on your computer try the following website
http://support.microsoft.com/default.aspx?scid=kb;en-us;315539
Once you can see the hidden devices and ports delete/uninstall all the ports which are not in use.
1 To sync with BT first delete all your pairing with your computer and phone on both devices.
2 Go to BT Manager on your phone and click both check boxes for Inbound and Outbound COM ports and pair the devices.
3 Once they are paired go to BT manager again and click on the start button (for BT activesync setup) and pair the devices again if you have to.
4 Once that is done check on the computer in BT Manager click on the phone device>property>services....the Serial Port Profile (SPP) "Serial Port COM4" will be checked.
5 After that on the computer's BT Manager itself ensure that the COM ports folder shows incoming and outgoing ports with the phone's name in front.
6 On the ActiveSync (on the ocmputer) ensure that the COM port no. is the same as the Incoming COM port no. given in step 5 above and it being shown as available. Sometimes if it is unavailable, the computer needs to be rebooted and then it will be shown as available.
7 Click on ActiveSync thru BT on the phone and it should work.
It has been working for me since the past couple of weeks. Initially it took a lot of time to set up but now even if the pairing gets deleted or something messes up its working fine. One thing to remember is that in case you are using a dongle with a laptop ensure that the dongle is plugged in BEFORE you boot up the laptop. A lot of people plug it in later and then ActiveSync on the computer shows the COM ports as unavailable.
Hope this helps.
I've just received a pair of 9100's from Expansys for me and the Mrs (I couldn't stand the look of torment on her face as she pecked SMS messages out on her old 6310 any longer) and, with trepidation installed AS4.0 over the old, trusty 3.7.1 or 3.8... Result... sh4gged...
On my laptop, I added rules to Sygate, tweaked connection manager, re-installed and patched Outlook, upgraded to 4.1 and everything else I could think of and it's still broke. It hangs on the Retrieving Settings bit. Curiously, even with it stuck, pending installs actually get installed...
On the work laptop where we mere users are policy'd out of everything it didn't get that far as the desktop security settings weren't having any TCP over Ethernet over USB at all.
Anyway, stroke of inspiration (and apologies if you guys already knew this) activated ActiveSync over IR on the 9100, pointed it at the laptop's IR port and bingo... All sync'd up without a whiff of a complaint or lock-up.
It looks very much like MicroSoft's desire to make the USB's old Point to Point IP link look like a real network interface in a world were network interfaces are mostly policed and firewalled to death is the problem, rather than ActiveSync 4 itself. Now, on my work laptop, my hx4700 will ActiveSync over AS4.1 on USB and the 9100 will do it over IR.
Shame my own laptop has no IR port otherwise I'd be happy (until MS fix the thing properly). Might try with my BT dongle instead.
Anyway, hope this if use to somebody out there...
Found the below in a German IT news ticker.
http://www.heise.de/newsticker/meldung/65210
It basiccaly says, that MS confirms Active Sync 4 problems with Firewalls, and plans to have a new fixed Active Sync Software by the end of Nov.
They also reccon to open TCP-Ports 990, 999, 5678, 5679, 5721 and 26675 in the Firewall to make it work until the fixed version is ready.
Hi,
I have a magician, and I have problems with the network passthrough (activesync on USB) for a year (ip worked, but not DNS resolution). I just upgraded to ActiveSync 4.1, and suddenly the passthrough works fine, great!
Now for my next step -- how can I access my device from my desktop pc? As far as I can see I can't get any route to 198.168.55.101 (device' ip) and there is no interface for that visible in ipconfig. Host is running XPsp2 (no firewall).
My ultimate goal is to experiment with a VNC server on the device.
Any input/comments are welcome! Thanks!
i never finished my trial...
but i get the following to run:
On DesktopPC bind a listen Socket on 127.0.0.1 TCP Port 123.
On PocketPC connect a socket to 192.168.55.100 TCP Port 123.
The 192.168.55.100 and 101 IPs are only for the Serial communication.
I currenty don´t know how to access this directly, but i don´t think that you have to do this. Loopback works fine.
I did not try the other direction, but i think it would also work fine.
So how would one do this in practice?
I have read a lot of the comments on ActiveSync 4.1 and the different things to try to get it to connect over USB ... I'm amazed!
I've Just 'upgraded' from a XDAIIs with ActiveSync 3.8 and used to have this connected all day on my desktop at work via USB cradle and sync over WiFi at home.
Very dissapointed at the moment ... was shocked to see that sync over WiFi is not supported (and I don't have BlueTooth and don't want a dongle) I've tried loads of suggestions from here ... disable firewalls, ensure TCP/IP setting correct etc and nothing seems to work.
The only thing I have found is that the XDA Mini S needs to be 100% charged and have a green light when connected to the USB cable, The USB 'not' connected to a hub (unlike my XDAIIs) and ActiveSync NOT running on the Mini S (i.e. perform a soft reset or use task manager)
Then ... and only then can I get it to sync ONCE. That combined with 'NO' cradle makes it a pretty useless business device unless you run a sync server.
ActiveSync 4.1 and Mobile5 have even stopped me from syncing my XDAIIs as a 'guest device' as ActiveSync 3.8 is not allowed to be kept on the laptop
I'm not even going to venture into installing TomTom on this! I'm sure thats a whole new kettle of fish!
if anyone has any further suggestions I'd be gratefull .... otherwise, here's hoping a future ActiveSync 5 or Mobile5 ROM upgrade is going to sort all of these issues.
Rich :evil:
Mine worked by enabling my local area connection although i have no local network, my laptop has a socket and windows firewall is disabled and zone labs firewall = added activesync to list of accepted programs. Works every time now
Hi,
do you know why my HD2 can sync only when plugged with usb cable and not with bluetooth? It has been correctly paired with my Win7 ultimate, but there is an ! on it in the device manger saying that no blueottoth device drivers has been loaded!
thank a lot in advance
M
I also get the device not recognised problem, but that's only for one part of the bluetooth stack - can't remember quite what it's for. Regardless, I am able to pair and use active sync with my 2 Windows 7 machines OK. I do have to use the active sync application on the phone to do it though - I can't just pair the devices then run active sync.
In the device center you have the possibility to setup your connection settings. Go to settings - connection settings - leave USB ticked - in the next connection possibility change bluetooth into com5 or com6 and you're ready to go.
I have kinda the same problem with Win XP and my HD2.
- I successfully paired the PC (Dell D820) and the Leo.
- I can successfully exchange files from the PC to the HD2 via bluetooth - but not the other way round (Leo says the PC does not support this ).
- I can successfully sync the Leo to the PC via USB cable.
- When I try to sync via bluetooth, HD2 says that the PC "does not offer any service that can be used with ActiveSync".
- Leo has incoming Bluetooth port set at COM1.
- XP has Bluetooth ports set at COM1 (incoming) and COM3 (outgoing).
Anyone out there has a clue?
Thanks.
I had to set com7 to make it work
I simply leave WMDC set to use "Bluetooth" and it works fine. Check that, then on the phone select the pc, in the BT manager, menu-> update, it should rediscover activesync and list activesync.
Hi,
I am facing the very same problem, please help...
Same problem here with Windows XP. Pairing is ok, discovering Activesync service fail. I never had this with my previous PDA.
kilrah said:
I simply leave WMDC set to use "Bluetooth" and it works fine.
Click to expand...
Click to collapse
WMDC?? On WinXP? Was that a typo or am I missing something?
vince2773 said:
am I missing something?
Click to expand...
Click to collapse
Probably that the original discussion was about Win7, so I assumed the rest was about it too
I didn't see your particular case was under XP, sorry.
But still, same went for XP, except replacing "WMDC" by "Activesync", and select the outgoing COM port your PC has assigned to the HD2 instead of "Bluetooth". NOT the one your HD2 shows as incoming.
Thanks for the clarification Kilrah (I didn't mean to be rude, I was just in a hurry).
Anyway, I tried as you said (which I had already done, but tried again just in case). No success with Bluetooth sync.
Guess I'll stick to the USB cable and wait till June when my new laptop comes in with Win7 and try again.
Too bad though. Bluetooth sync worked like a charm with my old Nokia. So far, this is the only major disappointment in 2 months with my HD2. Maybe it's because ActiveSync itself is a crappy app?