From owner-freebsd-gnome@FreeBSD.ORG Sat Nov 15 01:41:27 2003 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FA4516A4CE for ; Sat, 15 Nov 2003 01:41:27 -0800 (PST) Received: from bgruber.isa-geek.com (pool-151-204-142-146.ny325.east.verizon.net [151.204.142.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB02343F93 for ; Sat, 15 Nov 2003 01:41:25 -0800 (PST) (envelope-from lists@bgruber.isa-geek.com) Received: from bgruber.isa-geek.com (localhost [127.0.0.1]) by bgruber.isa-geek.com (8.12.9/8.12.9) with ESMTP id hAF9faVD071957 for ; Sat, 15 Nov 2003 04:41:36 -0500 (EST) (envelope-from lists@bgruber.isa-geek.com) Received: (from lists@localhost) by bgruber.isa-geek.com (8.12.9/8.12.9/Submit) id hAF9faj7071956 for freebsd-gnome@freebsd.org; Sat, 15 Nov 2003 04:41:36 -0500 (EST) Date: Sat, 15 Nov 2003 04:41:36 -0500 From: Brian Gruber To: freebsd-gnome@freebsd.org Message-ID: <20031115094136.GA71930@bgruber.isa-geek.com> Mail-Followup-To: freebsd-gnome@freebsd.org References: <20031115010547.GA32276@calvin> <1068879491.14636.1.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1068879491.14636.1.camel@shumai.marcuscom.com> User-Agent: Mutt/1.4.1i Subject: Re: gaim file transfer X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2003 09:41:27 -0000 > File transfers should work just fine on FreeBSD provided you're not > behind a firewall that might be blocking high TCP ports or NAT'ing. So it works fine for you (i know it should work fine)? I /am/ doing NAT behind a firewall, and I had also thought that might be the problem. The fact remains though that the same computer behind the same firewall does not have this problem under linux. I begin to think that maybe it's a network configuration thing or something... thanks for the input. brian