'httpd' does not stop with '/etc/init.d/httpd stop' even though it says it does.
'http://192.168.0.6' still goes to the 'It works!' page.

Also, 'drakconf' says 'httpd' is stopped.

Hmmm, OK the fact that it does not stop may help explain why changes to the configuration changes that you are making to the httpd.conf file do not appear to be recognized.

Because in the format that the conf file should have the system listening not on port 80, but on port 8080.

If it is possible, I would like to see of you could restart the machine. This way we know that the service will stop, and it will restart and read the configuration file. Once the system restarts, I would suspect that it should respond on the 'new' port. If after the reboot it still does not respond then I suspect that the httpd.conf file that we are editing is not controlling the instance of Apache that you are using and we will have to go back to the drawing board to sort things out.

Did a restart.
Entering 'http://192.168.0.6' gives the 'Failed to Connect' error screen.

dlw

http://192.168.0.6 does work on a different box.

So you can get to the web page on the default port (80), but not the alternate port (8080)?

Can you please tell me what 'Listen' lines you have in the httpd.conf file (you can of course ignore those lines starting with the number sign (#))?

'Listen 8080' is the only line in /etc/httpd/conf/httpd.conf

dlw

Hi guys - I know I's been long time ago.... but could you tell how that story ended??
I have similar problem - my apache keeps giving me "Access forbidden" message, and I don't know where to set it up properly
rgrds
T.J.

It didn't. I still have the problem.
Whoever was helping quit.

dlw

oh I feel your pain :-(

I solved one part of my problem: RootDirectory were pointing to wrong place. So now I can see 'It works!!" page - and now there is time to start a fight with no-ip ...

In my httpd.conf I put Listen for ports 80, 8080 and 8001 just to make sure that at least one of them will kick in. I found out that Apache denies all access to as default to whole file system "/" so it is nessesery to create a directive which will allow access to directory containnig www documents....
In your case i think it might be firewall blocking traffic to your box or there is some options set which deny access from foringer addresses - Listen shoould contain only port numbers i think no IPs