From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Can't connect RFCOMM socket
Date: Wed, 19 Jan 2005 21:38:17 +0100 [thread overview]
Message-ID: <1106167097.8190.133.camel@pegasus> (raw)
In-Reply-To: <csm972$gnu$1@sea.gmane.org>
Hi,
> First of all thanks again for your time, maybe this is another proof of
> my lack of basic knowledge, but I've trying a lot and can't get ride of
> this error (I know this error is in many mails arround the list, but I
> have not find the particular remedy for mine)
>
> When I try:
>
> rfcomm connect rfcomm0 00:10:60:A5:8F:8A 5
>
> I get:
>
> Can't connect RFCOMM socket: Connection refused
the dump shows that there is no service running on RFCOMM channel on the
other side.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-19 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 18:33 [Bluez-users] Can't connect RFCOMM socket soraberri
2005-01-19 20:38 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-28 19:19 [Bluez-users] Can't connect RFCOMM socket: resource temporarily unavailable Marcel Holtmann
2005-01-31 16:36 ` [Bluez-users] Can't connect RFCOMM socket Filipa Duarte
2005-01-31 17:07 ` Marcel Holtmann
2008-03-19 6:45 Matt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1106167097.8190.133.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.