Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!wuarchive!psuvax1!psuvm!VAXB!MOLTA From: MOLTA@VAXB.ACS.UNT.EDU Newsgroups: bit.listserv.novell Subject: Re: ETHERNET PROBLEM Message-ID: Date: 1 Feb 90 13:57:00 GMT Sender: Novell LAN Interest Group Reply-To: Novell LAN Interest Group Lines: 22 Approved: NETNEWS@PSUVM Gateway X-VMS-To: IN%"NOVELL%SUVM@pucc.PRINCETON.EDU" X-To: NOVELL%SUVM@pucc.PRINCETON.EDU >This is taken from "International Standard, ISO 8802-3, ANSI/IEEE Std >802.3, First edition 1989-02-24", Section 10 on Type 10BASE2. Under >10.7.2 Transmission System Requirements, "In order to maintain reflections >at an acceptable level, the minimum length cable section shall be 0.5m." Thanks for the authoritative answer. Does this mean that there needs to be a .5m stub tacked on to the last PC on a segment. We've been in the (possibly bad) habit of attaching a terminator directly to the T-connector on the last PC attached to an Ethernet segment. We haven't noticed any problems, but every once in a while, there are unsolved mysteries on our networks. I'd also be curious to hear about people's experiences in violating thin Ethernet cable distance restrictions, which officially call for segments of 200 meters (about 650 feet). There are several vendors, including 3Com, that claim to support segments of 1000 feet. While we try to keep within spec, I know we have several thinwire Ethernets on campus that are in the 700-800 ft. range. How far as anybody tried to push these limits? We've run RS-232 cable 1000 ft. at 9600 baud even though the spec says 50 ft. Is there any comparison? Dave Molta University of North Texas