From owner-freebsd-questions@FreeBSD.ORG Mon Jun 27 10:59:02 2005 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 3EC7A16A41C for ; Mon, 27 Jun 2005 10:59:02 +0000 (GMT) (envelope-from gerard-seibert@suscom.net) Received: from smtp4.suscom.net (smtp4.suscom.net [64.78.119.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA0B743D1F for ; Mon, 27 Jun 2005 10:58:59 +0000 (GMT) (envelope-from gerard-seibert@suscom.net) Received: from localhost (unknown [127.0.0.1]) by smtp4.suscom.net (Postfix) with ESMTP id 484ED150120; Mon, 27 Jun 2005 06:58:58 -0400 (EDT) Received: from smtp4.suscom.net ([127.0.0.1]) by localhost (smtp4.suscom.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25171-05-52; Mon, 27 Jun 2005 06:58:56 -0400 (EDT) Received: from [192.168.0.3] (ip148.217.susc.suscom.net [216.45.217.148]) by smtp4.suscom.net (Postfix) with SMTP id DC4FB150059; Mon, 27 Jun 2005 06:58:55 -0400 (EDT) Date: Mon, 27 Jun 2005 06:59:00 -0400 From: Gerard Seibert To: John Brooks Sender: Gerard@smtp4.suscom.net, Seibert@smtp4.suscom.net In-Reply-To: References: Message-Id: <20050627065648.529E.GERARD-SEIBERT@suscom.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Mailer: Becky! ver. 2.21.03 [en] X-Virus-Scanned: amavisd-new at suscom.net Cc: FreeBSD Question Subject: Re[2]: Still trying to get my site up! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gerard-seibert@suscom.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2005 10:59:02 -0000 On Sunday, June 26, 2005 8:47:41 PM "John Brooks" wrote: $>do you have any kind of firewall? from the outside world port 9545 $>is closed. so either it is being blocked, you are not actually $>listening on it, or there is no port forwarding on your gateway. $> $>run this on the box itself and post the output: $> netstat -na | grep LISTEN $> $>try to connect from another host on your network: $> http://192.168.0.4:9545 $> $>then try: $> http://192.168.0.4:80 $> $>-- $>John Brooks $>john@day-light.com $> $>> -----Original Message----- $>> From: owner-freebsd-questions@freebsd.org $>> [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Gerard Seibert $>> Sent: Sunday, June 26, 2005 6:07 PM $>> To: freebsd-questions $>> Subject: Still trying to get my site up! $>> $>> $>> Thanks to several individuals, I have almost gotten my Apache2 server $>> working. Almost, but not quite. $>> $>> My ISP blocks port 80; therefore I am using a redirect from DynDNS.org to $>> redirect to an alias using port 9545. $>> $>> The 'beerstud.us' redirects to 'www2.beerstud.us:9545' $>> $>> >From my FreeBSD box, if I type: lynx http://beerstud.us, I see the $>> following message: Using http://www2.beerstud.us:9545/. The connection is $>> made and the index.htm file is displayed. $>> $>> However, I am unable to reach this site from any other computer. $>> Eventually, the request will time out and I receive an error message $>> telling me that the site is not available. $>> $>> I am not sure what I am doing wrong at this point. I have posted the $>> following files if anyone feels ambitious enough to look them over for me. $>> $>> httpd.conf = http://www.seibercom.us/FreeBSD/httpd.conf $>> $>> hosts = http://www.seibercom.us/FreeBSD/hosts $>> $>> This is the output from ifconfig -a $>> net-card.txt = http://www.seibercom.us/FreeBSD/net-card.txt $>> $>> resolv.conf = http://www.seibercom.us/FreeBSD/resolv.conf $>> $>> The 'hosts' file has a pretty good description of my network in it. I $>> double checked my router, and I believe it is configured $>> correctly to pass $>> port 9545 through. $>> $>> -- $>> Thanks! $>> $>> Gerard Seibert $>> Gerard-seibert@suscom.net $>> ********** Reply Separator ********** Monday, June 27, 2005 6:48:35 AM The netstat -na | grep LISTEN command produces this output: tcp4 0 0 *.139 *.* LISTEN tcp4 0 0 *.445 *.* LISTEN tcp4 0 0 *.901 *.* LISTEN tcp46 0 0 *.9545 *.* LISTEN tcp4 0 0 127.0.0.1.25 *.* LISTEN Both http://192,168.0.4:9545 goes to my site. The http://192.168.0.4:80 produces this error: Looking up 192.168.0.4 Making HTTP connection to 192.168.0.4 Alert!: Unable to connect to remote host. lynx: Can't access startfile http://192.168.0.4/ -- Gerard E. Seibert gerard-seibert@suscom.net