Xref: utzoo comp.dcom.lans:2106 comp.periphs:1365 comp.terminals:998
Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!cornell!uw-beaver!blake!oregon!jqj
From: jqj@oregon.uoregon.edu (J Q Johnson)
Newsgroups: comp.dcom.lans,comp.periphs,comp.terminals
Subject: Re: Terminal Servers? (problems with Bridge)
Message-ID: <109@oregon.uoregon.edu>
Date: 14 Dec 88 10:29:48 GMT
References: <147@iquery.UUCP> <12380@cup.portal.com> <689@hscfvax.harvard.edu> <480@mmlai.UUCP> <Dec.14.10.40.26.1988.112@ron.rutgers.edu>
Organization: University of Oregon
Lines: 14

In article <Dec.14.10.40.26.1988.112@ron.rutgers.edu>, ron@ron.rutgers.edu
(Ron Natalie) writes:
> Both Bridge and Cisco terminal servers will boot either from themselves
> (Bridge uses a floppy, cisco uses roms (look ma! no moving parts) or over
> the network.
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.). 
Furthermore, the boot server must be on the SAME XNS NETWORK, normally
the same Ethernet, as the terminal server.  In contrast, Cisco and Annex
terminal servers can boot themselves from any network node that supports
tftp on tcp/ip, even across tcp/ip gateways. 

This is a very substantial restriction on the Bridge servers in a typical
complex internet.