From owner-freebsd-questions Mon Feb 22 23:43:51 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dsinw.com (dsinw.com [207.149.40.5]) by hub.freebsd.org (Postfix) with ESMTP id BEAC811003 for ; Mon, 22 Feb 1999 23:43:49 -0800 (PST) (envelope-from hamellr@dsinw.com) Received: (from hamellr@localhost) by dsinw.com (8.8.8/8.7.3) id XAA09123; Mon, 22 Feb 1999 23:39:26 -0800 (PST) Date: Mon, 22 Feb 1999 23:39:25 -0800 (PST) From: rick hamell To: Brad Benson Cc: freebsd-questions , Nick Faso Subject: RE: networking windows and freebsd In-Reply-To: <000e01be5ed7$88a13b40$6400a8c0@BillyJoeBob> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There are free proxy server apps for windows that my let you do it, but > I haven't a clue as to how to set up the FreeBSD side. it depends on the > Proxy server. I do know however that it's 100 times easy to go the other > way. Let FreeBSD handle the internet connection, and do your browseing > in windows. FreeBSD does a much better job handleing the connection, and > takes some load off the windows machine. You get better performance, less > lost connaections , and maybe even less Windows lockups. If that's possible. Check out www.winfiles.com or www.tucows.com for such a beast. BUT, having run both sides of the equation, setting up FreeBSD as the dial up server instead of Windows is much better in the long run. Granted, for me it was a bit hard at first diving directly into FreeBSD as I was, but since then my Windows machines have amazingly not crashed at all! Performace is easily twice as good, and I've yet to get a dropped carrier. Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message