Intel NICs, Cisco, autoneg, and borken-ness

Paul Lussier p.lussier at comcast.net
Mon Mar 13 13:00:04 EST 2006


klussier at comcast.net writes:

> Can you try more then just ping? Try tracerouting to another network
> to see where the traffic stops, or where it tries to go. 

If ping doesn't work, neither will traceroute, since the latter is
built using TTL tricks of the former.  Since I can't even ping the
gateway of the subnet I'm *on*, trying to get *off* net isn't going to
work either.

> Try using lynx to open a web page.

To what?  I can't even get off the network I'm on?

> Sometimes someone does something dumb on a router like disallowing
> ICMP, or, in Cisco's case, tuning on "ICMP-Helper", which I have
> seen to have the same effect as blocking ICMP (not very
> helpful...).

We checked the router/switch config several times.  It was configured
correctly (i.e. ICMP-helper and the like were not configured).

> Also, check the cable. You can have link light with but a single
> wire in a pair :-)

This turned out to be closer the to problem.  Bad wiring in the patch
panel between the switch and router.  Changing to a different port
worked just fine.

Thanks.
-- 

Seeya,
Paul



More information about the gnhlug-discuss mailing list