Mike and I just sorted this out. All services were running, but these were showing up in his logs:
[Fri Sep 03 13:18:06 2010] [error] (13)Permission denied: proxy: HTTP: attempt to connect to 127.0.0.1:7066 (localhost) failed
Which led us (eventually ;-) ) to temporarily disabling SELinux via the "setenforce Permissive" command (or "setenforce 0" for some of you). This fixed the problem, and an explanation is available here:
That being said, never leave SELinux turned off if you can help it; tweak it, adjust it, and make it work for you. "Security" is an assortment of methods and practices which must work like clockwork, and should be changed with all the care of a watchmaker. Disabling SELinux is the equivalent of bringing out the sledgehammer to get those darned gears back in place.