Phone cannot access mobile web app...why?

[lnong]

I built an ASP.NET mobile web application last year for fun and hosted it on my home server. I was successful in accessing it with my Sprint phone, which uses the "Obigo 1.1.4 WAP 2.0" browser. Now, I'm with Verizon and my current phone also uses an Openwave WAP 2.0 browser, but I cannot access my mobile web site. When I punch in the URL, it hangs for long time, then it gives me the error "Error: Request timed out".

I asked a friend who is with AT&T to try it on his cell phone, and it works. So, my app is working. I dont know if it's a problem with my new phone's browser software (do I need to upgrade it?), or with the Verizon service (maybe they block something on their network).

Another concern is that my home internet service provider blocks port 80 on our network. So i had to use another port, like 81. So to access my web app, the URL would be something like http://myapp.mydomain.com:81. Could it be that my phone's browser does not recognize this non-default port?

Any ideas? Anyone with Verizon that is able to successful access .NET mobile web apps?

[griff777]

I built an ASP.NET mobile web application last year for fun and hosted it on my home server. I was successful in accessing it with my Sprint phone, which uses the "Obigo 1.1.4 WAP 2.0" browser. Now, I'm with Verizon and my current phone also uses an Openwave WAP 2.0 browser, but I cannot access my mobile web site. When I punch in the URL, it hangs for long time, then it gives me the error "Error: Request timed out".

I asked a friend who is with AT&T to try it on his cell phone, and it works. So, my app is working. I dont know if it's a problem with my new phone's browser software (do I need to upgrade it?), or with the Verizon service (maybe they block something on their network).

Another concern is that my home internet service provider blocks port 80 on our network. So i had to use another port, like 81. So to access my web app, the URL would be something like http://myapp.mydomain.com:81. Could it be that my phone's browser does not recognize this non-default port?

Any ideas? Anyone with Verizon that is able to successful access .NET mobile web apps?

Maybe try port forwarding on no-ip.com or similar service.

the user would type in the domain such as http://somedomain.no-ip.com, and this would get port forwarded (as this is a port 80 request) to a different port, IE: 124.456.789.124:81

Although it is not optimal, it does work...

Hope that helps.

[PeOfEo]

I built an ASP.NET mobile web application last year for fun and hosted it on my home server. I was successful in accessing it with my Sprint phone, which uses the "Obigo 1.1.4 WAP 2.0" browser. Now, I'm with Verizon and my current phone also uses an Openwave WAP 2.0 browser, but I cannot access my mobile web site. When I punch in the URL, it hangs for long time, then it gives me the error "Error: Request timed out".

I asked a friend who is with AT&T to try it on his cell phone, and it works. So, my app is working. I dont know if it's a problem with my new phone's browser software (do I need to upgrade it?), or with the Verizon service (maybe they block something on their network).

Another concern is that my home internet service provider blocks port 80 on our network. So i had to use another port, like 81. So to access my web app, the URL would be something like http://myapp.mydomain.com:81. Could it be that my phone's browser does not recognize this non-default port?

Any ideas? Anyone with Verizon that is able to successful access .NET mobile web apps?
Sounds like a verizon network issue. You might need to call their support and ask them how come you can't get at the page, it might be an account problem. You might try doing it with someone elses phone who has verizon too.