Douglas, Brian and anyone else interested, dt> Can other boxes/NICs get 100 Mb/s across the AT hub? Perhaps the AT hub is only 10 Mb/s.
The AT-3612TR is one of earliest 12 port hubs on the market. It is 10base-T, half duplex; 100 Mb/s across it is out of the question. Clarification The question is not "why is communication across the AT-3612TR limited to 10 Mb/s?" but rather "why does communication fail without the the AT-3612TR acting as filter?" The Netgear hub supports 100 Mb/s on the upstream LAN connection and with a NetVista 6578-RAU using the original IBM NIC. As explained in a message to Brian, I've checked the cables. The problem is not a broken cable or use of a cross-over where a patch belongs. I have the original Belkin documentation. There is no mention of the significance of the three states of the light, red, amber, green. Considering the messages which spew to the console at times and the observation that the connection works when filtered by the AT-3612TR, my first guess is that the Belkin is not negotiating the link properly. I suppose that either the Belkin hardware or the Pegasus driver is at fault. A sample of the console messages is visible. http://carnot.yi.org/PegasusMessages.jpg The only meaning for me is that a bug report against the Pegasus driver might be in order. Thanks, ... Peter E. http://carnot.yi.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
