Jump to content


redhat 9 apache problems

  • Please log in to reply
3 replies to this topic

#1 chief

  • New Members
  • Pip
  • Newbie
  • 1 posts

Posted 19 November 2003 - 11:00 PM

first post; howdy;

i have redhat 9 and decided to setup a webserver. i used redhat-config-packages to install the webserver package, which includes apache, mysql, and others. then i tried http://localhost and the apache test page and works; i thought great, that was easy, until i tried to access the webserver from a networked computer. i get nothing in ie, just \"THE PAGE CANNOT BE DISPLAYED\".

i can ping the server and recieve confirm from a network machine but no webpage. i have turned on the httpd service and restarted it. i do not have a firewall in between computers and i believe i have configured the httpd.conf correctly

i don\'t know what to try next; can someone please help?

#2 Arenium

  • Staff Alumni
  • Advanced Member
  • 111 posts
  • LocationMassachusetts

Posted 20 November 2003 - 01:09 AM


probably something like

localhost is exactly how it sounds, LOCAL to THAT machine only. if the machine you\'re trying to view the page from doesnt have httpd running, then theres nothing to show.

http://localhost = http://[lan.ip.address] = http://[hostname] (my linux box is named martinman, so http://martinman works)

only exception is, the ip address and hostname (if configured correctly) is accessible to all computers within the network.

#3 greenhornet

  • New Members
  • Pip
  • Newbie
  • 2 posts
  • LocationSydney, Australia

Posted 21 November 2003 - 05:30 AM

Also check that port 80 (the default http port) is viewable by the other machines on your network. Even if you dont have a firewall in between the machines either computer might have a software firewall on it.

Use a program like nmap (is on the RH9 install disc) to do a port scan on the server from one of your other computers, if port 80 is open and you don\'t have your httpd.conf file setup to allow access to anyone (it is setup like this by default in RH9) then you should be able to see the pages as Arenium said above.

If nmap says port 80 isn\'t open then on the server machine as root type;
\"service iptables stop\" and try portscanning the server again. This command will turn your firewall off. It will startup again when you reboot the server however.

#4 sjennings

  • New Members
  • Pip
  • Newbie
  • 2 posts

Posted 22 November 2003 - 02:07 AM

If you have windows client PC\'s or even if you don\'t, find the \"hosts\" file. You can create your own virtual DNS testing environment using host files as it was done in the eraly days. Look in the etc/ folder this is where it should be.

Example Host File;


# Copyright © 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a \'#\' symbol.
# For example:
# rhino.acme.com # source server
# x.acme.com # x client host localhost datanet


Create a line under the examples that says something like this. MyServerName

The first line being the IP of your box that Apache is installed on and MyServerName being the actual name of the server that Apache is running on.

copy that or re-create that file to each client PC or on the server.

change your primary DNS server info that is bound to your NIC to either point to the Apache server if you created the new host file there or the client PC its self with the host file. This will allow the PC to look a local address, find the hosts file, and resolve the name to IP just like any DNS server out there.

You will now be able to type in \"MyServerName\", meaning, the actual name of the server that apache is running on and get full DNS resolution.

You can extend this concept to create your own internal www.xxx.com test environment as long as you are not hitting any live DNS servers on the net.

Hopes this helps, typing ip\'s to test your site gets old.

Shane J
Shane J

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users