Scott: >>> I still seem to have the same problem where index.php is not coming up >>> properly. by this I mean I cannot see it at all. Tim: >> A 404 error? Scott: > No it doesn't look like a 404 error. Here is what it says. > Network Error > > block quote > Network Error (tcp_error) > > A communication error occurred: "" > The Web Server may be down, too busy, or experiencing other problems > preventing it from responding to requests. Sounds like it might be the same thing that I just mentioned to someone else: How are you accessing the website? By domain name or IP? And if by domain name, what IP address does that machine see it as? If you're trying to browse a server on the same machine as the browser, and you're trying to use an external IP address, it may not work. Your networking hardware or firewall rules may not route such a connection through. It can help if *that* machine has a hosts file entry giving a LAN IP address for the domain name. That way, when it browses to the domain name, the networking is all internal. If it's not a routing issue, then it sounds like your server isn't listening. -- [tim@bigblack ~]$ uname -ipr 2.6.22.1-41.fc7 i686 i386 Using FC 4, 5, 6 & 7, plus CentOS 5. Today, it's FC7. Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
