Xref: utzoo comp.dcom.lans:2145 comp.periphs:1415 comp.terminals:1019 Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!rice!bcm!watson!sob From: sob@watson.bcm.tmc.edu (Stan Barber) Newsgroups: comp.dcom.lans,comp.periphs,comp.terminals Subject: Re: Terminal Servers? (problems with Bridge) Message-ID: <1357@gazette.bcm.tmc.edu> Date: 27 Dec 88 23:21:03 GMT References: <147@iquery.UUCP> <12380@cup.portal.com> <689@hscfvax.harvard.edu> <480@mmlai.UUCP> <109@oregon.uoregon.edu> Sender: usenet@bcm.tmc.edu Reply-To: sob@watson.UUCP (Stan Barber) Organization: Baylor College of Medicine, Houston, TX Lines: 21 In article <109@oregon.uoregon.edu> jqj@oregon.uoregon.edu (J Q Johnson) writes: >It should be noted that Bridge/3Com terminal servers can boot themselves >over the network only from a special-purpose boot node (NCS) running XNS >(even if you are using a TCP/IP or OSI version of the Bridge t.s.). This is incorrect. The NCS does NOT run XNS. I have an NCS/AT that runs TCP/IP just fine, thank you. >Furthermore, the boot server must be on the SAME XNS NETWORK, normally >the same Ethernet, as the terminal server. The must be on the same ETHERNET, not the same XNS network. If you have a large network that uses bridges or bridging routers, it all works. >This is a very substantial restriction on the Bridge servers in a typical >complex internet. I agree that the 3Com/Bridge boot system is not the best, but let's try to argue from accurate information. Stan internet: sob@bcm.tmc.edu Baylor College of Medicine Olan uucp: {rice,killer,hoptoad}!academ!sob Barber Opinions expressed are only mine.