Problem with new Cyclone
    WHITE, KEVIN 
    kwhite@redroof.com
    Fri Oct 16 14:02:47 1998
    
    
  
>Hmmm, it looks like a routing problem.
I hope not...I tried everything I knew to verify that this wasn't the case
before I bothered the list...I didn't want to bug people with a problem
like that that I should be able to solve.  If it ends up being that, I
apologize in advance.  :)
>Perhaps its a problem with both machines having the same IP address?
They don't...two ports, 2 IP addresses...
>Try using 'route -n' to avoid the nameserver lookup.  (Note: Don't use the
>phrase "lock up" unless the machine actually freezes.)
OK, sorry...
Here's the original route -n:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.248.90.0     0.0.0.0         255.255.255.0   U     0      0        3 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         10.248.90.254   0.0.0.0         UG    0      0        2 eth0
My (working) notebook had one more entry, so I manually added it.  Here's
the new route -n:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.248.90.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        0 lo
10.0.0.0        10.248.90.254   255.0.0.0       UG    0      0        1 eth0
0.0.0.0         10.248.90.254   0.0.0.0         UG    0      0        0 eth0
Now, the notebook and PC have the same rouitng table.  
It still doesn't work.  The PC can't ping anything, and nothing can ping
it.  route without the -n just quits responding after the first 2
entries...same as before.
I guessed that if routing was broken, the notebook and PC should still at
least be able to see each other...they're on the same subnet.  Maybe I
should try a crossover cable between them?
>> Oct 15 16:46:06 kwhite kernel:   MII transceiver found at address 24,
>> status 786d.
>
>Good status -- you have link beat.
>
>> eth0      Link encap:Ethernet  HWaddr 00:10:5A:15:93:28
>>           inet addr:10.248.90.16  Bcast:10.248.90.255  Mask:255.255.255.0
>>           RX packets:8 errors:0 dropped:0 overruns:0
>>           TX packets:40 errors:0 dropped:0 overruns:0
>
>Everything looks peachy from the device driver viewpoint -- you are both
>sending and receiving packets!
That bothered me as well...I was receiving some.  I should see if they're
being rejected...
>>  MII PHY 0 at #0 transceiver registers:
>>    3000 786d 0000 0000 01e1 0020 0004 2001
>
>You are connected to a 10mbps repeater without autonegotiation.
That's correct...
Thanks for any help...is there a chance there's something weird in this
hardware?  I noticed the card is only 2 months old...
I might try a NetGear from home (real DEC Netgear...)
Kevin