Received Fri, 13 Jun 2008 15:20:12 PHT
Can't connect RFCOMM socket: Connection refused - call_passkey_agent(): no agent registered. How to solve this error
Bluetooth authentication error - PIN exchange NOT working
A common error is Can't connect RFCOMM socket: Connection refused. By default my openSuSE Linux had NO passkey-agent activated. Hence authentication failed. rfcomm.conf does NOT answer the PIN request, the passkey-agent does that job!!
Watch your messages - log during your configuration period to get feedback for your possible trouble shooting:
tail -f /var/log/messages
You'll most likely find errors such as:
call_passkey_agent(): no agent registered
pin_code_request (sba=00:19:7E:EA:90:52, dba=00:1E:3A:7A:AE:66)
call_passkey_agent(): no agent registered
You have NO passkey-agent active in your system. It appears that the rfcomm.conf does NOT solve the PIN request. Start your passkey-agent as below and set the PIN in use ( the same as in your rfcomm.conf ).
/usr/bin/passkey-agent --default 0000Passkey-agent needs to be closed using CTRL C. It appears in my case with correct N95 auto reconnect configuration set ONCE for the initial pairing / connection. I now no longer need the passkey-agent for future connections. That most likely depends on the security features of your Nokia smartphone and whether you allow your smart phone to accept / auto connect upon connection requests from your laptop once you have correctly paired with that laptops HW BT address. Provided that you have always the same laptop connecting to your smartphone - that certainly may be a preferred solution if your Nokia supports auto-reconnect without re-use of PIN after the initial PIN has been entered ONCE.
OR
start / use your bluetooth daemon
/opt/kde3/bin/kbluetoothd
Be aware that kbluetoothd has a POP-UNDER window showing up when a password / PIN is requested upon connection. That may cause a problem if you have OTHER windows covering this POP-UNDER window and you may get error messages due to time out of your PIN request failing!!!
I personally prefer the simple method of using the /usr/bin/passkey-agent --default 0000 and have configured my Nokia N95 smart phone to always auto-connect to my precise laptop when my laptop sends a connection request. You may replace the PIN 0000 by any other PIN of your choice - just be sure you remember it and the PIN also should be included in yourm /etc/bluetooth/rfcomm.conf..
Enjoy
hans
For more help on other Nokia N95 smartphone / bluetooth modem connection problems, please have a look at all my other articles to solve all possible errors and problems.






