Nokia Cellular Telephones Do Not Work Properly with Bluetooth Transceiver (811235)


The information in this article applies to:

  • Microsoft Wireless Optical Desktop for Bluetooth
  • Microsoft Optical Desktop Elite for Bluetooth 2.0
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

When you try to use a Nokia cellular telephone with a Bluetooth transceiver, the telephone may not work properly. This issue is not limited to Nokia phones. For example, the Sony au c413s and the Docomo (Sharp) PALDIO 633 may have the same issue and therefore require the resolution that is described later in this article.

CAUSE

The link key exchange is susceptible to "sniffing" (the process of viewing line or connection data by using a sniffing tool or program). If the initial link key exchange is captured, any future connections could be listened to by an outside Bluetooth device. To minimize that risk, devices that a connection will be established to are instructed that link keys will change for every new connection. Some radio manufacturers and vendors misunderstood the specification and changed it so that this change occurred immediately. Because of this immediate change, they disconnected, losing the state of the link key exchange, and therefore not working with the Bluetooth stack. If you use this workaround, be aware that it reduces your security for all bonded connections. However, anyone sniffing your connection must be within approximately 30 feet on a low-power radio, and would have to sniff your first bonding process.

RESOLUTION

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this issue, add the missing registry value. To do so, follow these steps:
  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. In Registry Editor, locate the following registry key (where bus_type is the bus type that is being used by your Bluetooth device (for example, PCI, PCMCIA, or USB):

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\bus_type

  4. Expand each subkey in the bus_typekey to locate the Device Parameters key, which contains the Bluetooth identification number. For example, the key for a device USB might be located in the following key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0c10&Pid_0000\120000AB0AFC\Device Parameters

  5. In the right pane, right-click a blank area, point to New, and then click DWord.
  6. In the Name box, type Change Link Key Always.
  7. In the right pane, right-click Change Link Key Always, and then click Modify.
  8. In the Value box, type 0.
  9. Quit Registry Editor.
  10. Unplug and reinsert your Bluetooth Device for this change to take affect. If your Bluetooth device is embedded, then restart your computer for this change to take affect.
  11. Run the Bluetooth Authentication Wizard to re-authenticate the device.

MORE INFORMATION

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Modification Type:MajorLast Reviewed:9/24/2004
Keywords:kbinfo KB811235
©2004 Microsoft Corporation. All rights reserved.