I've been perplexed by this particular anomaly for a while, so I figured I'd ask and see if any of you know.
On almost all of my Old World G3s (beige DT/MT/AIO, WS/PDQ, not Kanga), the onboard 10bT Ethernet is collision city when used on a network with 100bT machines. I've used different switches/cables/computers, with the same result. Somebody said it was because 10bT is only half-duplex while 100bT is normally full-duplex, thus there are problems. I'd buy that except, no other beige machine has the same problems; I can use a 6100/60 (or my 540c, even) with its AAUI-10bT adapter, or my Mac II with a NuBus 10bT card, on a mixed network with no problems, but I plug in my WallStreet or G3MT, and it has more collisions than packets received. It doesn't quite explain why the Kanga works just fine, either...
More or less, I'm just curious to see if anybody else has noticed these issues or perhaps has a more plausible explanation or work-around.
On almost all of my Old World G3s (beige DT/MT/AIO, WS/PDQ, not Kanga), the onboard 10bT Ethernet is collision city when used on a network with 100bT machines. I've used different switches/cables/computers, with the same result. Somebody said it was because 10bT is only half-duplex while 100bT is normally full-duplex, thus there are problems. I'd buy that except, no other beige machine has the same problems; I can use a 6100/60 (or my 540c, even) with its AAUI-10bT adapter, or my Mac II with a NuBus 10bT card, on a mixed network with no problems, but I plug in my WallStreet or G3MT, and it has more collisions than packets received. It doesn't quite explain why the Kanga works just fine, either...
More or less, I'm just curious to see if anybody else has noticed these issues or perhaps has a more plausible explanation or work-around.


