The solution is to use the Microsoft Driver instead of the Widcomm driver. There is a conflict between the widcomm tools coming with the widcomm driver and PC Suite. I experienced recently the same problem on my labtop with a Belkin bluetooth key.įinally, I found the solution on the web at this forum I'm wondering if there can be some compatibility problem with Widcomm drivers 5.

When I click 'Next', it hangs for a while and then answers 'Cannot authenticate the phone'.Įverything works fine on another PC with same OS and PC Suite version, but different BlueTooth software. When I try 'Make new connection', PC suite finds the phone (E51) and recognises it is paired, but claims 'Phone needs to be authorised'.

Phone is correctly paired, I can see that in 'My BT places', but PC suite does not see it. I haven't checked yet whether or not it has to do with whether the laptop has gone into hibernation in the meantime or not. In the previous version, once the phone had been paired I could switch off bluetooth discoverability and it would just continue to work. EVEN after it has been paired with both laptop and PC Suite. What I have noticed is that the phone (6120 for me) MUST have Bluetooth visibility switched on 'Shown to All' in order for the new version of PC Suite to see it.

However, my laptop is an older Dell running WIDCOMM drivers version 3.0.1.804. I too recently upgraded to PC Suite 7.0.8.2 on Win Xp SP2. I believe the below to have more to do with the latest incarnation of PC Suite.

Widcomm bluetooth software 6.0.1.4900