I installed Centos 5.5 on a new machine. The setup went OK with no errors. I have a static IP address from the ISP, let's call it:
72.86.26.xxx, and I reigstered a domain xxx.com with a registrar and pointed the A record to 72.86.26.xxx

During setup I edited the eth0 entry for static IP, and entered 2.86.26.xxx, and entered the host name, under hosts xxx.com

When the install was finished, the system restarted, and I logged back in as root. I had internet connectivity, indicating that my connectivity settings were correct (I am writing this message on the system, using Firefox). The problem is that when I enter xxx.com from another computer, I get nothing. It has been more than 48 hours, and when I ping xxx.com, it comes back with the correct IP address.

I am a newbier, so there could be some steps I missed. I looked through the FAQs, and googled the issues, but I could not find a solution. Suggestions are appreciated.

Regards

What is your goal? What exactly do you mean by "enter xxx.com from another computer"? Are you trying to run a Web server? SSH in? FTP?

I am running an Apache HTTP server. I also installed the FTP server. What I mean is that when I enter http://xxx.com in my browser, on another PC, I get a "cannot connect". But when I ping, it's there.

Ok, so is Apache installed, running, and listening on port 80 on the server?

It is running and listening to all addresses on port 80. If it was not running I would not be able to install and run webmin.

check with your firewall. stop iptables for while and check. If it works, then open port 80 in your firewall for your web interface.

Is the server behind a router? Have you forwarded port 80 form your router to the server's internal IP? Is the client behind the same router?

Hi,

The computer you are using to reach the server is on the same network, LAN? What are you using for DNS? Try entering the IP for the URL in the address on the second computer. If this works then you definitely have DNS issues. You said that 'ping' does provide link but name doesn't so what is setup for DNS for your LAN?

The server is plugged directly in the Ethernet port. Frontier (replaced Verizon locally), offers a fiber link that's a direct Ethernet port. It's no different from plugging into an Ethernet switch.

The client is on another connection, from Comcast. I use the Comcast connection for my home service, and the Frontier fiber port (just installed it for this server, which will be hosting multiple domains), for business.

No, separate networks, and separate ISPs. For DNS, on the server, I am using the ISP's DNS servers. Trying http://72.86.26.xxx is the first thing I did, no results. I pinged the name, not the IP address, and it resolved to the proper address (meaning the DNS servers at the registrar are properly configured), and the ping was returned.

On the server, can you get to port 80 on localhost?

Does Verizon block port 80 inbound? Try moving Apache to 81 or 7438 and see if http://72.x.x.x:pp works