Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!umd5!umbc3!thierbac From: thierbac@umbc3.UMD.EDU (Ed Thierbach ) Newsgroups: comp.os.vms Subject: Re: Thoughts On Why Only Some Systems Perform Terminal Server Load Function Message-ID: <1067@umbc3.UMD.EDU> Date: 8 Jul 88 18:42:25 GMT References: <8806161751.AA22557@linc.cis.upenn.edu> Reply-To: thierbac@umbc3.UMD.EDU (Ed Thierbach) Organization: University of Maryland, Baltimore County Lines: 20 Many thanks to Paul Clayton for his help with DECserver loading, and for the Ethernet packet types (those will come in handy for filtering later). After he sent his reply, I checked into things and foud two items of interest: 1) Service was not enabled in the DECnet databases of all machines; I fixed that one. 2) DECserver 200 software version 2.0 has added a new parameter to DSVCONFIG: @DSVCONFIG SET_CIRCUIT, which will allow you to have a central DECserver database stored in SYS$COMMON:[DECSERVER], and then set the proper service circuit name for each node in the cluster. For example, if the service circuit is stored as UNA-0 in DSVCONFIG,DAT, you can use @MOM$LOAD:DSVCONFIG SET_CIRCUIT BNT-0 to set the proper circuit ID for your BI-based machines. Thanks again! -Ed Thierbach- -Roy F. Weston, Inc.-