Web Server behind a NAT Router?

**bugnote** · 13th March 2003

I'm trying to run a basic apache server on my computer.
Apache is running and working, localhost etc
Router port forwarding is on, port 80 forward to my allocated ip 192.168.0.2

but I can't access the computer from over the internet using my dynamic IP given by the ISP.

any thougths.....I've tried with norton firewall disabled aswell, so t's not that.

cheers

Bug

**SpArKy** · 13th March 2003

i have a similar problem with port forwarding using several port forwarding apps, eg ip_relay

It allows ssh connections using the static external ip address
however when connecting to ftp it connects but then fails opening the utp port on destination.

Cant figure it out at all, this is the current setup

Internet --> winxp box --> rh8.0 server

I have managed to setup a port forwarder on port 22 for ssh connections with an app called ip_relay available at download.com
To enable this forwarder i just used this command:

ip_relay 3000 192.168.0.122 22

where 3000 is port running on winxp box
192.168.0.122 is the linux box ip
and 22 is destination port on linux box

The above works fine however i now want/need another forwarder to forward incoming connections from say port 8000 on winxp box (using internet link ip address [static]) to port 4000 on the linux box which is port for an ftp server.
I tried using the following without success

ip_relay 8000 192.168.0.122 4000

It connects to the linux box as flashfxp says that its conncected but then it just hangs and eventually times out. Also ip_relay then displays the following msg.
"Unable to connect UDP port" (or words to that effect)

Was wondering if any1 ever came across this or any ideas why it might happen, btw running glftpd server on the linux box.
And i also know it would be "better" to run the linux box as the first on the link but for personal reasons its not possible.

Any help with this topic much appreciated.
l8rZ SpArKy

P.S i would of made a new topic but it seems to relate to the original post made.

**merlinL14** · 13th March 2003

The ip range 192.xx.xx.xx and 10.xx.xx.xx is not a recognised ip for internet connection. This range is reserved for LAN (local) operation, most isp's and i-servers will when presented with this ip range attempt to transport it over the internal LAN system that it sits on where it will get blocked and therefor it will not get broadcast over the internet.

**Pegasus** · 13th March 2003

Originally posted by merlinL14
The ip range 192.xx.xx.xx and 10.xx.xx.xx is not a recognised ip for internet connection. This range is reserved for LAN (local) operation, most isp's and i-servers will when presented with this ip range attempt to transport it over the internal LAN system that it sits on where it will get blocked and therefor it will not get broadcast over the internet.

That's why routers have port forwarding (a.k.a NAT).

**merlinL14** · 13th March 2003

That's why routers have port forwarding (a.k.a NAT).

No shit sherlock!

My reply was to try to explain a reason as to why the ip he has selected will not transport, not to try and be a smart arse. And any NAT transport will not work with 192.xx.xx.xx or 10.xx.xx.xx it will allocate a new ip, which is the one he should use for remote access.

**bugnote** · 13th March 2003

so wht should I do then?
if port forwarding to port 80 on 192.168.0.2 that has the server running on it doesn';t work?
ntl dont block port 80 do they?
I'mnow seriously confused...

cheers

Bug

**Pegasus** · 13th March 2003

Originally posted by merlinL14
No shit sherlock!

Obviously politeness isn't one of your stronger points, so just for you I will drag myself down to your level.

And any NAT transport will not work with 192.xx.xx.xx or 10.xx.xx.xx it will allocate a new ip, which is the one he should use for remote access.

What a load of bollock$, the very idea of NAT is to translate the external IP address to the internal one (that's why it is called port forwarding).
Feel free to come back when you have read Bugnote's post in full and you actually know what you are talking about.
In the meantime, get back behind the counter and keep those burgers coming, because it's obvious from the above statement you know fcuk all about networking.

EDIT:
Bugnote, what router do you have?

**bugnote** · 14th March 2003

thanks for the discussions guys, i've got a rp614 Netgear 4 port router...

did a bit more diggin last night, there's a good tips guide on no-ip's website....

anyway, I did the old 'turn it off, turn it on again' chestnut, and its working fine now.....(the router and CM that is)

funny old things computers aren't they!

cheers

Bug

P.S. Router has latest firmware, port forwarding 80 to my local IP, works fine, just as it should.

**Pegasus** · 14th March 2003

Originally posted by bugnote
anyway, I did the old 'turn it off, turn it on again' chestnut, and its working fine now.....(the router and CM that is)

Bugnote, whenever you make changes like that you always have to restart the router so those changes can be implemented (that applies to ANY router).
Anyway, glad it's working.