Bluetooth: Can't connect L2CAP socket: Connection refused
Hello, my problem has been widely discussed however it seems there is not sustainable solution to it. I have installed Suse 10.0 and applied all the current auto updates to it: In a nutshell the problem is that my AVM Fritz USB Bluetooth cannot connect to the dongle hooked up to the S0 bus (no fancy access point, just a non-configurable dongle with a hard coded PIN). Using the ciptool I get the following error: linux:~ # ciptool scan Searching ... Checking service for 00:01:02:03:04:05 Connecting to device 00:01:02:03:04:05 Can't connect L2CAP socket: Connection refused The well known pin file is created and contains the password string imprinted on the dongle. At this point I am having my first eye brown raise: How come, that there is only one entry expected in that pin file. I would imagine some kind of table that has one pin per device. How would this system work if I had, let's say, two access points: With the current architecture I could only connect to one of them ? This problem is bugging me for quite some time now and there is no light at the end of the tunnel. Any help from your side is highly appreciated. Jochen ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
participants (1)
-
Jochen