This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems with port 8080

ok I currently have a web server running behind the firewall, with a virtual IP on the external Interface...
then I SNAT/DNAT my External Dest. IP to my Internal Dest. Ip

this works great
I have rules allowing port 80, and port 8080
though to both the int/Ext IP for my web server..

port 80 works fine I can hit the machine with an external web browser,

but when I try to use port 8080 it no longer works... any ideas???

This thread was automatically locked due to age.

0 Maurice over 23 years ago

If I understood your problem correctly, you are trying to reach your S/D natted web server on port 8080 unsucessfuly, and obviously you won't be able to unless you will either configure your web server to accept connections on 8080 and at the same time make sure that HTTP proxy on ASL is turned OFF (unless you change the default proxy port of ASL). Otherwise ASL will take over the port automatically.

Just for curiosity, why would you like to connect to the web server on 8080? This port is for proxy use and it might easily conflict with the proxy on ASL, as I assume you are experiencing now.

Maurice
- 0 Knight over 23 years ago in reply to Maurice
  
  in our office we use Jakarta Tomcat application server in conjunction with Apache or IIS, and Jakarta Tomcat's default port is 8080... Our company develops and does some very limited hosting of advanced Mapping applications..
  
  I am using SNAT/DNAT..
  
  I have created an additional IP on the external ..
  let's say
  x.x.x.80/255.255.255.255 = webserver1_EXT
  192.168.10.80/255.255.255.255 = webserver1_INT
  
  SNAT/DNAT
  
  is configured so that all packets destined for webserver1_Ext go to webserver1_INT
  
  and this works fine
  
  I am also spesifically allowing port 80 and port 8080 in my packet filter rules..
  
  port 80 works and 8080 does not...
  
  I have the HTTP Proxy disabled.