OK, I have an FTP server that I use for file storage, and I wanted to set up apache to serve the FTP directory so that I can also link to files that have been uploaded. So I set about configuring apache yesterday, and I think everything is working OK. I have 3 computers on a local LAN, one of them is the apache/FTP box. I have a no-ip acount that I use to point to the FTP server. I can connect via FTP fine, and I am confident that I have the port forwardings on my router set up correctly. The firewall on the apache/FTP box is off currently. Apache is being run as standalone, FTP is being run through inetd.

The problem is, I can connect to the web server from all fo the computers that are on my LAN, even when using the FQDN that people would use to connect externally as well. However, people outside my LAN cannot connect to the web server, even though people CAN connect to the same machine using ssh and FTP.

I'm at work and I won't be able to post my httpd.conf until I get home.
In the mean time, is there anything that is commonly missed that would cause this problem?
Recap:

FTP - can connect internally and externally
ssh - can connect internally and externally
http - can only connect internally

any ideas?

slight

Are you behind a router or such? If so do you have port 80 forwarded to your machine? Any other firewall setup at all? Is your ISP blocking port 80?

Yes, yes, no and I'm not sure.... can my ISP block incoming port 80? I have only a basic acount, and not a business acount, but I didn't think that they would block port 80 by default. They don't block FTP, and they don't block SSH, so why block http? Also, doesn't the fact that I can connect to the web server using the FQDN from inside my LAN mean that they are NOT blocking the port? If they were, I would expect that I could connect internally using the internal IP, but not the FQDN.

slight