Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!security!genrad!grkermit!masscomp!clyde!floyd!harpo!ihnp4!zehntel!hplabs!sri-unix!towson@amsaa From: towson%amsaa@sri-unix.UUCP Newsgroups: net.micro.cpm Subject: TAC news. Message-ID: <15644@sri-arpa.UUCP> Date: Tue, 17-Jan-84 11:29:42 EST Article-I.D.: sri-arpa.15644 Posted: Tue Jan 17 11:29:42 1984 Date-Received: Fri, 20-Jan-84 06:05:28 EST Lines: 64 From: David Towson (CSD) The following is provided for the benefit of those persons who can access MILNET TAC's. Dave Towson info-cpm-request@brl-vgr ----------------------------------------------------------------------------- Received: From Sri-Nic.ARPA by BRL via smtp; 16 Jan 84 19:51 EST Date: Mon 16 Jan 84 16:04:23-PST From: NIC Subject: All-Points Broadcast--TAC Login Procedures Sender: NIC@SRI-NIC To: ALL-POINTS: ; Reply-To: NIC@SRI-NIC The following message explains MILNET TAC Login. Users will encounter the need for this information as of Midnight tonight EST. These instructions are also available through all MILNET/ARPANET TAC's as a menu item in the TACNEWS system, which is accessible via the "@n" command. Note that ARPANET users will be unaffected at present, unless they use a MILNET (Defense Data Network) TAC to access their ARPANET host. Please broadcast these TAC Login procedures to all of your MILNET TAC users. As announced in DDN Newsletter No. 35, the Universal UserID procedure will be in effect 17 January through 15 February, after which individual UserIDs will be necessary. ===================================================================== The access control system for MILNET (Defense Data Network) TAC's requires you to login before connections may be opened. The login process is automatically started with the first "@open" ("@o") command you issue. There is also a new "@logout" ("@l") command to logout. Otherwise, the functioning of the TAC is unaffected by the access control system. Here is a sample of the login dialog (user input is underlined): a) PVC TAC 110 #:01 b) @o 26.2.0.8 ----------- c) TAC Userid: TAC.LOGIN ---------- d) Access Code: 22ockedc2 (Does not echo.) ---------- e) Login OK f) TCP trying...Open In the above example, the TAC prints its greeting (a). The user proceeds to give the command to open a connection to host 26.2.0.8 (b). If you are used to using a host number with a slash in it, you may still use that form, i.e. "@o 2/8", as long as you are not going across networks. The TAC prompts for a TAC UserID. The user enters the Universal UserID which expires February 15, 1984 (c). The Access Code corresponding to the UserID is entered (d). After a brief wait, the TAC indicates that ***Error on net connection*** === brl-vgr netread error from amsaa at Tue Jan 17 11:43:49 ===