From owner-freebsd-questions Sat Dec 14 15:49: 3 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 B3E0C37B401 for ; Sat, 14 Dec 2002 15:49:00 -0800 (PST) Received: from neptune.he.net (neptune.he.net [216.218.166.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40FA743EB2 for ; Sat, 14 Dec 2002 15:49:00 -0800 (PST) (envelope-from fluid@sfmidimafia.com) Received: from sfmidimafia.com (12-232-218-189.client.attbi.com [12.232.218.189]) by neptune.he.net (8.8.6/8.8.2) with ESMTP id PAA09074; Sat, 14 Dec 2002 15:49:04 -0800 Message-ID: <3DFBC464.2090400@sfmidimafia.com> Date: Sat, 14 Dec 2002 15:53:08 -0800 From: "Scott R." User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joe Gwozdecki Cc: freebsd-questions@freebsd.org Subject: Re: natd mostly working but not quite... References: <3DFBB421.2050300@sfmidimafia.com> <00b301c2a3c2$eb689dc0$0300000a@lyon> <3DFBBA59.6060200@sfmidimafia.com> <00e101c2a3c7$fdcd3a20$0300000a@lyon> In-Reply-To: <3DFBB421.2050300@sfmidimafia.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 I honestly don't think that is the case. I had this same setup working at my other house and I have this same setup working at work with more than 30 PC's. The differences are: the service providers are different and all are/were running FreeBSD 4.6.2-RELEASE and this one is running 4.7-RELEASE. If the Windows clients were not configured correctly, they wouldn't get anything at all (speaking from past experience). -Scott Joe Gwozdecki wrote: > Your TCP/IP settings in the Windows boxes are not configured correctly. > > FreeBSD gateway box is working as it should but it can't talk 100% > to the > Windows boxes. There is nothing wrong with the DSL modem, outside > connection, long distance carrier, etc, or the FreeBSD gateway box, > if it is > operating perfectly to the internet. > > Joe Gwozdecki > Houston, TX > > > ----- Original Message ----- > From: "Scott R." > To: "Joe Gwozdecki" > Cc: > Sent: Saturday, December 14, 2002 5:10 PM > Subject: Re: natd mostly working but not quite... > > > > >The gateway machine is running FreeBSD 4.7-RELEASE and the other > two are > >running WinXP and Win2000 respectively. > > > >-Scott > > > >Joe Gwozdecki wrote: > > > > > >>What is the OS you are running on the 3 operating systems? Is it > >>FreeBSD also or something else? > >> > >>Joe Gwozdecki Houston, TX > >> > >> > >>----- Original Message ----- From: "Scott R." To: Sent: Saturday, > >>December 14, 2002 4:43 PM Subject: natd mostly working but not > >>quite... > >> > >> > >> > >> > >>>[note: please cc me in any replies as I am not currently subscribed > >>>to freebsd-questions. Thank you.] > >>> > >>>I'm using a FreeBSD 4.7-RELEASE box as a gateway for my household > >>>network (3 machines total). I'm using natd + ipfw + DHCP. It > >>>works mostly as it should (i.e. the other two boxes are able to > >>>connect to the internet as expected), but there are some > >>>inconsistencies. For example, if I go to Yahoo! and look up a map, > >>>I get a "The connection was refused while attempting to contact > >>>rd.yahoo.com" message when I try to zoom in. This does not happen > >>>from the FreeBSD box itself (everything works perfectly normally on > >>>this box). Also, those wonderful ads embedded in many web pages do > >>>not come up due to similar "connection refused" messages. This > >>>leads me to believe that something is not translating but I'm not > >>>sure what it could be. I tried disabling the firewall completely > >>>and that brought no change to this odd behavior. I tried bypassing > >>>DHCP by setting everything statically, but the behavior was still > >>>the same. > >>> > >>>At my last apartment, I was running FreeBSD 4.6.2-RELEASE as the > >>>firewall OS and everything worked just fine. Has something changed > >>>in 4.7 that might cause this behavior? Or, could this just be an > >>>oddity when dealing with AT&T Broadband (I had Sprint at the other > >>>place). > >>> > >>>I'm not sure what information might be required to try and > >>>debug/diagnose this so more info is available upon request. Any > >>>and all ideas will be greatly appreciated! Thanks in advance. > >>> > >>>-Scott > >>> > >>> > >>>To Unsubscribe: send mail to majordomo@FreeBSD.org with > >>>"unsubscribe freebsd-questions" in the body of the message > >> > >> > >> > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message