For some reason, I cannot get the index page from apache http server 2.2.13 from outside my network. But, there are caveats: using dyndns and port forwarding within my router, I CAN get to the index page of my NAS, and use all web interface functions. However, if I forward same port (http 80) to the machine running http server, no dice. It just doesn't make sense to me that I can reach in from outside the network to one IP in my home network using the same settings as another IP within the network, and the other just doesn't want to play. Am I missing something so ridiculously simple here? From within my network, and from other machines, I can reach the index page on my apache server, so I know the server is listening to :80 and responding (it's the only 'listen' I put in the config). What gives? Anyone have same or similar experience and figure it out?

I'd check the firewall settings on the linux box, also - does the HTTP server have a default route (gateway) ?? I'd also check w/ 'tcpdump -i <interface> "port 80"' and see if the SYN/ACK's are acutally leaving the box w/ the right destination IP. But, sounds like a routing issue...

Ha, all this time it was the machine running apache. Macafee firewall was preventing incoming traffic. What a n00b mistake. I've cleared the way, now it's time to start building website. Thanks for your assistance.