dave@oldcolo.UUCP (Dave Hughes) (03/22/90)
What is the best solution to the following: A Xenix 2.2.2 386 box sitting next to a Unix 3.2 386, which they desire to link together with an Ethernet thin wire board and TCP/IP. But a desire to *also* link the Unix 3.2 box to a Vax with Ethernet thin wire and TCP/IP. What would this entail? Two ethernet boards in the Unix 386, one connected to the other 386 and one to the Vax? Will the TCP/IP software handle that? Or wil ethernet boards for 386s permit multiple thin wire connections?
itkin@mrspoc.Transact.COM (Steven M. List) (03/26/90)
dave@oldcolo.UUCP (Dave Hughes) writes: >What is the best solution to the following: A Xenix 2.2.2 386 box >sitting next to a Unix 3.2 386, which they desire to link together >with an Ethernet thin wire board and TCP/IP. But a desire to >*also* link the Unix 3.2 box to a Vax with Ethernet thin wire >and TCP/IP. >What would this entail? Two ethernet boards in the Unix 386, one >connected to the other 386 and one to the Vax? Will the TCP/IP >software handle that? Or wil ethernet boards for 386s permit >multiple thin wire connections? GACK! Sorry, Dave, didn't mean to be insulting. Ethernet is Ethernet is Ethernet. If you have your 386 connected with thin Ethernet, then anything else on that network is connected. No need for other boards or special setups. You need to idenify the VAX just like you would identify any other system on the network, but once done it is just another node. No multiple connections, please! This is NETWORKING, not serial ports! -- +----------------------------------------------------------------------------+ : Steven List @ Transact Software, Inc. :^>~ : : Chairman, Unify User Group of Northern California : : {apple,coherent,limbo,mips,pyramid,ubvax}!itkin@guinan.Transact.COM :
lws@comm.wang.com (Lyle Seaman) (03/27/90)
dave@oldcolo.UUCP (Dave Hughes) writes: >What is the best solution to the following: A Xenix 2.2.2 386 box >sitting next to a Unix 3.2 386, which they desire to link together >with an Ethernet thin wire board and TCP/IP. But a desire to >*also* link the Unix 3.2 box to a Vax with Ethernet thin wire >and TCP/IP. >What would this entail? Two ethernet boards in the Unix 386, one >connected to the other 386 and one to the Vax? Will the TCP/IP >software handle that? Or wil ethernet boards for 386s permit >multiple thin wire connections? one wire, three machines, three interfaces. ethernet is _not_ point- to-point. There's only one thin wire connection per board, but it's a broadcast medium. -- Lyle Wang lws@comm.wang.com 508 967 2322 Lowell, MA, USA uunet!comm.wang.com!lws