Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: sam russo on July 10, 2002, 05:03:35 AM
-
I'm not sure what I'm doing wrong. I've read most of the posted port forwarding qns and I'm still unable to get my port forwarding to work.
Here's my situation
1. I've installed the http://myezserver.com/downloads/mitel/contrib/portforwarding-0.0.1/ in my e-smith 4.1.2 box and its come up in the console.
2. This 4.1.2 Box is a Server-Gateway with a registered domain www.mydomain.com
3. The ppp connection has a "real" ip address , the ethernet card has an internal IP (192.168.1.1)
4. I wish to port forward another internal 4.1.2 box ( on the inside with an IP 192.128.1.30) to the web on a port. Say port 4001
So I set port forwarding such that:
Protocol is TCP
External Port Number is 4001
Dest. IP is 192.168.1.30
Dest Port Num is 80
I then goto the web and do a http://www.mydomain.com:4001 and nothing happens.
I'd like to know how to troubleshoot this problem.
Note: Although the 192.168.1.30 e-smith box is inside its gateway is not the 192.168.1.1 e-smith box its another machine on the LAN (192.168.1.150)
Any help would be appreciated.
sam russo
sam@duval.nsw.edu.au
-
Are you trying to connect from inside the E-Smith Firewall LAN? I don't think it forwards from the interal NIC back to the internal network, though I could be wrong.
-
No, Just from outside on the internet
-
start with checking if web server inside IS running. try to connect to it from inside by ip (192.168.1.30) and then, if it works, from outside http://your.public.ip:4001.
After you get this working, make sure that your internal server responds to virtual domain www.mydomain.com as well.
-
Boris I'm not sure what you mean on all parts:
> start with checking if web server inside IS running. try to
> connect to it from inside by ip (192.168.1.30)
This definetly works. When I do a http://192.168.1.30 (or for that matter a http://192.168.1.30:80) on the inside it comes up correctly.
> and then, if
> it works, from outside http://your.public.ip:4001
This did not work ie I did a http://:4001 and the connection timed out. ( a http:// by itself obviously brings up the 192.168.1.1 machine OK)
> After you get this working, make sure that your internal
> server responds to virtual domain www.mydomain.com as well.
I don't understand this part?
-
It doesn't really help anything, but it sounds like you're doing everything right, if that's any consolation.
You said you are able to access the LAN PC's webserver directly via its IP. And you are able to access the 192.168.1.1 e-smith itself from the internet? That should be all there is to it. Tell the e-smith what port to listen on, and which IP:port to forward that to. Make the connection to that port, and it should get passed on to the LAN PC...
-
I have mine set up the same way you described and it works fine. The only difference is the verison of E-Smith you are using. I have been suing port forwarding since version 5, but never used it on earlier versions. Maybe you should try upgrading to a later version. Also, I know this shouldn't matter, but have you tried forwarding different ports? Maybe the one you have chosen is creating a problem. Longshot, but worth a try.
-
If you don't really care about the port number, you can use this ProxyPass contrib to forward a specific Virtual Domain or a directory to an internal server.
http://myezserver.com/downloads/mitel/contrib/ProxyPass/
I have 4 different Virtual Domains all pointing to 4 different internal IIS web servers.