Tim Green wrote:
On 8/25/05, Ian bell ianbell@ukfsn.org wrote:
[...] What I am struggling with is making them appear on the web via my wireless router. At the moment if I point a browser at my fixed IP I get my router login page.
You need to reconfigure your router to forward port 80 to your Apache PC. It is also a HUGE security risk to be able to see the router's config page from outside the network, but luckily looking at http://84.45.208.102/ shows your Apache server. Therefore your router is probably already doing the right thing with port 80.
This may be a symptom of how Ian was testing.
If (from inside the LAN) you put your external IP address into your web browser, you'll simply end up at your router (and since you've come from the inside you'll have access to the router's front end).
To test what the outside world can see you'll need to check from the outside.
Incidentally, anyone planning this on a standard ADSL line needs to know what that first letter stands for: A=Asynchronous. Your connection is designed for low volume uploads (eg page requests) and high volume downloads (eg page data). By running a webserver you're reversing that, and your relatively puny 256kbps upload rate will get hammered (its 256kbps on ADSL regardless of your headline download rate).
Mark Rogers, More Solutions Ltd