From owner-freebsd-questions Thu Feb 24 17:44:30 2000 Delivered-To: freebsd-questions@freebsd.org Received: from funky.monkey.org (funky.monkey.org [63.77.239.13]) by hub.freebsd.org (Postfix) with ESMTP id 2AFF937BAA3 for ; Thu, 24 Feb 2000 17:44:24 -0800 (PST) (envelope-from chester@monkey.org) Received: by funky.monkey.org (Postfix, from userid 1114) id CD48B151C7; Thu, 24 Feb 2000 20:42:00 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by funky.monkey.org (Postfix) with ESMTP id 94DD214A01; Thu, 24 Feb 2000 20:42:00 -0500 (EST) Date: Thu, 24 Feb 2000 20:42:00 -0500 (EST) From: Chester Kustarz 2 To: Mauricio Marquez Cc: freebsd-questions@freebsd.org Subject: Re: Networking(ARP) problem with FreeBSD 3.4 In-Reply-To: <3.0.32.20000224184717.011c6c10@enlace.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the suggestion -- it worked! I swapped out my mx PCI ethernet card and replaced it with a NE2000 isa card and it seems to work fine (after changing ifconfig settings of course to match the new card).=20 On Thu, 24 Feb 2000, Mauricio Marquez wrote: > We had a similar problem on an NT server. ARP problems normally have to d= o > with bad cables, NIC=B4s and/or Hubs/Switches. >=20 > We changed our switch and cables without success. We then changed the NIC > to a new one, same brand and model: big mistake, no success. Finally > changed to a different brand/model of NIC and problem was solved. >=20 > Just wanted to share our experience. >=20 > Mauricio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message