From owner-freebsd-net Mon May 11 12:59:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10098 for freebsd-net-outgoing; Mon, 11 May 1998 12:59:26 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from clutch.accrue.com (mail.accrue.com [207.86.139.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10080 for ; Mon, 11 May 1998 12:59:09 -0700 (PDT) (envelope-from andy@accrue.com) Received: from seatbelt.accrue.com (seatbelt.accrue.com [207.86.139.217]) by clutch.accrue.com (8.8.7/8.8.5) with ESMTP id MAA18104 for ; Mon, 11 May 1998 12:59:09 -0700 (PDT) Received: from accrue.com (localhost.accrue.com [127.0.0.1]) by seatbelt.accrue.com (8.8.5/8.8.5) with ESMTP id MAA00374 for ; Mon, 11 May 1998 12:56:49 -0700 (PDT) Message-ID: <35575801.985C55ED@accrue.com> Date: Mon, 11 May 1998 12:56:49 -0700 From: Andrew Sharp Organization: Accrue Software X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Re: home network References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm going to jump in here and add another cook. Hopefully I won't make a complete fool of meeself. It seems that the software is "working" on both systems, as the pings to x.x.1.1 would seem to indicate. so the problem is that the two systems can't actually see each other: ie., a hardware problem. start checking hardware-related stuff: are the drivers on both systems capable of auto-detecting/setting media types? are either of the cards not in auto-media mode and hard-configured for TP or AUI/thick-net or somesuch? perhaps one or more of the cards is sufficiently old that it doesn't even have the capability of auto-media-ing, and has to be configured to one media or another using some utility. do the cards in question have link-leds? check them to see that they are on. do you have more than one cable/terminator(s) that you can switch around to see if one or more is bad? where did you get the cable? it needs to be the right impedence...ie., leftover cable from when the TV cable installation guy was there won't work. Just kidding. It IS a home network... are the cards known good? I've had more than one "it's just dead" ISA networking card from 3com in my day. if you've got diagnostics, try them. you can put a terminator on both ends of the t-conn and do card/loopback diags. on the freeBSD box, arp -a should say something about both the dos and bsd interfaces on your network. if it just returns w/ no output, your arp is worse than your byte. sorry. if arp -a gives no output, then it seems to me that your hardware link isn't working. a Richard Wackerbarth wrote: > > At 10:21 PM -0500 5/10/98, Arnold J. Rimmer wrote: > >> But the "ping" of interest is ping 192.168.1.2 > > >ping 192.168.1.2 from windoze box results: > >timed out > > > >ping 192.168.1.1 from freebsd box results: > >PING 192.168.1.1 (192.168.1.1) 56 data bytes: > >ping: send to: Host is down > >ping: wrote 192.168.1.1 64 chars, ret=-1 > > :-( > I thought that the netmask was the culprit. > > To recap: > On the FreeBSD box, > ifconfig -a > netstat -rn > arp -a > > On the windoze box, > (anything that you can provide) > > Richard Wackerbarth > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message