Austin, I believe by default 'adbd' listens on port 5555. If you do a 'netstat' on your Android device, you should see: tcp 0 0 0.0.0.0:5555 0.0.0.0:* LISTEN
The command to connect is: adb connect ip:port Let me know how you make out, sws-vinpa. On Jun 12, 3:59 pm, Austin <[email protected]> wrote: > Hi folks, > > My Android (eclispe) development machine is separate from the machine > which my phone is physically connected to (the dev machine is actually > in a Hyper-V virtual machine). > > The ADB helps makes it look like the ADB server can connect over TCP/ > IP to a remote daemon, but I can't quite convince it to startup > correctly. > > On the real machine, I can use "adb devices" to successfully see my > HTC Desire, and other adb commands work locally fine. > > But attempting to turn on TCP listening on the daemon side (with "adb > tcpip 12345") doesn't actually get the adbd on the phone to start > listening ("adb shell netstat -a" doesn't show port 12345 being in > LISTEN state). > > How can I connect to ADB server or daemon remotely? > > Thanks, > Austin -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
