Foo touch remote not connecting

[GoogleCodeExporter]

Q. What Android hardware device do you own?  (HTC Hero, Samsung Galaxy,
etc)

A: Gooogle Nexus 7

Q. What TunesRemote+ version? (found on Menu->More->About)

A:

I just download this app from the market, and footouch remote for foobar.

Your app launches and shows foobar, but when I click it says connection 
refused. When i go to foo touch remote in foobar to pair it, it just says 
searching.

Im unsure what to do, or how to pair the devices if needed.

Original issue reported on code.google.com by GhostM...@gmail.com on 10 Aug 2012 at 12:25

[GoogleCodeExporter]

Also no firewall equipment is going either.

Original comment by GhostM...@gmail.com on 10 Aug 2012 at 12:38

[GoogleCodeExporter]

I also have your 3 suggested ports forwarded, and the foobar plugin 
footouchremote is working on my iphone with apples remote software. I cannot 
get your software to connect to it on android when click on my foobar server in 
your software, constantly just says refused, it is showing foobar my ip address 
and a bunch of letters behind it, but wont let me connect.

Original comment by GhostM...@gmail.com on 11 Aug 2012 at 12:31

[GoogleCodeExporter]

It is a bug in FooTouchRemote.  I would report it to the FooTouch developer.  
It has been reported to him before.  TR+ has been tested with other DACP 
servers such as iTunes, MonkeyTunes, AlbumPlayer with no issues.

Original comment by mellowaredev on 11 Aug 2012 at 2:42

[GoogleCodeExporter]

Original comment by mellowaredev on 11 Aug 2012 at 2:42

[GoogleCodeExporter]

I think, OP might start with checking TouchRemote FAQ.

Q: Ok, I’ve paired with my device (it appeared in the list of paired 
devices), but client couldn’t connect to foobar2000.
A: Most likely your firewall doesn’t allow incoming connections on port 
specified in settings (7000 by default).
Also, if you’re running Android with Hyperfine or TunesRemote+ client 
application, you should set port to 3689, ’cause those clients currently 
don’t support custom ports announced via Bonjour.

Original comment by PieceOfS...@gmail.com on 2 Sep 2012 at 1:58

[GoogleCodeExporter]

I dont have any firewall going. It is completely disabled when attempting this.

I will try to forward the last recommended port.

Original comment by GhostM...@gmail.com on 2 Sep 2012 at 7:40

[GoogleCodeExporter]

PiecesOfSummer how is the port announce in Bonjour?  I can fix TR+ to read the 
port out of there I just have never seen the port announced in a Bonjour field 
from iTunes?

Original comment by mellowaredev on 2 Sep 2012 at 1:27

[GoogleCodeExporter]

mellowaredev,
when you register your service with DNSServiceRegister, you pass host (or null 
for current machine) AND port number where your service is located.

later, when your client lookups for service, it typically uses DNSServiceBrowse 
to list services of specific type and DNSServiceResolve to get host name and 
TXT record for each service. And as well as host name, there's port parameter 
in ResolveCallback which tells where service is registered.

Note that port parameter is always in network byte order, so you need to 
convert it from the host byte order both in DNSServiceRegister call and in 
ResolveCallback.

Original comment by PieceOfS...@gmail.com on 2 Sep 2012 at 3:57

[GoogleCodeExporter]

You are right, looking through the code the original developer has 3689 hard 
coded in a couple of places and didn't pass it through when storing previously 
connected libraries, he only stored the ipaddress not the port as well.   I am 
leaving this ticket open since the real problem is that TR+ assumes that port 
3689 is the only one.

Original comment by mellowaredev on 3 Sep 2012 at 2:54

• Changed state: Accepted