[SOLVED] fresh install; cannot access the server

[A-Learner]

I am a first time Apache user. I just installed Apache using Ubuntu server install CD. I installed a nearly complete setup for the server; LAMP and PostGRE and SSH but not email -- I just really want to use it as a test/development platform for converting an IIS-hosted MS-SQL Server application we developed a few years ago to run on MySQL and Apache.

 

I installed GNOME but configured the Ubuntu boot so that GNOME is not started automatically; I start it after logging in to the server by typing "sudo startx", that way GNOME's overhead is not present until I want it, and I can exit and remove it whenever I'm done doing admin tasks. I prefer using a GUI to command line.

 

Comcast issued me five static IPs. I have my legacy IIS/SQL-Svr system on a separate computer on the same LAN and gateway. The IIS/SQL-Svr computer uses one of the five IPs (Gateway, subnet mask, all that), and it works fine. I set the network connections for Apache using Menu|System|Administration|Network (in GNOME).  I used all the same data for the Gateway, subnet, etc and the next IP in the range issued by Comcast for the new (Ubuntu/LAMP) computer. I made no other changes to any other config file in the /etc/apache2 directory from their default contents after the installation; i.e., no aliases, no virtual servers, no changes at all.

 

When I open Firefox on the server and go to localhost, I get the "It works!". When I enter the static IP on a different computer completely outside the LAN, I get page not found. The IIS server operating through the same gateway configured with all the same IP data works fine (except that it uses the first static IP in the range Comcast issued), but the Apache server does not.

 

I figured this would be the simplest way to verify that the server was operational and online, but it does not work. What did I miss? I've been through three different text books on this and researched a dozen articles and forums, but I still seem to be missing something that ought to be obvious. Can anyone steer me straight? thanks!

 

Steve

[trq]

Do you need to confirue your gateway to allow connectins via port 80 to be forwarded to this new server?

 

It doesn't seem an issue with the server, but something within the network itself. Can you access this server from within the LAN using its internal LAN IP address?

 

On a side note. Don't issue 'sudo startx' to start Gnome. This would start Gnome and every process it spawns to run as root. A simple 'startx' should suffice.

[A-Learner]

Thankx, I'll remember the "startx" v "sudo startx". I'm an old DOS guy, not Unix, and there are a zillion little idiosyncrasies to learn...

 

Apparently my problem was related to the gateway. I've got it working now, but I'm not entirely sure what I did. When I wrote the base thread, I thought I had it configured exactly as I have it now, but now it is working and then it was not. Maybe a double-clutch is all it takes (just kidding... I must have had some kind of mistake in there somewhere).

 

*sigh*. Thanks for the response!