From owner-freebsd-questions Tue Apr 24 20:28:13 2001 Delivered-To: freebsd-questions@freebsd.org Received: from shell.bchosting.com (shell.bchosting.com [64.69.68.35]) by hub.freebsd.org (Postfix) with ESMTP id 27ACC37B423 for ; Tue, 24 Apr 2001 20:28:11 -0700 (PDT) (envelope-from chris@selkie.org) Received: from localhost (chris@localhost) by shell.bchosting.com (8.11.0/8.11.0) with ESMTP id f3P3S5C30955; Tue, 24 Apr 2001 20:28:05 -0700 (PDT) (envelope-from chris@selkie.org) Date: Tue, 24 Apr 2001 20:28:05 -0700 (PDT) From: Chris Phillips X-Sender: chris@shell.bchosting.com To: Matthew Emmerton Cc: Dave VanAuken , freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD w 3C905 cannot connect to Cisco 3524XL switch In-Reply-To: <029a01c0cd32$06182b40$1200a8c0@gsicomp.on.ca> 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 I would have to agree with Matthew. I have about 80 boxes sitting behind a 3524XL-EN all using Intel cards and have never had a problem. I avoid most other cards, but 3COM cards I avoid like the plague. -Chris Phillips On Tue, 24 Apr 2001, Matthew Emmerton wrote: > > Sorry, forgot the follow bits of info... > > > > Using FreeBSD 4.2 Stable (about 3 weeks since last cvsup) no > > X or anything like that. PIII 500, 256mb or greater RAM, low > > load ( no load right now! :) > > > > Thanks > > Is it just this one server, or are there more? If it's just the one, and > given that FreeBSD reports "status: (no-carrier)", I'd be inclined to think > that you have a bad card and/or a bad cable and/or a dead port on the > switch. > > -- > Matt Emmerton > > > 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