Bluetooth with no passkey ???

[John1234]

Hello,

There is a problem with using the Microsoft stacks for setting up a
Bluetooth connection to a device that does not require any passkey.

The device use Bluetooth SPP (Serial Port Profile).

When you select the "no passkey" during the discovery process, everything
looks fine but the Microsoft driver comes back and still requires a passkey
after the discovery.

This problem is only with Microsoft and is present on their Bluetooth stack
for all OS (Windows XP, Vista, Tablet PC editions, Windows Mobile 5.0 and
6.0). All other Bluetooth drivers on the market on all Operating Systems work
fine with no passkey.

For Windows Mobile 5 and 6 devices that use the Microsoft stack, there is a
work around: hit "next" the first time it asks for the passkey and entering a
blank space the second time it asks for the passkey. Mobile 6 still gives an
error message at the end, but it works fine once you ignore it. For XP,
Vista... a totally different story. I have tried everything possible on all
sorts of hardware and always the same results. You are forced to enter a
passkey to go further.

I know this issue has been reported many times to Microsoft by some hardware
manufacturers over the last 3 years, but it is only getting worse.

Does anyone have a clue of whatever could be done for a non-secure Bluetooth
connection, using the Microsoft stack, to a Serial Port Profile device that
does not require a passkey? Any idea on a work-around?

Thanks,

John

 

[Quaoar]

Hello,

There is a problem with using the Microsoft stacks for setting up a
Bluetooth connection to a device that does not require any passkey.

The device use Bluetooth SPP (Serial Port Profile).

When you select the "no passkey" during the discovery process, everything
looks fine but the Microsoft driver comes back and still requires a passkey
after the discovery.

This problem is only with Microsoft and is present on their Bluetooth stack
for all OS (Windows XP, Vista, Tablet PC editions, Windows Mobile 5.0 and
6.0). All other Bluetooth drivers on the market on all Operating Systems work
fine with no passkey.

For Windows Mobile 5 and 6 devices that use the Microsoft stack, there is a
work around: hit "next" the first time it asks for the passkey and entering a
blank space the second time it asks for the passkey. Mobile 6 still gives an
error message at the end, but it works fine once you ignore it. For XP,
Vista... a totally different story. I have tried everything possible on all
sorts of hardware and always the same results. You are forced to enter a
passkey to go further.

I know this issue has been reported many times to Microsoft by some hardware
manufacturers over the last 3 years, but it is only getting worse.

Does anyone have a clue of whatever could be done for a non-secure Bluetooth
connection, using the Microsoft stack, to a Serial Port Profile device that
does not require a passkey? Any idea on a work-around?

Thanks,

John

does a string of zeros work? My cellphone does not ask for a passkey,
but my XP BT does, so I enter "0000" and it works in this instance.

Q