From owner-freebsd-questions@FreeBSD.ORG Tue May 13 17:22:25 2003 Return-Path: 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 EB6BD37B401 for ; Tue, 13 May 2003 17:22:25 -0700 (PDT) Received: from Gina.esfm.ipn.mx (esfm.ipn.mx [148.204.102.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBA4943F85 for ; Tue, 13 May 2003 17:22:24 -0700 (PDT) (envelope-from mrspock@esfm.ipn.mx) Received: from Gina.esfm.ipn.mx (localhost [127.0.0.1]) by Gina.esfm.ipn.mx (8.12.6p2/8.12.6) with ESMTP id h4E0MLvM035957; Tue, 13 May 2003 19:22:21 -0500 (CDT) (envelope-from mrspock@esfm.ipn.mx) Received: from localhost (mrspock@localhost)h4E0MLPF035954; Tue, 13 May 2003 19:22:21 -0500 (CDT) X-Authentication-Warning: Gina.esfm.ipn.mx: mrspock owned process doing -bs Date: Tue, 13 May 2003 19:22:21 -0500 (CDT) From: Eduardo Viruena Silva To: Jim Arnold In-Reply-To: Message-ID: <20030513191905.D34161@Gina.esfm.ipn.mx> References: <1052864431.319.55.camel@gyros> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: questions@freebsd.org Subject: Re: netatalk: Mac or BSD problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2003 00:22:26 -0000 On Tue, 13 May 2003, Jim Arnold wrote: > At 6:20 PM -0400 5/13/03, Joe Marcus Clarke wrote: > >On Tue, 2003-05-13 at 08:20, Jim Arnold wrote: > >> > > When I do type in my login and password I get the evil spinning > >> > > beachball that will not go away without a force quit. All of this > >was > >> >> working fine for a few weeks after going to 10.2.6 on the Mac. > >> > > >> >Can you get a sniffer trace with ethereal or tcpdump? > >> > >> Attached is a tcpdump of my network card on the offending BSD box. > > > >I was looking for a _binary_ capture as the headers themselves don't do > >my any good. The best way to run tcpdump is: > > > >tcpdump -w /tmp/outfile -s 1518 host mac.client.addr > > > >Then send me the outfile. > > > Joe, > > I hope I did this correctly. > > Thanks, > Jim Somedays ago we had the same strange behaviour in our systems. The problem was a Windows XP box that had got a virus. Running tcpdump let us detect which computer had the problem.