From owner-freebsd-questions Wed Dec 25 3:41:49 2002 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 0DB4A37B401 for ; Wed, 25 Dec 2002 03:41:47 -0800 (PST) Received: from shockwave.systems.pipex.net (shockwave.systems.pipex.net [62.241.160.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4509243EC2 for ; Wed, 25 Dec 2002 03:41:46 -0800 (PST) (envelope-from stacey@vickiandstacey.com) Received: from [192.168.1.8] (81-86-129-77.dsl.pipex.com [81.86.129.77]) by shockwave.systems.pipex.net (Postfix) with ESMTP id BAC4B16000F46; Wed, 25 Dec 2002 11:41:41 +0000 (GMT) Subject: Re: Refusing Connections From: Stacey Roberts Reply-To: stacey@vickiandstacey.com To: bbrummer@solar.com.br Cc: FreeBSD Questions , jimit@myrealbox.com In-Reply-To: References: Content-Type: text/plain; charset=ISO-8859-1 Organization: Message-Id: <1040816512.68500.26.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 25 Dec 2002 11:41:52 +0000 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 2002-12-25 at 11:03, Bernardo M. Brummer wrote: > If itīs a DSL or cable connection probably your provider has blocked the 80 > port. > In this case they are workarounds using (free) domain services. > > Bernardo > > > > OS - 5.0 RC2 > > Apache - 2.0.43 > > OpenSSL - 0.9.6g > > > > I'm having a rather odd problem and I can't quite put my finger on it. I > > can verify that the apache httpd is running but I am unable to connect to > > the box on port 80. > > I verified that httpd.conf specifies port 80. I've verified that the > > firewall is disabled. I can connect on other ports so I know that the > > network settings are working properly. If someone could point out what > > I'm missing, I'd really appreciate it. I have a feeling that it's going > to > > be a "DOH!" momemt. > > > > Thanks, > > > > Ms. Jimi Thompson > Hi, Sorry if I missed this from an earlier post, but a couple of questions. I presume that you're attempting to run a webserver that is accessible from the Internet, and you're trying to test it. As such:- 1] Where are you attempting to access the webserver *from*? 2] How are you trying to connect? You mentioned that you can connect on other ports, could you provide an example? The reasoning behind my questions, is the fact that if you are sitting on your local lan, and attempting to access the webserver as "www.your_web_server.com" in your browser, then unless you have local (read internal) name resolution on your lan, then you won't be able to connect. If you've got the webserver set up and running, a request from your internal site would take the following route (if you're attempting to connect via the method above): Your browser would attempt to resolve the www.your_web_site.com through whatever NS (from ISP?) entries you have in /etc/resolv.conf. Unless those NS's have records for your webserver, they won't be able to return any resource records to your browser. In the same vein, unless the box that the webserver is running on, actually knows its name to be www.your_web_site.com, then he won't know to answer requests at port 80 anyways. Hope this helps. Let me know if I've got your setup completely wrong as well :-) Regards, Stacey > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message