Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site mtxinu.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!genrad!panda!talcott!harvard!seismo!lll-crg!dual!unisoft!mtxinu!ed From: ed@mtxinu.UUCP (Ed Gould) Newsgroups: net.dcom,net.lan Subject: Re: Ethernet compatability Message-ID: <458@mtxinu.UUCP> Date: Tue, 10-Sep-85 12:15:38 EDT Article-I.D.: mtxinu.458 Posted: Tue Sep 10 12:15:38 1985 Date-Received: Sat, 14-Sep-85 06:05:44 EDT References: <391@brl-sem.ARPA> Reply-To: ed@mtxinu.UUCP (Ed Gould) Distribution: net Organization: mt Xinu, Berkeley, CA Lines: 23 Xref: watmath net.dcom:1287 net.lan:1019 In article <391@brl-sem.ARPA> jcp@brl-sem.ARPA (Joe Pistritto ) writes: > Having heard some horror stories about compatability between >components, does anyone have and of the DEUNA/DECNA/DEQNA Ethernet >controllers operating thru 3com transcievers out there? The DEC devices are Ethernet 2 (compatible with IEEE 802.3), while the 3Com transcievers are Ethernet 1. They're compatible on the ether side, but not on the device side (i.e., you can mix 3Com's and others on the same Ethernet, but you can't match a 3Com transciever to a DEUNA). On the other hand, I've never had any real problems with stinger-tap transcievers, except when a customer tried to connect one to a cheapernet, and since they didn't have any yellow thick cable, they just cut the thin cable and soldered it to the transciever! What a disaster! (The worst of it was that they wouldn't believe me when I told them that that was the problem.) -- Ed Gould mt Xinu, 2910 Seventh St., Berkeley, CA 94710 USA {ucbvax,decvax}!mtxinu!ed +1 415 644 0146 "A man of quality is not threatened by a woman of equality."