Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I would like access to my local tomcat admin from the external ip address.

By doing http://192.168.1.4:8080/ (internal ip) request it works perfectly ( i see tomcat)

By doing http://127.0.0.1:8080/(internal ip) it works

By doing http://151.48.112.116:80 (external ip address) it works and goes on the Router administration

By doing http://151.48.112.116:8080 i get 404

i did the port forwarding on the 192.168.1.4 address

Screenshots of the router settings:

enter image description here

enter image description here

share|improve this question

migrated from serverfault.com Jan 5 '13 at 21:58

This question came from our site for professional system and network administrators.

    
screenshots show an xbox, so I guess this question is "home related" –  befree42 Jan 5 '13 at 20:20
    
yes home related –  frank Jan 5 '13 at 20:40
    
why you put -1 damn what is the problem with my question ? –  frank Jan 5 '13 at 20:41
    
Your question is good but should not be asked on this website : I downvoted because the question is home related : serverfault.com/faq "and it is not about… Anything in a home setting" –  befree42 Jan 5 '13 at 20:43
1  
I do not think that saying "my home is a office too" qualifies. The problem is with the setting and with the equipment. This is a site for professional server and network administrators and the scope of the site fits very badly with home gear such as this one from netgear. –  ItsGC Jan 5 '13 at 21:01

2 Answers 2

up vote 1 down vote accepted

This is router specific you are in a dual NAT situation:

Excerpt stolen from here

This problem occurs when machines on an internal LAN try to access a server (let's say a web server) that is actually located on the same LAN and NAT'ed through the firewall for external access. If internal users access it by its external NATted address, then they send their TCP packets through the firewall, which translates them and sends them to the server on LAN. The server, however, replies back to the clients directly because they are on the same network. Since the reply has server's real address in the source, clients do not recognize it and the connection cannot be established.

We would need to know router models to see if you can get round this. Since it's a home router there may be no way around it.

share|improve this answer
    
right answer .... –  frank Jan 5 '13 at 21:04
    
you are sure there is no way to round this ?? please –  frank Jan 5 '13 at 21:04
    
mine is D-link DSL-2740B –  frank Jan 5 '13 at 21:06
    
Just RTFM an no there is no way around it. It's no biggie though just use the internal IP inside and external IP outside, –  Shutupsquare Jan 5 '13 at 21:16
    
there may not be on a locked down firmware such as this on linux, but on general purpose Linux and on IOS and JunOS you can fix this with nat. A way that may work with this particular platform is split DNS. Setup an internal dns that catches a call for a public dns domain and direct it to your internal ip. People from outside would use the "real" dns record of the domain, pointing to the public ip of the router. –  ItsGC Jan 6 '13 at 13:07

Try http://151.48.112.116:8008 or changing the External Port to 8080. Is that a typo?

share|improve this answer
    
i did 151.48.112.116:8008 but dose not works as i said .. –  frank Jan 5 '13 at 20:40
    
Port 8080 isn't a typo, it is a commonly used substitute port especially on systems hosted by consumer ISP's preventing homeowners from becoming low bandwidth ecommerce sites for $40 home user rates. But it is so commonly used that intruders hunt for it to when scarfing for web servers especially if they know that ISP on that address block filters 80. Sprint Mobile broadband is a good example, they filter HTTP/HTTPS but allow the HTTP protocol on high ports instead of just filtering inbound HTTP as a protocol on any port. Meaning a guy can host a web server from a moving car. –  SmirksWhileWalkingWCabaretGirl Jan 5 '13 at 20:49
    
explain it please i don't get what to do.... –  frank Jan 5 '13 at 20:53
    
On the screenshot 8008 is a typo .. yes. –  frank Jan 5 '13 at 20:57
    
uploaded new screenshot –  frank Jan 5 '13 at 21:02

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.