09-24-2012, 09:34 PM
I'm another one having trouble with this. It has worked in the past, but after not using it for a couple of months, I can't now get it to connect.
The PC is running Windows 7 Ultimate 64-bit SP1, and the tablet is an Asus Transformer TF-101 running Android 4.0.3. There is no firewall on the PC (the local network is behind a Netgear NAT wifi router).
I've run Nirsoft's CurrPorts utility to check that the ports the Companion wants aren't already in use. That seems to be OK. It shows the Companion as opening UDP 8888 and TCP 16568, but shows the local address for these as 0.0.0.0, when I would have expected 127.0.0.1. (Having said that, it shows a lot of other processes as opening UDP and TCP ports on 0.0.0.0).
I can't find anything in the router setup related to disabling multicasting. I know it's working fine on wired devices because I've been developing s/w for controlling lighting using UDP.
I have a suggestion that may help with connection problems. If you are only using UDP to identify the PC, perhaps you could put an option into the Android app for the user to enter the PC's IP address, and if that's entered then connect directly to the TCP port (maybe even make the port configurable at both ends, just in case something else is using the one you want).
The PC is running Windows 7 Ultimate 64-bit SP1, and the tablet is an Asus Transformer TF-101 running Android 4.0.3. There is no firewall on the PC (the local network is behind a Netgear NAT wifi router).
I've run Nirsoft's CurrPorts utility to check that the ports the Companion wants aren't already in use. That seems to be OK. It shows the Companion as opening UDP 8888 and TCP 16568, but shows the local address for these as 0.0.0.0, when I would have expected 127.0.0.1. (Having said that, it shows a lot of other processes as opening UDP and TCP ports on 0.0.0.0).
I can't find anything in the router setup related to disabling multicasting. I know it's working fine on wired devices because I've been developing s/w for controlling lighting using UDP.
I have a suggestion that may help with connection problems. If you are only using UDP to identify the PC, perhaps you could put an option into the Android app for the user to enter the PC's IP address, and if that's entered then connect directly to the TCP port (maybe even make the port configurable at both ends, just in case something else is using the one you want).