Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 May 1998 12:56:49 -0700
From:      Andrew Sharp <andy@accrue.com>
To:        freebsd-net@FreeBSD.ORG
Subject:   Re: home network
Message-ID:  <35575801.985C55ED@accrue.com>
References:  <l03130300b17c16cabfc7@[208.2.87.10]> <l03130302b17c648a047f@[208.2.87.10]>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35575801.985C55ED>