From owner-freebsd-questions@FreeBSD.ORG Sat Feb 4 13:24:37 2006 Return-Path: X-Original-To: freebsd-questions@FreeBSD.org Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 655F516A420 for ; Sat, 4 Feb 2006 13:24:37 +0000 (GMT) (envelope-from robin@reportlab.com) Received: from smtp2.freeserve.com (smtp2.wanadoo.co.uk [193.252.22.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AAAF43D58 for ; Sat, 4 Feb 2006 13:24:34 +0000 (GMT) (envelope-from robin@reportlab.com) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3103.me.freeserve.com (SMTP Server) with ESMTP id 20B311C00086 for ; Sat, 4 Feb 2006 14:24:33 +0100 (CET) Received: from [81.78.125.133] (modem-3461.hyena.dialup.pol.co.uk [81.78.125.133]) by mwinf3103.me.freeserve.com (SMTP Server) with ESMTP id 86CE41C00085 for ; Sat, 4 Feb 2006 14:24:32 +0100 (CET) X-ME-UUID: 20060204132432552.86CE41C00085@mwinf3103.me.freeserve.com Message-ID: <43E4AB18.3000900@jessikat.fsnet.co.uk> Date: Sat, 04 Feb 2006 13:24:40 +0000 From: Robin Becker User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Invisible port 80 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2006 13:24:37 -0000 I am in the process of setting up a pair of freebsd 6.0 servers with different hosting services. On one of the servers I cannot seem to access the apache server which I have started. I can access port 80 on the machine itself using the machine IP address, but from my office port 80 seems invisible. The other machine works exactly as expected. Can anyone suggest something simple that may be causing this? So far I have only been using ssh to communicate with the machine so perhaps have neglected some network setting etc etc. -- Robin Becker