As I mentioned in the original post, I need to use the numeric address. In any case, this is not a name lookup issue. The port is definitely open (verified with netstat), and the behaviour is consistent: WiFi on, connection succeeds; WiFi off, connection refused. I have tested switching the WiFi on and off without restarting the server, and it's the same thing every time. In other words, it's not related to the opening of the socket either; it's purely a runtime issue which is why I'm thinking routing.
I can ping 127.0.0.1 from the device without WiFi connectivity, so ICMP is getting through - but TCP is not. My next step will be to write my own client too, in order to eliminate the browser itself as the cause. Cheers, /Uffe -- 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
