Cannot pair with foobar

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Click 'pair with new device' in foobar
2. Manual add using IP of foobar PC
3. Pairing screen comes up in foobar, add 5309 as pin
3. Android appears in foobar list of remotes
4. Tunesremote+ pairing with library screen disappears, then reappears and does 
not connect to library

What is the expected output? What do you see instead?
Expected to connect to library, works OK with Itunes, not with foobar

What version of the product are you using? On what operating system?
Tunesremote+ 2.04, Foobar v1 and foo_touchremote on windows 7

Please provide any additional information below.

Original issue reported on code.google.com by benmad...@gmail.com on 31 Oct 2010 at 6:01

[GoogleCodeExporter]

I thought I would ass, I have now repeated the setup with songbird and 
mediamonkey and they both have the same issue.

Original comment by benmad...@gmail.com on 31 Oct 2010 at 6:49

[GoogleCodeExporter]

OK if you tried all 3 apps and they did not work it means your Firewall is 
blocking the communication.   You should NEVER need to do the Manual Pairing.  

Try temporarily disabling your Windows Firewall and trying again.

Also when connecting to iTunes it is Manual Pairing:

IP: <your pc ip address>
PIN: 0000000000000001   (15 0's followed by a 1)

Trust me.  Please report your progress back here!

Original comment by mellowaredev on 31 Oct 2010 at 8:50

• Changed state: Accepted

[GoogleCodeExporter]

Hi there, thanks for your suggestion. Itunes already worked with manual 
pairing, as I installed it to test and it works fine using the above method 
(firewall is still on).

However unfortunately foobar (my standard media player) does not work even when 
windows firewall is disabled. An android device name shows up as paired in 
foobar, however on the phone the  pairing with library dialogue pops up again, 
or remains on the screen.

Original comment by benmad...@gmail.com on 31 Oct 2010 at 10:26

[GoogleCodeExporter]

I have also confirmed that the foobar plugin is functional, as it works with 
the remote app on an ipod touch I also have.

Original comment by benmad...@gmail.com on 31 Oct 2010 at 10:32

[GoogleCodeExporter]

OK if you installed my MonkeyTunes plugin do Manual Pairing and use the Pin 
Code = "1" and exactly "1".  It is a secret key into MonkeyTunes.

Let me know if that works?

http://code.google.com/p/tunesremote-plus/wiki/MonkeyTunesInstructions

Original comment by mellowaredev on 31 Oct 2010 at 10:54

[GoogleCodeExporter]

Thanks for your help. Unfortunately trying this did not work, it has the same 
issue as foobar - an android remote shows up in the menu but the phone doesn't 
access the library.

Original comment by benmad...@gmail.com on 1 Nov 2010 at 8:04

[GoogleCodeExporter]

Then I am absolutely POSITIVE your PC is blocking HTTP Port 3689 and possible 
port 1024.   Because I test MonkeyTunes extensively and the only way the Pin 
Code = "1" doesn't work is if your Firewall is blocking traffic.

My guess is Itunes creates a "TCP Tunnel" legally through the firewall that 
MonkeyTunes and Foobar are not doing.

Trust me, it is virus, spyware, firewall software or hardware blocking the 
communication back to your Android.

Original comment by mellowaredev on 1 Nov 2010 at 10:37

[GoogleCodeExporter]

Also another thing I thought of.  were you running Itunes at the same time as 
Foobar or MonkeyTunes?  because only one application can have Port 3689 at a 
time so if you had iTunes running then MediaMonkey or Foobar will not work util 
you shut it down.  Only try running one app at a time and see if it works.

Original comment by mellowaredev on 1 Nov 2010 at 11:34

[GoogleCodeExporter]

Hi there, thanks for the additional suggestions. I had only foobar open at the 
time.

I do not think it is likely to be the firewall, as I tested with it disabled. 
Additionally the remote app on my itouch works fine with foobar, suggesting 
that transmissions do get through.

I believe when i tried it with monkeytunes I looked at the log and it said the 
connection was declined by the android phone's IP (I have uninstalled 
mediamonkey, but can reinstall to confirm this if needed). Again, the phone 
shows up in the software (foobar, monkeytunes) but the library does not connect 
on the phone.

Thanks once again for your help.

Original comment by benmad...@gmail.com on 1 Nov 2010 at 8:13

[GoogleCodeExporter]

So what I think the problem was if you have Foobar open the bonjour part will 
recognize your Android and it shows up in the tree node but since Port 3689 was 
already in use it can't actually do the communication.

Please try again with NO other apps running and Manual Pairing with Pin Code 
"1".  If it works then we know it was because foobar or Itunes had Port 3689 
locked up.  I will then mark this ticket Invalid,

Original comment by mellowaredev on 1 Nov 2010 at 8:31

[GoogleCodeExporter]

Ideally I would like to work with foobar as that is my standard media player.

I just tried with only monkeytunes open and only tunesremote+ running on the 
phone, using the method above. The same problem remains, the Android phone 
appears in Monkeytunes, but tunesremote stays stuck at pairing with library.

The log file from when I try to connect shows this:-
2010-11-01 21:42:49,298 [ERROR] - (1) - Error On Node Focused
System.Collections.Generic.KeyNotFoundException: The given key was not present 
in the dictionary.
   at System.ThrowHelper.ThrowKeyNotFoundException()
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Melloware.MonkeyTunes.MonkeyTunesServer.DnghiupD7(SDBTreeNode )
2010-11-01 21:43:01,921 [INFO ] - (9) - NetServiceBrowser_DidFindService: 
8501fb58b875d93ca61e8145d8f739ff51da45c8
2010-11-01 21:43:02,865 [INFO ] - (10) - NetServiceBrowser DidResolveService: 
8501fb58b875d93ca61e8145d8f739ff51da45c8
2010-11-01 21:43:02,877 [INFO ] - (10) - OnClientListChanged: New DACP Clients 
discovered...
2010-11-01 21:43:08,464 [INFO ] - (1) - Attempting to Pair Service: 
8501fb58b875d93ca61e8145d8f739ff51da45c8
2010-11-01 21:43:10,552 [ERROR] - (1) - No Response from Pairing!!!
2010-11-01 21:43:10,554 [ERROR] - (1) - HTTP GET Error
Melloware.DACP.DACPPairingException: Unable to complete pairing ---> 
System.Net.WebException: Unable to connect to the remote server ---> 
System.Net.Sockets.SocketException: No connection could be made because the 
target machine actively refused it 127.0.0.1:1024
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
   at System.Net.WebClient.DownloadData(Uri address)
   at System.Net.WebClient.DownloadData(String address)
   at Melloware.DACP.DACPPairingServer.NEZLMMZVbcxvmXqnNDd(Object , Object )
   at Melloware.DACP.DACPPairingServer.PairService(NetService service, String passCode)
   --- End of inner exception stack trace ---
   at Melloware.DACP.DACPPairingServer.PairService(NetService service, String passCode)

Original comment by benmad...@gmail.com on 1 Nov 2010 at 9:49

[GoogleCodeExporter]

Gotcha.  You might want to contact the FooTouchRemote developer specifically 
but as for your error above...

http://social.msdn.microsoft.com/Forums/en-US/netfxnetcom/thread/29a8831a-6251-4
7e5-90a3-dfe4c87ff20e/

It looks like .NET uses the default IE Proxying mechanism when making the call 
Back to the Android device.  Do you have Proxy settings set up in IE for any 
reason?

Original comment by mellowaredev on 1 Nov 2010 at 9:58

[GoogleCodeExporter]

Thanks, I will try the footouch developer as well.

I don't have any proxy set up in IE. Seems like a very odd problem! Strange 
that tunesremote+ pairs fine with itunes, but not mediamonkey, foobar or 
songbird!

I tried again in monkeytunes. complete fresh start, same issue occurs where the 
phone appears in moneytunes but in tunesremote+ it goes straight back to the 
pairing popup. Details below again

2010-11-01 21:54:49,182 [ERROR] - (1) - Error On Node Focused
System.Collections.Generic.KeyNotFoundException: The given key was not present 
in the dictionary.
   at System.ThrowHelper.ThrowKeyNotFoundException()
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Melloware.MonkeyTunes.MonkeyTunesServer.DnghiupD7(SDBTreeNode )
2010-11-01 21:54:49,437 [INFO ] - (9) - NetServiceBrowser_DidFindService: 
5371474054c328c9bcb788f096462a3ef9f64d40
2010-11-01 21:54:50,157 [INFO ] - (11) - NetServiceBrowser DidResolveService: 
5371474054c328c9bcb788f096462a3ef9f64d40
2010-11-01 21:54:50,169 [INFO ] - (11) - OnClientListChanged: New DACP Clients 
discovered...
2010-11-01 21:55:05,545 [INFO ] - (1) - Attempting to Pair Service: 
5371474054c328c9bcb788f096462a3ef9f64d40
2010-11-01 21:55:17,045 [INFO ] - (9) - NetServiceBrowser_DidRemoveService: 
5371474054c328c9bcb788f096462a3ef9f64d40
2010-11-01 21:55:17,048 [INFO ] - (9) - OnClientListChanged: New DACP Clients 
discovered...
2010-11-01 21:55:17,796 [INFO ] - (9) - NetServiceBrowser_DidFindService: 
e822454d3c1e597fcab2487bc42e5fdc753fd830
2010-11-01 21:55:17,813 [INFO ] - (7) - NetServiceBrowser DidResolveService: 
e822454d3c1e597fcab2487bc42e5fdc753fd830
2010-11-01 21:55:17,813 [INFO ] - (7) - OnClientListChanged: New DACP Clients 
discovered...

Original comment by benmad...@gmail.com on 1 Nov 2010 at 10:13

[GoogleCodeExporter]

Is this issue with Manual Pairing and Pin = "1"?  That should bypass everythign 
else and just work.

Original comment by mellowaredev on 1 Nov 2010 at 10:18

[GoogleCodeExporter]

Yes, this was using manual pairing and pin = 1

No libraries are found automatically in the tuneremote+ software (not itunes, 
foobar, or mediamonkey), I have to manually put in the IP to get the pairing 
password screen up (the 5039). Perhaps it is a hardware firewall issue with my 
router?

Original comment by benmad...@gmail.com on 1 Nov 2010 at 10:25

[GoogleCodeExporter]

I think it might be.  Because Bonjour UDP 5353 is not even discovering services 
on your network that is very bad.  You can tell for sure if you download a free 
app from Android Market called "ZeroConf Browser" that I wrote.  That shows you 
every Bonjour discoverable service your Android phone can see.  If that app 
comes up blank then you know there is something seriously whacky going on your 
network!

Original comment by mellowaredev on 1 Nov 2010 at 10:34

[GoogleCodeExporter]

Thanks very much for your help. I will try using this app tomorrow after work.

Original comment by benmad...@gmail.com on 1 Nov 2010 at 10:37

[GoogleCodeExporter]

Actually just tested app now - it does indeed come up blank! Itunes still pairs 
with tunesremote+ fine using manual connect, shame it is not a good media 
player and can't play flac!

Any idea what might be stopping bonjour being discoverable? My router is a 
standard thomson provided by my ISP, nothing odd set up on it and the PC is 
using windows firewall. Disabling that didn't help either!

Original comment by benmad...@gmail.com on 1 Nov 2010 at 10:45

[GoogleCodeExporter]

Actually just tested app now - it does indeed come up blank! Itunes still pairs 
with tunesremote+ fine using manual connect, shame it is not a good media 
player and can't play flac!

Any idea what might be stopping bonjour being discoverable? My router is a 
standard thomson provided by my ISP, nothing odd set up on it and the PC is 
using windows firewall. Disabling that didn't help either!

Original comment by benmad...@gmail.com on 1 Nov 2010 at 10:45

[GoogleCodeExporter]

Well at least now you know the problem is your network is not allowing UDP 
Multicast Packets on Port 5353.  I think this might be at the heart of all your 
troubles.

As to how and why, that is unique per network "jungle".  I wouldn't even begin 
to know how to diagnose it.  But at least we know now why you are having so 
much trouble.

Original comment by mellowaredev on 1 Nov 2010 at 10:47

[GoogleCodeExporter]

I am going to mark this defect as INVALID since this really isn't a 
TunesRemote+ issue it is a home networking issue.

Original comment by mellowaredev on 1 Nov 2010 at 10:48

• Changed state: Invalid

[GoogleCodeExporter]

thanks for your help anyway!

Original comment by benmad...@gmail.com on 2 Nov 2010 at 6:50