Apache working on LAN, not on internet (WAN)

rathodr used Ask the Experts™
I am running three servers: Win2003SBS, Win2003Ent and Linux Red Hat Fedora Core 3. For sake of discussion, lets call them as follows:

A = Win 2003 SBS
B = Win 2003 Ent
C = Linux Red Hat Fedora Core 3

All three are on a LAN behind a router. I have static IP and a registered name (lets use www.mysite.com). The routers config table is something like this:

HTTP     80     80      TCP  Enabled    ---> this is for A
HTTP2   8010  8010  TCP  Enabled    ---> this is for B
HTTP3   8100  8100  TCP  Enabled    ---> this is for C

A & B work. They are running IIS. The last one, C, does not work. It is running the Linux Red Hat Fedora Core 3 with Apache as the web server. The /etc/hosts has the following line:      flslinux.mysite.com    localhost.locadomain   localhost

Once I restart the httpd process, I am able to ping C from A and B. I can even open a browser from A & B machines and enter: http://www.mysite.com:8100 and get the appropriate page on C.

The problem is: if I go to another machine, outside of the router (i.e. somewhere else on the internet), I was initially getting:

Zero Sized Reply.

Once I reset the httpd.conf file, now I get:

Connection Refused.

In the apache logs, the only file that shows any sign of an issue is the ssl_error_log. There are two lines that say "localhost.localdomain error"

Ok, where shall I start debugging this one? BTW: if anyone provides suggestions, would you please give me specific instructions and commands? I know you don't have my exact system configuration in Linux, but the more info. you can give me, the faster I will be able to try it.

Thank you.
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Well the first thing I would want to check is that you are not running iptables and bloking your connection,
As root run the command:
iptables -L

And paste the output here.

We will also want to check that apache is set to listen on that port.
Check your httpd.conf (probably /etc/httpd/conf/httpd.conf)
There should be a line:
which is the default.  Change that to
so apache knows to listen on port 8100 (the port you are forwarding to it on)

Sorry for the slow response, I was away from my computer for a few days...


Thank you for getting me started on the debugging.

The latest is: I can use the browser locally and see the site using http://www.mysite.com:8100, http://www.xxx.yyy.zzz:8100 (the static ip from the ISP). When I try http://localhost, I get "The Connection was refused when trying to contact localhost" error. From another machine on the LAN, I can successfully see the website using http://www.mysite.com:8100 and http://www.xxx.yyy.zzz:8100. I must have monkeyed with the /etc/hosts file to not allow the http://localhost.

The iptables -L output:
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

The /etc/httpd/conf/httpd.conf  (this file is lengthy because I kept the original comments in the file):
# Based upon the NCSA server configuration files originally by Rob McCool.
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See URL:http://httpd.apache.org/docs-2.0/ for detailed information about
# the directives.
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
# The configuration directives are grouped into three basic sections:
#  1. Directives that control the operation of the Apache server process as a
#     whole (the 'global environment').
#  2. Directives that define the parameters of the 'main' or 'default' server,
#     which responds to requests that aren't handled by a virtual host.
#     These directives also provide default values for the settings
#     of all virtual hosts.
#  3. Settings for virtual hosts, which allow Web requests to be sent to
#     different IP addresses or hostnames and have them handled by the
#     same Apache server process.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/etc/httpd" will be interpreted by the
# server as "/etc/httpd/logs/foo.log".

### Section 1: Global Environment
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.

# Don't give away too much information about all the subcomponents
# we are running.  Comment out this line if you don't mind remote sites
# finding out what major optional modules you are running
ServerTokens OS

# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
# (available at <URL:http://httpd.apache.org/docs-2.0/mod/core.html#lockfile>);
# you will save yourself a lot of trouble.
# Do NOT add a slash at the end of the directory path.
ServerRoot "/etc/httpd"

# ScoreBoardFile: File used to store internal server process information.
# If unspecified (the default), the scoreboard will be stored in an
# anonymous shared memory segment, and will be unavailable to third-party
# applications.
# If specified, ensure that no two invocations of Apache share the same
# scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK.
#ScoreBoardFile run/httpd.scoreboard

# PidFile: The file in which the server should record its process
# identification number when it starts.
PidFile "/var/run/httpd.pid"

# Timeout: The number of seconds before receives and sends time out.
TimeOut 600

# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
KeepAlive false

# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
MaxKeepAliveRequests 100

# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
KeepAliveTimeout 15

## Server-Pool Size Regulation (MPM specific)

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule prefork.c>
StartServers 8
MinSpareServers 5
MaxSpareServers 20
MaxClients 150
MaxRequestsPerChild 100

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule worker.c>
StartServers         2
MaxClients         150
MinSpareThreads     25
MaxSpareThreads     75
ThreadsPerChild     25
MaxRequestsPerChild  0

# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (

# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule access_module modules/mod_access.so
LoadModule auth_module modules/mod_auth.so
LoadModule auth_anon_module modules/mod_auth_anon.so
LoadModule auth_dbm_module modules/mod_auth_dbm.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule auth_ldap_module modules/mod_auth_ldap.so
LoadModule include_module modules/mod_include.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule headers_module modules/mod_headers.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imap_module modules/mod_imap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule cache_module modules/mod_cache.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule cgi_module modules/mod_cgi.so

# Load config files from the config directory "/etc/httpd/conf.d".
Include conf.d/*.conf

# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#ExtendedStatus On

### Section 2: 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.

# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
# User/Group: The name (or #number) of the user/group to run httpd as.
#  . On SCO (ODT 3) use "User nouser" and "Group nogroup".
#  . On HPUX you may not be able to use shared memory as nobody, and the
#    suggested workaround is to create a user www and use that user.
#  NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
#  when the value of (unsigned)Group is above 60000;
#  don't use Group #-1 on these systems!
User apache
Group apache

# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
ServerAdmin webmaster@mysite.com

# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If this is not set to valid DNS name for your host, server-generated
# redirections will not work.  See also the UseCanonicalName directive.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address anyway, and this will make
# redirections work in a sensible way.
ServerName localhost

# UseCanonicalName: Determines how Apache constructs self-referencing
# URLs and the SERVER_NAME and SERVER_PORT variables.
# When set "Off", Apache will use the Hostname and Port supplied
# by the client.  When set "On", Apache will use the value of the
# ServerName directive.
UseCanonicalName on

# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/var/www/html/mambo"

# Disable autoindex for the root directory, and present a
# default Welcome page if no other index page is present.
<LocationMatch "^/$">
    Options -Indexes
    ErrorDocument 403 /error/noindex.html

# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received.
# The path to the end user account 'public_html' directory must be
# accessible to the webserver userid.  This usually means that ~userid
# must have permissions of 711, ~userid/public_html must have permissions
# of 755, and documents contained therein must be world-readable.
# Otherwise, the client will only receive a "403 Forbidden" message.
# See also: http://httpd.apache.org/docs/misc/FAQ.html#forbidden
<IfModule mod_userdir.c>
    # UserDir is disabled by default since it can confirm the presence
    # of a username on the system (depending on home directory
    # permissions).
    UserDir "disable"

    # To enable requests to /~user/ to serve the user's public_html
    # directory, use this directive instead of "UserDir disable":
    #UserDir public_html


# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents.  The MultiViews Option can be used for the
# same purpose, but it is much slower.

# AccessFileName: The name of the file to look for in each directory
# for access control information.  See also the AllowOverride directive.
#AccessFileName .htaccess

# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all

# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
TypesConfig "/etc/mime.types"

# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain

# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
<IfModule mod_mime_magic.c>
#   MIMEMagicFile /usr/share/magic.mime
    MIMEMagicFile conf/magic

# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
HostNameLookups Off

# EnableMMAP: Control whether memory-mapping is used to deliver
# files (assuming that the underlying OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems.  On some systems, turning it off (regardless of
# filesystem) can improve performance; for details, please see
# http://httpd.apache.org/docs-2.0/mod/core.html#enablemmap
#EnableMMAP off

# EnableSendfile: Control whether the sendfile kernel support is
# used to deliver files (assuming that the OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems.  Please see
# http://httpd.apache.org/docs-2.0/mod/core.html#enablesendfile
#EnableSendfile off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "/var/log/httpd/error_log"

# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel debug

# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here.  Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
# CustomLog logs/access_log common
CustomLog logs/access_log combined

# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#CustomLog logs/referer_log referer
#CustomLog logs/agent_log agent

# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog logs/access_log combined

# Optionally add a line containing the server version and virtual host
# name to server-generated pages (error documents, FTP directory listings,
# mod_status and mod_info output etc., but not CGI generated documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of:  On | Off | EMail
ServerSignature on

# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL.  So "/icons" isn't aliased in this
# example, only "/icons/".  If the fakename is slash-terminated, then the
# realname must also be slash terminated, and if the fakename omits the
# trailing slash, the realname must also omit it.
# We include the /icons/ alias for FancyIndexed directory listings.  If you
# do not use FancyIndexing, you may comment this out.
Alias /icons/ "/var/www/icons/"

# This should be changed to the ServerRoot/manual/.  The alias provides
# the manual, even if you choose to move your DocumentRoot.  You may comment
# this out if you do not care for the documentation.
#Alias /manual "/var/www/manual"

<IfModule mod_dav_fs.c>
    # Location of the WebDAV lock database.
    DAVLockDB /var/lib/dav/lockdb

# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"

<IfModule mod_cgid.c>
# Additional to mod_cgid.c settings, mod_cgid has Scriptsock <path>
# for setting UNIX socket for communicating with cgid.
#Scriptsock            logs/cgisock

# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Example:
# Redirect permanent /foo http://www.example.com/bar

# Directives controlling the display of server-generated directory listings.

# FancyIndexing is whether you want fancy directory indexing or standard.
# VersionSort is whether files containing version numbers should be
# compared in the natural way, so that `apache-1.3.9.tar' is placed before
# `apache-1.3.12.tar'.
IndexOptions FancyIndexing VersionSort NameWidth=*

# AddIcon* directives tell the server which icon to show for different
# files or filename extensions.  These are only displayed for
# FancyIndexed directories.
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*

AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core

AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^

# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
DefaultIcon /icons/unknown.gif

# AddDescription allows you to place a short description after a file in
# server-generated indexes.  These are only displayed for FancyIndexed
# directories.
# Format: AddDescription "description" filename
#AddDescription "GZIP compressed document" .gz
#AddDescription "tar archive" .tar
#AddDescription "GZIP compressed tar archive" .tgz

# ReadmeName is the name of the README file the server will look for by
# default, and append to directory listings.
# HeaderName is the name of a file which should be prepended to
# directory indexes.
ReadmeName README.html
HeaderName HEADER.html

# IndexIgnore is a set of filenames which directory indexing should ignore
# and not include in the listing.  Shell-style wildcarding is permitted.
IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t

# AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
AddEncoding x-compress Z
AddEncoding x-gzip gz tgz

# DefaultLanguage and AddLanguage allows you to specify the language of
# a document. You can then use content negotiation to give a browser a
# file in a language the user can understand.
# Specify a default language. This means that all data
# going out without a specific language tag (see below) will
# be marked with this one. You probably do NOT want to set
# this unless you are sure it is correct for all cases.
# * It is generally better to not mark a page as
# * being a certain language than marking it with the wrong
# * language!
# DefaultLanguage nl
# Note 1: The suffix does not have to be the same as the language
# keyword --- those with documents in Polish (whose net-standard
# language code is pl) may wish to use "AddLanguage pl .po" to
# avoid the ambiguity with the common suffix for perl scripts.
# Note 2: The example entries below illustrate that in some cases
# the two character 'Language' abbreviation is not identical to
# the two character 'Country' code for its country,
# E.g. 'Danmark/dk' versus 'Danish/da'.
# Note 3: In the case of 'ltz' we violate the RFC by using a three char
# specifier. There is 'work in progress' to fix this and get
# the reference data for rfc1766 cleaned up.
# Danish (da) - Dutch (nl) - English (en) - Estonian (et)
# French (fr) - German (de) - Greek-Modern (el)
# Italian (it) - Norwegian (no) - Norwegian Nynorsk (nn) - Korean (kr)
# Portugese (pt) - Luxembourgeois* (ltz)
# Spanish (es) - Swedish (sv) - Catalan (ca) - Czech(cz)
# Polish (pl) - Brazilian Portuguese (pt-br) - Japanese (ja)
# Russian (ru) - Croatian (hr)
AddLanguage da .dk
AddLanguage nl .nl
AddLanguage en .en
AddLanguage et .et
AddLanguage fr .fr
AddLanguage de .de
AddLanguage he .he
AddLanguage el .el
AddLanguage it .it
AddLanguage ja .ja
AddLanguage pl .po
AddLanguage kr .kr
AddLanguage pt .pt
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pt-br .pt-br
AddLanguage ltz .ltz
AddLanguage ca .ca
AddLanguage es .es
AddLanguage sv .se
AddLanguage cz .cz
AddLanguage ru .ru
AddLanguage tw .tw
AddLanguage zh-tw .tw
AddLanguage hr .hr

# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
LanguagePriority en da nl et fr de el it ja kr no pl pt pt-br ltz ca es sv tw

# ForceLanguagePriority allows you to serve a result page rather than
# MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
# [in case no accepted languages matched the available variants]
ForceLanguagePriority Prefer Fallback

# Specify a default charset for all pages sent out. This is
# always a good idea and opens the door for future internationalisation
# of your web site, should you ever want it. Specifying it as
# a default does little harm; as the standard dictates that a page
# is in iso-8859-1 (latin1) unless specified otherwise i.e. you
# are merely stating the obvious. There are also some security
# reasons in browsers, related to javascript and URL parsing
# which encourage you to always set a default char set.
AddDefaultCharset ISO-8859-1

# Commonly used filename extensions to character sets. You probably
# want to avoid clashes with the language extensions, unless you
# are good at carefully testing your setup after each change.
# See ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets for
# the official list of charset names and their respective RFCs
AddCharset ISO-8859-1  .iso8859-1  .latin1
AddCharset ISO-8859-2  .iso8859-2  .latin2 .cen
AddCharset ISO-8859-3  .iso8859-3  .latin3
AddCharset ISO-8859-4  .iso8859-4  .latin4
AddCharset ISO-8859-5  .iso8859-5  .latin5 .cyr .iso-ru
AddCharset ISO-8859-6  .iso8859-6  .latin6 .arb
AddCharset ISO-8859-7  .iso8859-7  .latin7 .grk
AddCharset ISO-8859-8  .iso8859-8  .latin8 .heb
AddCharset ISO-8859-9  .iso8859-9  .latin9 .trk
AddCharset ISO-2022-JP .iso2022-jp .jis
AddCharset ISO-2022-KR .iso2022-kr .kis
AddCharset ISO-2022-CN .iso2022-cn .cis
AddCharset Big5        .Big5       .big5
# For russian, more than one charset is used (depends on client, mostly):
AddCharset WINDOWS-1251 .cp-1251   .win-1251
AddCharset CP866       .cp866
AddCharset KOI8-r      .koi8-r .koi8-ru
AddCharset KOI8-ru     .koi8-uk .ua
AddCharset ISO-10646-UCS-2 .ucs2
AddCharset ISO-10646-UCS-4 .ucs4
AddCharset UTF-8       .utf8

# The set below does not map to a specific (iso) standard
# but works on a fairly wide range of browsers. Note that
# capitalization actually matters (it should not, but it
# does for some browsers).
# See ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets
# for a list of sorts. But browsers support few.
AddCharset GB2312      .gb2312 .gb
AddCharset utf-7       .utf7
AddCharset utf-8       .utf8
AddCharset big5        .big5 .b5
AddCharset EUC-TW      .euc-tw
AddCharset EUC-JP      .euc-jp
AddCharset EUC-KR      .euc-kr
AddCharset shift_jis   .sjis

# AddType allows you to add to or override the MIME configuration
# file mime.types for specific file types.
AddType application/x-tar .tgz

# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#AddHandler cgi-script .cgi

# For files that include their own HTTP headers:
#AddHandler send-as-is asis

# For server-parsed imagemap files:
AddHandler imap-file map

# For type maps (negotiated resources):
# (This is enabled by default to allow the Apache "It Worked" page
#  to be distributed in multiple languages.)
AddHandler type-map var

# Filters allow you to process content before it is sent to the client.
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
AddOutputFilter INCLUDES .shtml

# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location

# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html

Alias /error/ "/var/www/error/"

# The following directives modify normal HTTP response behavior to
# handle known problems with browser implementations.
BrowserMatch "Mozilla/2" nokeepalive
BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0

# The following directive disables redirects on non-GET requests for
# a directory that does not include the trailing slash.  This fixes a
# problem with Microsoft WebFolders which does not appropriately handle
# redirects for folders with DAV methods.
BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully
BrowserMatch "^WebDrive" redirect-carefully
BrowserMatch "^WebDAVFS/1.[012]" redirect-carefully
BrowserMatch "^gnome-vfs" redirect-carefully

# Allow server status reports, with the URL of http://servername/server-status
# Change the ".your-domain.com" to match your domain to enable.
#<Location /server-status>
#    SetHandler server-status
#    Order deny,allow
#    Deny from all
#    Allow from .your-domain.com

# Allow remote server configuration reports, with the URL of
#  http://servername/server-info (requires that mod_info.c be loaded).
# Change the ".your-domain.com" to match your domain to enable.
#<Location /server-info>
#    SetHandler server-info
#    Order deny,allow
#    Deny from all
#    Allow from .your-domain.com

# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#<IfModule mod_proxy.c>
#ProxyRequests On
#<Proxy *>
#    Order deny,allow
#    Deny from all
#    Allow from .your-domain.com

# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# Set to one of: Off | On | Full | Block
#ProxyVia On

# To enable the cache as well, edit and uncomment the following lines:
# (no cacheing without CacheRoot)
#CacheRoot "/etc/httpd/proxy"
#CacheSize 5
#CacheGcInterval 4
#CacheMaxExpire 24
#CacheLastModifiedFactor 0.1
#CacheDefaultExpire 1
#NoCache a-domain.com another-domain.edu joes.garage-sale.com

# End of proxy directives.

### Section 3: Virtual Hosts
# VirtualHost: If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
# Please see the documentation at
# <URL:http://httpd.apache.org/docs-2.0/vhosts/>
# for further details before you try to setup virtual hosts.
# You may use the command line option '-S' to verify your virtual host
# configuration.

# Use name-based virtual hosting.

# Where do we put the lock and pif files?
LockFile "/var/lock/httpd.lock"
CoreDumpDirectory "/etc/httpd"

# Defaults for virtual hosts

# Logs

# Virtual hosts

# Virtual host Default Virtual Host
       DocumentRoot "/var/www/html/mambo"
       ServerName www.mysite.com
      ServerAdmin webmaster@mysite.com      
       ServerSignature email
      DirectoryIndex index.php index.html index.htm index.shtml

# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.

<Directory "/">
        Options FollowSymLinks
        AllowOverride None

<Directory "/var/www/html">
        Options Indexes Includes FollowSymLinks
        AllowOverride None
        Allow from all
        Order allow,deny

<Directory "/var/www/html/mambo">
        Options Indexes Includes FollowSymLinks
        AllowOverride None
        Allow from all
        Order allow,deny

<Directory "/var/www/icons">
        Options Indexes MultiViews
        AllowOverride None
        Allow from all
        Order allow,deny

<Directory "/var/www/cgi-bin">
        Options ExecCGI
        AllowOverride None
        Allow from all
        Order allow,deny

The /etc/hosts :
# Do not remove the following line, or various programs
# that require network functionality will fail.      localhost.localdomain localhost      flslinux.mysite.com flslinux www.mysite.com

Additionally, I have a hosts.allow and renamed hosts.deny to hosts.deny.sav. Here is /etc/hosts.allow :
# hosts.allow   This file describes the names of the hosts which are
#               allowed to use the local INET services, as decided
#               by the '/usr/sbin/tcpd' server.

Ok you don't look to be running any iptables to block incoming connections so that route is clear.

What do you mean when you said, "I must have monkeyed with the /etc/hosts file to not allow the http://localhost."

Ok, the configuration file is set to
Which tells apache to listen on any interface (ethernet card) on port 8100, that should be set.

(Just because I want to cover my butt :) )
Are you sure that the Fedora machine is on IP
And are you sure that the port 8100 redirection is enabled on the router?

What might be useful is to open yourself a few shell windows and tail both the system log and apache log files while you
a) restart httpd
b) connect from an internal machine
c) connect from an external machine

You can tail the log files with the following comands, note you'll need to be root and run each one in a seperate shell/xterm.
tail -f /var/log/httpd/access_log
tail -f /var/log/httpd/error_log
tail -f /var/log/messages
Amazon Web Services

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.


With the /etc/hosts file, I modified it manually and now, if I type http://localhost on the local machine (where Apache is running), I get the error message. it was not giving me the error message before. Anyway, I made the changes long enough before that I cannot remember what the original (after Fedora was installed) file looked like. I figured, I will attack that problem later as it is nive to have it working, but not of the highest priority (or aleast I think its not the highest priority!)

I will check the other items later this evening and repost.


default /etc/hosts should look like:

# Do not remove the following line, or various programs
# that require network functionality will fail.       localhost.localdomain   localhost


UPDATE: /sbin/ifconfig output:
eth0      Link encap:Ethernet  HWaddr 00:50:70:C8:48:99                                              <------ Comment: I masked this addr. to prevent anyone reading this
          inet addr:  Bcast:  Mask:                                from trying anything.  This is masked only for the posting here.
          inet6 addr: fe80::250:70ff:fec8:4999/64 Scope:Link
          RX packets:27350 errors:0 dropped:0 overruns:0 frame:0
          TX packets:34707 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12152992 (11.5 MiB)  TX bytes:8990997 (8.5 MiB)
          Interrupt:11 Base address:0xe000

lo        Link encap:Local Loopback
          inet addr:  Mask:
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:11138 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11138 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6542297 (6.2 MiB)  TX bytes:6542297 (6.2 MiB)

I checked the routers port forwarding and it is what I mentioned at the very begining of my original question. So I think its correct.

When I restart httpd, here are the messages
Feb 17 20:42:12 flslinux httpd: httpd shutdown succeeded
Feb 17 20:42:14 flslinux httpd: httpd startup succeeded
Feb 17 20:45:01 flslinux crond(pam_unix)[10080]: session opened for user root by (uid=0)
Feb 17 20:45:02 flslinux crond(pam_unix)[10080]: session closed for user root
Feb 17 20:45:15 flslinux nmbd[31355]: [2005/02/17 20:45:15, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(353)
Feb 17 20:45:15 flslinux nmbd[31355]:   find_domain_master_name_query_fail:
Feb 17 20:45:15 flslinux nmbd[31355]:   Unable to find the Domain Master Browser name FLSLINUXGROUP<1b> for the workgroup FLSLINUXGROUP.
Feb 17 20:45:15 flslinux nmbd[31355]:   Unable to sync browse lists in this workgroup.

/var/log/httpd/access_log: no additional messages

[Thu Feb 17 20:42:12 2005] [info] removed PID file /var/run/httpd.pid (pid=10026)
[Thu Feb 17 20:42:12 2005] [notice] caught SIGTERM, shutting down
[Thu Feb 17 20:42:13 2005] [notice] core dump file size limit raised to 4294967295 bytes
[Thu Feb 17 20:42:13 2005] [info] mod_unique_id: using ip addr
[Thu Feb 17 20:42:14 2005] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Feb 17 20:42:14 2005] [info] Init: Initializing OpenSSL library
[Thu Feb 17 20:42:14 2005] [info] Init: Seeding PRNG with 256 bytes of entropy
[Thu Feb 17 20:42:14 2005] [info] Init: Generating temporary RSA private keys (512/1024 bits)
[Thu Feb 17 20:42:14 2005] [info] Init: Generating temporary DH parameters (512/1024 bits)
[Thu Feb 17 20:42:14 2005] [info] Init: Initializing (virtual) servers for SSL
[Thu Feb 17 20:42:14 2005] [info] Server: Apache/2.0.52, Interface: mod_ssl/2.0.52, Library: OpenSSL/0.9.7a
[Thu Feb 17 20:42:15 2005] [notice] Digest: generating secret for digest authentication ...
[Thu Feb 17 20:42:15 2005] [notice] Digest: done
[Thu Feb 17 20:42:15 2005] [debug] util_ldap.c(1248): LDAP merging Shared Cache conf: shm=0x8f14010 rmm=0x8f14030 for VHOST: www.meeract.com
[Thu Feb 17 20:42:15 2005] [debug] util_ldap.c(1248): LDAP merging Shared Cache conf: shm=0x8f14010 rmm=0x8f14030 for VHOST: localhost
[Thu Feb 17 20:42:15 2005] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Thu Feb 17 20:42:15 2005] [notice] LDAP: SSL support unavailable
[Thu Feb 17 20:42:15 2005] [info] mod_unique_id: using ip addr
[Thu Feb 17 20:42:16 2005] [notice] mod_python: Creating 4 session mutexes based on 150 max processes and 0 max threads.
[Thu Feb 17 20:42:16 2005] [info] Init: Initializing OpenSSL library
[Thu Feb 17 20:42:16 2005] [info] Init: Seeding PRNG with 256 bytes of entropy
[Thu Feb 17 20:42:16 2005] [info] Init: Generating temporary RSA private keys (512/1024 bits)
[Thu Feb 17 20:42:16 2005] [info] Init: Generating temporary DH parameters (512/1024 bits)
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(364): shmcb_init allocated 512000 bytes of shared memory
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(550): entered shmcb_init_memory()
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(572): for 512000 bytes, recommending 4266 indexes
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(615): shmcb_init_memory choices follow
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(617): division_mask = 0x1F
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(619): division_offset = 64
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(621): division_size = 15998
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(623): queue_size = 1604
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(625): index_num = 133
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(627): index_offset = 8
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(629): index_size = 12
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(631): cache_data_offset = 8
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(633): cache_data_size = 14386
[Thu Feb 17 20:42:16 2005] [debug] ssl_scache_shmcb.c(646): leaving shmcb_init_memory()
[Thu Feb 17 20:42:16 2005] [info] Shared memory session cache initialised
[Thu Feb 17 20:42:16 2005] [info] Init: Initializing (virtual) servers for SSL
[Thu Feb 17 20:42:16 2005] [info] Server: Apache/2.0.52, Interface: mod_ssl/2.0.52, Library: OpenSSL/0.9.7a
[Thu Feb 17 20:42:16 2005] [debug] util_ldap.c(1432): INIT global mutex /tmp/fileePNrUd in child 10072
[Thu Feb 17 20:42:16 2005] [debug] util_ldap.c(1432): INIT global mutex /tmp/fileePNrUd in child 10073
[Thu Feb 17 20:42:16 2005] [debug] util_ldap.c(1432): INIT global mutex /tmp/fileePNrUd in child 10074
[Thu Feb 17 20:42:16 2005] [debug] util_ldap.c(1432): INIT global mutex /tmp/fileePNrUd in child 10076
[Thu Feb 17 20:42:16 2005] [debug] util_ldap.c(1432): INIT global mutex /tmp/fileePNrUd in child 10077
[Thu Feb 17 20:42:16 2005] [debug] util_ldap.c(1432): INIT global mutex /tmp/fileePNrUd in child 10078
[Thu Feb 17 20:42:16 2005] [debug] util_ldap.c(1432): INIT global mutex /tmp/fileePNrUd in child 10079
[Thu Feb 17 20:42:16 2005] [notice] Apache/2.0.52 (Fedora) configured -- resuming normal operations
[Thu Feb 17 20:42:16 2005] [info] Server built: Nov 11 2004 10:31:42
[Thu Feb 17 20:42:16 2005] [debug] prefork.c(955): AcceptMutex: sysvsem (default: sysvsem)
[Thu Feb 17 20:42:16 2005] [debug] util_ldap.c(1432): INIT global mutex /tmp/fileePNrUd in child 10075

When I access the httpd from LAN, I receive the following messages:
Feb 17 20:50:01 flslinux crond(pam_unix)[10083]: session opened for user root by (uid=0)
Feb 17 20:50:01 flslinux crond(pam_unix)[10085]: session opened for user root by (uid=0)
Feb 17 20:50:01 flslinux crond(pam_unix)[10085]: session closed for user root
Feb 17 20:50:01 flslinux crond(pam_unix)[10083]: session closed for user root

/var/log/httpd/access_log: - - [17/Feb/2005:20:50:17 -0500] "GET /templates/rhuk_solarflare/css/template_css.css HTTP/1.1" 200 9647 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:17 -0500] "GET /templates/rhuk_solarflare/images/title_back.png HTTP/1.1" 200 1762 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:17 -0500] "GET / HTTP/1.1" 200 19999 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:17 -0500] "GET /templates/rhuk_solarflare/images/header_short.jpg HTTP/1.1" 200 12160 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /templates/rhuk_solarflare/images/subhead_bg.png HTTP/1.1" 200 293 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /images/M_images/rss091.gif HTTP/1.1" 200 224 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /images/M_images/rss10.gif HTTP/1.1" 200 218 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /images/M_images/rss20.gif HTTP/1.1" 200 219 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /images/M_images/atom03.gif HTTP/1.1" 200 991 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /images/M_images/opml.png HTTP/1.1" 200 288 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /templates/rhuk_solarflare/images/advertisement.png HTTP/1.1" 200 279 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /images/banners/OiBanner.gif HTTP/1.1" 200 7726 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /templates/rhuk_solarflare/images/powered_by.png HTTP/1.1" 200 1439 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /templates/rhuk_solarflare/images/menu_bg.png HTTP/1.1" 200 262 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /templates/rhuk_solarflare/images/arrow.png HTTP/1.1" 200 238 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /templates/rhuk_solarflare/images/rating_star_blank.png HTTP/1.1" 200 418 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /images/stories/asterisk.png HTTP/1.1" 200 3385 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)" - - [17/Feb/2005:20:50:18 -0500] "GET /templates/rhuk_solarflare/images/contenthead.png HTTP/1.1" 200 287 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)"

/ver/log/httpd/error_log: no additional messages

When I access the httpd from WAN, I receive no additional messages from any of the log files.

Now, if I had to debug this, my best guess would be in the /var/log/messages during httpd restart. The following line:
Feb 17 20:45:15 flslinux nmbd[31355]:   find_domain_master_name_query_fail:
appears to say that the nmbd service could not resolve the flslinux name. But this would be a total guess on my part. Any clues what this all means??


I was Googling and I found the following. It appears this user has a similar issue:

I read a peculiar refrence in this and here is a clip from that post:
This is what I had to do:

I have a Billion 746 router / firewall / ADSL modem.

First I gave the server a steady IP address. Called it Then by using a different machine on same network, I can see the web pages by typing [url][/url] in the browser. (My Apache web server is set up in port 8080, not the standard port 80) (You can also type that on the linux machine, and you should see the pages, instead of using [url]http://localhost/[/url] )

Then, in the route, I redirected port 8080 to IP Think it was under menu "virtual connection".

The IP address my ISP gave me is something like, so by going to work, and typing [url][/url] I managed to connect to the webserver at home.

In the firewall I opened of course port 8080 both ways. And did the same thing in my Linux firewall.

I can't figure out what the "Linux firewall" is. Reading through these steps, it appears I have done everything except the last line. I currently do not have a firewall enabled on the router. Finally, if my Linux firewall is enabled and not accepting incoming, then it could explain it. But what is this "Linux firewall"?
Anyway, poking around some more, I decided to check out ICANN port numbers. It appears 8100 is used up, so I went to 8081. I changed the router table and then httpd.conf. In the httpd.conf, I also changed "ServerName" to "flslinux.mysite.com" and the <Virtual Host localhost> Servername to flslinux.mysite.com.

Now, I get another reply. This time, when I attempt to access the httpd server, I get:
"Zero Sized Reply"

Am I making progress, or just creating different or more complex errors?


I am getting this "Zero Sized Reply" even if I have a simple HTML page. Within the LAN, I do not get this error. So it appears I still have the same connectivity issue, (I cannot get to the server from the WAN), but for different reasons.


Well that's it. I gave up on that installation. I really messed up the config -- so much that I couldn't even get to the outside world.

So, last night, I reinstalled Fedore Core 3. I installed everything the distro had to offer. The firewall is enabled, Apache, mySQL, PHP installed. I quickly changed the listening port to 8081. The firewall is blocking all requests, so I need to enable it to pass the requests in.

What is it I should change in the firewall setting to allow HTTP requests to be served?

I have not installed Fedora so I'm not sure how they are setting up their firewall rules - i would imagine it's an iptables script and you should just be able to allow port 8100 incoming (see if you cna find a configuration qizard) - I'll take a look at this again tomorrow when I have some free time, I'm traveling for my company right now.


Thank you -- I appreciate your help thus far.

I reinstalled the whole Fedora. (I even reformatted the hard drive)

The problem is still there. In the initial install, I brought up the firewall and was able to see the tables and their respective entries. I wonder if using the firewall is required (though I can't imagine why!). Another soln I am contemplating is using the firewall with the appropriate entries (just as you suggest above).

BTW: I believe now they are using something call IPCHAINS, which appears to be IPTABLES. I am looking into this further.

Please let me know if you come up with other ideas. Thanks, again!


As I read more, I think I may be coming up on some configuration questions. Can I have the following (knowing I do not have a firewall and an unprotected system is dangerous):

          DSL MODEM
                     |    (www.xxx.yyy.zzz - Static IP assigned by ISP)
                     |-----(192.168.1.aaa - internal IP) LINUX BOX
                     |       (no firewall, no DHCP, no DNS, Apache web server)
                     |-----(192.168.1.bbb - internal IP) WINDOWS BOX
                     |       (DHCP, DNS, IIS, Exchange)

Sounds pretty straight, but the material I have been reading shows that the Linux box requires a firewall and some mechanism to point outside.
Sorry for the long absence, I was on a trip to California with no notice, that ended up requiring a stop through Kentucky on the way back home..

As for the firewall, ipchains is much older then iptables - Again not using fedora I'm not 100% sure, but Redhat 9 which fedora was based on was using iptables for a long time, so I'm guessing they used that.  (Many times ipchains are also included for compatability).

The setup you've shown above should be perfectly fine - I'm not sure what you are talking about when you say the linux boz requires some mechanism to point outside?  All that should need done here is each web server behind the firewall should be set to listen on a different port, and that port should be forwarded from the router (which has your public IP) to the correct webserver like you showed in the first place.
HTTP     80     80      TCP  Enabled    ---> this is for A
HTTP2   8010  8010  TCP  Enabled    ---> this is for B
HTTP3   8100  8100  TCP  Enabled    ---> this is for C

I run 2 webservers (granted both are Linux) at home behind my router without a problem - so it's certainly doable.  
I think we either have a config problem here, or we have a firewall on the fedora box sticking it''s hand in the way.

For the sake or argument, can you run the linux firewall on port 80 (and set the config file back to 80) ?  This lets us prove that your existing port forwarding to the windows machine running on 80 fails when trying to connect to the linux box.  We then know it is the linux box with the problem and not your router/setup.


Ok, its working! Your last response was right on mark. During the absence of the messages, I learned a few things about Fedora -- its soooo tightly wrapped that trying to load all, or most, of the features tends to limit the freedom of configurability. So, after about 6 reinstalls (thats right, I don't even know how many), I ended up doing the following:

1. Install Fedora without Apache & MySQL.
2. Once installed, I downloaded Apache, PHP, and MySQL (all latest versions).
3. I installed Apache, PHP and MySQL in that order. After each install, I made sure the previous packages did not break.
4. Finally, I installed Mambo server. I have an issue with Mambo, but that's another post.

I decided to use Port 80 since this box will be the final production box. I did the router port forwarding and it has been flawless.

Anyway, I am pretty sure I would have still been lost without your help -- so I thank you. Additionally, I am documenting a link here: http://www.ntsug.org/docs/snort_acid_fc1.pdf
that was the exact steps I followed to make all of this work. This person documented so well, that I was able to make a couple of minor tweaks and have the four steps above completed in one day. I highly suggest taking a look at this doc!

The IPTABLES is running and setup the way Fedora installed it. So, it does work -- as long as you don't mess with it (unless of course, you know exactly what you're doing). And, planning on reinstalls is a good idea as a learning process.

Best Regards.

Glad everything is working for you!

(P.S. I'm going to edit your post so the URL is correct, you have .org and it's .pdf)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial