Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!sun-barr!rutgers!cunixf.cc.columbia.edu!cs.columbia.edu!mail From: camargo@cs.columbia.edu (Kiko) Newsgroups: comp.sys.novell Subject: Finally, down to cables... Message-ID: Date: 26 May 91 22:32:53 GMT Reply-To: camargo@cs.columbia.edu Lines: 42 Hi there, Well, here we go again... We are ready to start deploying Thin-Ethernet cables in a 3-floor building, and I just came up with a few concerns that might not be relevant. In any case, here they are: . What is the minimal "T" cable drop, from a Thin-Ethernet to the NIC ? . Is is really advantageous to have the T-connectors in the NIC's themselves ? . What is the effect of using wall-plates with 2 BNC connectors, and each workstation connected to the ethernet with a T in the NIC ? Won't this arrangement easily exceed the "minimal number of connections" ? We are planning to run 6 sub-segments, each about 120 feet long, with 10 workstations in each (in average). They will be connected through a T-connector in the back of 3 NIC's in the file-server, thus yielding 3 actual segments. The realm of the question is: Should we put "T-connectors" inside the wall, or have the "T-connectors" in the workstations? While the "T-in-the-wall" solution is "cleanner", the "T-in-NIC" is more flexible, but adds to the number of connections in each segment. My knowledge of "Thin-Ethernet limit-values" calls for 30 connections, at most, in each segment, limit that will be easily exceed if we use the "T-in-NIC" solution. Is anybody out there to say that I'm wrong ? In case I'm not, how far away can a workstation be from a "T-in-the-wall" ? Well, thanks for any help. /Kiko camargcs.o@colbia.edu [Disc: To this date, I had experiences only with the "T-in-NIC" solution, in much more limited spaces. Thus, these questions were never an issue.]