Okay sorry, the real error message is:

root@server:/home/httpd/bin# apachectl start
(99)Cannot assign requested address: make_sock: could not bind to address 192.168.0.1:80
no listening sockets available, shutting down
Unable to open logs

And yes, I have googled and researched this problem myself before coming to the forums. Everyone else seemed to solve the problem by listening to any ip address at the specific port. This does not work for me..

192.168.0.1 is the address of my router.. however, it is properly configured to forward all http (port 80) traffic to the server. The server's ip on the LAN is 192.168.0.101.. Thanks for any further suggestions.

Okay, I resolved that issue (apparently I must have installed apache in two different locations or something.. the apache demean in /home/httpd/bin was actually executing a httpd.conf file in /etc/httpd for whatever reason... (I was editing the httpd.conf file in /home/httpd/conf) =(

Now I am able to actually start the httpd, HOWEVER I believe it is only accessible from my LAN. When I ping 'schulte.homelinux.com' from my lan it correctly identifies the ip, and has 0% packet loss. When I ping from outside the lan, then schulte.homelinux.com correctly resolves the correct ip, but the ping fails with 100% packet loss.

ping is ICMP and has nothing to do with http and port 80. try from outside to "telnet your.server.wan.ip 80"

anyhow, can you access the webpage from within the LAN? we have to locate the problem to either the router, or the httpd server

Okay, here are the results from accessing the webpage from the LAN:

Typing schulte.homelinux.com fails
Typing the public ip address fails

However, typing the private ip address of the server does pull up the "It Works!" apache default webpage.

so... does this mean there is something wrong with my router forwarding traffic to the http server? Or perhaps my isp? Maybe there is something I have done wrong in the configuration files..

well, if you can access the http server, you must have misconfigured port forwarding on your router. try to put the server's IP in the DMZ address in the router and see if that helps

I have port forwarding enabled property.. it's configured the same way for my ssh and irc servers (just with a different port).

The DMZ doesn't work either

I am certain that it has nothing to do with my router.. is there any other config file or something that would be stopping traffic on port 80?

I edited my hosts file to contain the server's private ip followed by 'schulte.homelinux.com'.

as I said - if you can reach the webpage from the lan, but cannot reach it from outside - something is wrong with port forwarding

you might not have enough memory?

I know that MySQL says "cannot create socket" if you have under 256ram, and it intermittently refuses connections. Maybe the same thinking applies to apache?

Really? I only have 96MB of ram... and I know for a fact that port forwarding is properly configured..