|
thanks for the quick repsonse...I was unable to get to the machine for a
week...
here's the output you asked for
output of ping
ping: sendto:operation not performed
ping: wrote: 202.186.1.10 64 chars, ret=-1
output of route -n
Kernel IP routing table
Destination
Gateway
Genmask Flags Metric
Ref Use Iface
202.186.1.0
0.0.0.0
255.255.255.0
U 0
0 1 eth0
127.0.0.0
0.0.0.0
255.0.0.0
U 0
0 1 lo
0.0.0.0
202.186.1.50
0.0.0.0
UG 1
0 0 eth0
arp -an
?(202.186.1.10) at <incomplete> on eth0
output of ifconfig
lo Link encap:Local
Loopback
inet
addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST
LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:8
errors:0 dropped:0 overruns:0 frame:0
TX packets:8
errors:0 dropped:0 overruns:0 carrier:0
Collisions:0
eth0 Link encap:Ethernet HWaddr
00:10:5A:09:26:63
inet
addr:202.186.1.65 Bcast:202.186.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING
MULTICAST MTU:1500 Metric:1
RX packets:0
errors:0 dropped:0 overruns:0 frame:0
TX packets:9
errors:0 dropped:0 overruns:0 carrier:0
Collisions:0
Interrupt:10 Base
address:0xfc00
-------- Original Message --------
Subject: Re: Network problems with Vortex Adapter Date: Sat, 17 Apr 1999 10:35:56 -0700 (PDT) From: George Bonser <grep@shorelink.com> Reply-To: grep@oriole.sbay.org To: Karl Gordon <karlos@cybervale.com> CC: debian-user@lists.debian.org On Sat, 17 Apr 1999, Karl Gordon wrote: > Hi > I'm running Hamm on a Micron Millenia XKU 333 with a 3Com Etherlink 905B > PCI installed. > > The kernel is configured with the correct Vortex driver but the adapter > does not connect with or even see the other machines on the network. It > has the correct IP address and can 'ping' itself but no other machine > can ping it or vice versa. > I tried moving it around in the machine but that doesn't work either. I > down loaded the latest version of the driver and re-compiled the kernel > and nothing. > Which kernel version are you using. What is the output of arp -an after you have attempted a ping. What are the output of ifconfig route -n |