Re: war app, Tomcat, public IP and port 8080 - remote access

2011-01-31 Thread Amilcar De Leon
thanks for your suggestions guys, sorry for the delay, but after all, it was
a firewall problem, I tried to connect in another location and It wored
fine; the location where I first tried to connect had some kind of firewall
restrictions but I could not configure it.

Thanks!
-- 
Amílcar de León
Think Freely http://www.antigualug.org


Re: war app, Tomcat, public IP and port 8080 - remote access

2011-01-29 Thread Ognjen Blagojevic

On 28.1.2011 23:14, Amilcar De Leon wrote:

So, on my server, if I type, 211.210.19.11:8080/myAPP I can run my app OK.
The same if I try from another computer within the same LAN (connected to
the same router).


Your webapp seems to be working just fine.



When I try to access that same address from another computer out of the LAN
(eg an internet coffee), I get the error connection time out. But if I
only type 211.210.19.11:8080 I can see a page that says I'm sucessfully
installed tomcat and links to the tomcat manager, tomcat documentation and
others.

An extra note, the first page of my app is a login page, and I can see it if
I use the firefox addon calle Go2proxy, but then when I type the login info
I gen again the connection time out error. Not sure if this is useful


What you describe indicates like you have a network problems. Login page 
and Tomcat home are maybe cached, but I cannot say for sure. Try to turn 
off Go2Proxy, and to clear Firefox cache. Then try to browse Tomcat 
examples, or try to login to Tomcat manager application. What happens?


Also probe your Tomcat port directly from command like with:

  telnet 211.210.19.11 8080

What happens? Do you get a blank screen (success) or you get Connect 
failed message?


-Ognjen


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: war app, Tomcat, public IP and port 8080 - remote access

2011-01-29 Thread David Smith
This smells like a router/firewall issue and it only looks like the top 
level page at 211.210.19.11:8080 works.  Some browsers (IE) offer the 
cached copy when it runs into trouble loading a page fresh.  When you do 
get tomcat home page from your server at an internet cafe, try holding 
the shift key and reloading.  This forces most browsers to throw out 
cached versions of pages and redownload.  I'm wiling to bet it fails to 
load.


Oh yes .. and as someone else said, don't use go2 proxy while testing.  
Disable it until you have the problem worked out.


--David

On 01/28/2011 05:14 PM, Amilcar De Leon wrote:

I have my server configured with a static public IP like 211.210.19.11 (this
is not my real one if you ask).

There is another static public IP that came with the routher which is the
same than the above, except for the last numer (eg 211.210.19.10). I'm
giving this as I don't know if you'd need this info too.

So, on my server, if I type, 211.210.19.11:8080/myAPP I can run my app OK.
The same if I try from another computer within the same LAN (connected to
the same router).

When I try to access that same address from another computer out of the LAN
(eg an internet coffee), I get the error connection time out. But if I
only type 211.210.19.11:8080 I can see a page that says I'm sucessfully
installed tomcat and links to the tomcat manager, tomcat documentation and
others.

An extra note, the first page of my app is a login page, and I can see it if
I use the firefox addon calle Go2proxy, but then when I type the login info
I gen again the connection time out error. Not sure if this is useful



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



RE: war app, Tomcat, public IP and port 8080 - remote access

2011-01-28 Thread Caldarale, Charles R
 From: Amilcar De Leon [mailto:ada...@antigualug.org] 
 Subject: war app, Tomcat, public IP and port 8080 - remote access

 I have recently gotten a Public IP (eg 10.10.1.38)

There's either a misconception or a terminology problem here: 10.x.x.x is *not* 
a public IP address; rather, it's one of the three ranges specifically reserved 
as /private/ IP addresses.

 the problem comes when I try to access it from outside

What does outside mean in this context?

 when follow to type :8080/myAPP I don't have any luck;

I don't recall any Tomcat or browser error message saying you have no luck; 
what _exactly_ happens?

 but again when I try to go to the manager
 page - for instance -, I have no luck.

There's that no luck HTTP status again; I don't recall ever seeing that in 
the RFCs.  Also, exactly what URL are you trying?  There's no Tomcat URL that 
includes the phrase manager page; be precise.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: war app, Tomcat, public IP and port 8080 - remote access

2011-01-28 Thread Amilcar De Leon
I have my server configured with a static public IP like 211.210.19.11 (this
is not my real one if you ask).

There is another static public IP that came with the routher which is the
same than the above, except for the last numer (eg 211.210.19.10). I'm
giving this as I don't know if you'd need this info too.

So, on my server, if I type, 211.210.19.11:8080/myAPP I can run my app OK.
The same if I try from another computer within the same LAN (connected to
the same router).

When I try to access that same address from another computer out of the LAN
(eg an internet coffee), I get the error connection time out. But if I
only type 211.210.19.11:8080 I can see a page that says I'm sucessfully
installed tomcat and links to the tomcat manager, tomcat documentation and
others.

An extra note, the first page of my app is a login page, and I can see it if
I use the firefox addon calle Go2proxy, but then when I type the login info
I gen again the connection time out error. Not sure if this is useful
-- 
Amílcar de León
Think Freely http://www.antigualug.org