Hi,
Any chance you have succeeded with another port than port 80 ?
We are also receiving report from user not able to reach our server
running on port 8080 from their mobile network, is there any
(recommended) list of server port that can be use ?
thanks
On Mar 20, 11:17 am, Samsyn wrote:
> O
On Mar 18, 8:11 pm, Samsyn wrote:
> OK, some success, as it were.
>
> Let the wookiie win
>
OK OK, apparently I just picked the world's worst port number ()
and was SO SURE that was an innocent number that I didn't even try any
others. Well, is apparently blocked by verizon/android (loo
OK, some success, as it were.
Let the wookiie win
--
I changed my server to listen on port 80 instead and now it works fine
in both WIFI and MOBILE modes.
* server ping is now 800ms instead of 100ms
* I can not, of course, run a web server on the same machine now,
which is a small pain.
But he
Sadly, no joy. I get the same behaviour trying to connect to three
different non-port-80 servers.
Recapping
* using Socket, TCP connection, originated by phone
* Have the "INTERNET" privilege
code section:
[code]
try {
mServerSocket = new Socket( );
Thanks for the suggestion Michael, I'll give that a try.
I went through some abortive experiments with
requestHostForConnection() (man that turned out to be a major pain)
and that bore no fruit (so I was happy to tear it out).
There is also a connect through proxy option which might bear fruit.
B
On 03/14/10 21:03, Samsyn wrote:
> I wonder if this could be a Verizon thing. What strikes me as odd is
> that the UrlConnection works fine, and that must also be using tcp, so
> is fundamentally the same as my subsequent Socket connection, which
> fails.
>
> The differences are:
>
> * different s
I wonder if this could be a Verizon thing. What strikes me as odd is
that the UrlConnection works fine, and that must also be using tcp, so
is fundamentally the same as my subsequent Socket connection, which
fails.
The differences are:
* different server.. .MAYBE my server doesn't like the 3gs '
7 matches
Mail list logo
