Endless Paradigm

I've got Apache running on a computer and I'm trying to host some files. Simple enough.

I'm using no-ip.com to turn my dynamic IP into something a little more memorable, again simple enough. But, my router being a bitch, reserves port 80 for its online config so I'm running Apache through port 1234, forwarding port 1234 and set up no-ip.com to forward requests to port 1234. In theory that should work. But of course it doesn't.

Visiting robserv.no-ip.org just gives me a "Though the site seems valid, the browser was unable to establish a connection." error in Firefox but, when someone else other than me (I recruited the help of andrewcc for testing from another location) visits robserv.no-ip.org, Firefox gives a "Request timed out" error. Same thing happens when you try and ping me.

I've tried bypassing no-ip.com altogether by visiting my external IP with port 1234 on the end but that gives exactly the same results from both locations as typing in robserv.no-ip.org. No-IP therefore isn't the problem.

I've tested Apache also by putting my internal IP into Firefox with port 1234 on the end, that works fine. I've fiddled with firewalls and tried disabling them completely for testing, none of which made any difference.

I'm at a loss. I can't work out where exactly the problem lies. I think it may be either the router or the ISP but I can't be sure.

Help?

have you tried it with your PC added to the DMZ, see if that makes a difference? Can't imagine it would if you've tried disabling your firewall to no avail, but might be worth a check

Nah, I get exactly the same thing...

well traceroute seems to reach your IP, but then continues on and times out, and traceroute for the URL resolves at 14 173 ms 176 ms 174 ms url-redirect.noip.net [72.5.169.70]

All i can suggest is to phone your ISP and ask them if there is something in there service preventing it, although it may take a few tries to get through to someone who both can and will help

right... I'll wait until I get a contract phone (cheaper that pay-as-you-talk) then I'll give them a call...

Spoiler for Complete traceroute for URL and IP:

Just in case anyone else sees something i can't, but i tried the URL, and the IP that firefox said it resolved to (different to the one tracert resolved to)

Routers will probably drop ICMP packets so ping and traceroute are unlikely to work.

As for your issue, what interfaces is Apache listening on? Check the config file for a "Listen" directive.

I'm running Apache on an old P3-256MB-500GB computer mounted in a drawer (oh yeah... ghetto...). It connects to my home network with a USB WiFi dongle, so I'm assuming that's what Apache is listening on. I've set it to listen on port 1234 (because my router reserves port 80 for its online config) using this:

Code:

			#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 1234

From reading various tut's on the internet I think that is correct.

Can you post the entire configuration file?

is port 1234 forwarded to the computer running the server? (in router settings)
also try going to localhost:1234 on the server computer

PSPkiller

roberth

PSPkiller

roberth

PSPkiller

roberth

ZiNgA BuRgA

PSPkiller

ZiNgA BuRgA

Mickey