No, on a differnt box on the same LAN http://192.168.0.6 does not take me to the 'It works.' page.

No, entering http://192.168.0.6 on a different box does not work.

If the noip client is working correctly your noip URL i.e dlw.no-ip.org should resolve to your external IP address. You can use whatsmyip.com to verify the IP address.

Your ISP may block webserver traffic and a firewall running on the webserver could block webserver traffic.

What ip do you give to no-ip.com?

OK, I appoligize for having misread your earlier statement. In order to get results from the outside, you will need to be able to access the resource from inside the network.

I suspect that the likely cause for this problem is related to the configuration of Apache. When I get home I will look to see if I can findout likely causes for Apache not to provide content to requesting hosts.

I found the following in /etc/httpd/httpd.conf which I understand is what runs Apache. What should the 'Listen 0.0.0.0:80'be? Or, should it be as is?

#
# 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 0.0.0.0:80

You do not need to give any IP to noip.com since that is the job of the noip client.
You do not need to change http.conf unless your ISP blocks port 80. Since you can not access the webserver from other PCs on your local network I assume a firewall is blocking access. Try turning the firewall off.

Listen 0.0.0.0:80

The way that I read this, it seems like your instance of Apache should be set to accept request from all IP address on port 80 (which of course is the default for a web browser making an HTTP request).

Yet you do not seem to be able to get the web server to host a page to the requsting system that is lying on the same subnet. I know that this may seem like a silly question, but from the system on the same subnet, can you verify that you can ssh to your box (or barring that, can you at least ping the machine)?

What does this mean?
can you verify that you can ssh to your box

I can ping all four boxes on the network from all directions. From each box in other words.

PING 192.168.0.6 (192.168.0.6) 56(84) bytes of data.
64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=0.051 ms
64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=0.045 ms

--- 192.168.0.6 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.045/0.048/0.051/0.003 ms
[don@server ~]$

to ssh to a box is to create a secure shell connection. This is similar to creating a telnet connetction to a system, but it does not tranmit the information about the session in clear text on the wire, which is why many distrobutions have made ssh readily available.

I was thinking that this would be a good way to verify that you have no issues in establishing a network connection. But the ping should work for our purposes. So to recap, we are comfortable that from the other systems on this network, we can reach the 'web server' via the network, the http.conf file appears to be configured in such a way as to accept port 80 request from all IP address, yet we do not seem to be able to receive a response to a HTTP request from this system (even on the local network).

Does that seem to sum up where we currently stand?

If I understand it all correctly, yes, that seems to be the problem.
I can ping in all directions and to 192.168.0.6, the web server.
But, http does not work on the net or the LAN.

I think that where things stand.

OK, with that in mind I will do some digging on Apache and see what goodies I can find. Once we are comfortable with getting Apache to work for you on the LAN then we can go back at take a look at where we are with the no-ip solution.

Ugh... golly, gee whiz.... I kinda hate to admit this... but the httpd service was off. I turned it on and http://192.168.0.6 now works on the LAN but www.dlw.no-ip.org does not. But, it might work on your end.

Sorry about that.
Go ahead, call me names, it's all right.

No worries,

I am still unable to access anything from that URL, but at least we now know that the server is serving up web pages. It is possible as mentioned by michaelk earlier in the thread that your ISP may be our right blocking port 80 inbound to your connection.

One test for this would be to see if no-ip supports operations on non-traditional ports. If they do we can change the http.conf to answer request on some other port number (such as 9485) and then configure your router to forward that port and then make a web request to see if it goes through.

I will see if I find anything on no-ip documation for this.

Could it be in the DSL router?
I think I got it change to redirect to port 80.

I'll check again.