1. Manuals
  2. Brands
  3. SynOptics Manuals
  4. Server
  5. 3395
  6. Management manual

SynOptics 3395 Management Manual

Software management guide terminal server
Hide thumbs Also See for 3395:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Command Reference, Using Manual
Software Management Guide
for the Model 3395/3395A

Terminal Server

Supplement 5.2
SynOptics Communications, Inc.
4401 Great America Parkway
Santa Clara, CA 95052-8185
(408) 988-2400
893-763-A
July 1994

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 3395 and is the answer not in the manual?

Questions and answers

Related Manuals for SynOptics 3395

Summary of Contents for SynOptics 3395

  • Page 1: Terminal Server

    Software Management Guide for the Model 3395/3395A Terminal Server Supplement 5.2 SynOptics Communications, Inc. 4401 Great America Parkway Santa Clara, CA 95052-8185 (408) 988-2400 893-763-A July 1994...
  • Page 2 General License VDE 0871, Class B (AmtsblVfg No. 243/1991 and Vfg 46/1992) VCCI Class 1 ITE This supplement contains new pages and replacement pages for the Software Management Guide for the Model 3395/3395A Terminal Server, 893-158-C. Follow these instructions to add and replace pages in this manual: Replacement Pages...
  • Page 3 Software Management Guide for the Model 3395/3395A Terminal Server Version 5.2 SynOptics Communications, Inc. 4401 Great America Parkway Santa Clara, CA 95052-8185 (408) 988-2400 893-763-A July 1994...
  • Page 4 © 1994 by SynOptics Communications, Inc. All rights reserved. Trademarks SynOptics, SynOptics Communications, and LattisNet are registered trademarks of SynOptics Communications, Inc. Lattis System 3000 and SynOptics Press are trademarks of SynOptics Communications, Inc. Other brand and product names are registered trademarks or trademarks of their respective holders. Statement of Conditions In the interest of improving internal design, operational function, and/or reliability, SynOptics Communications, Inc.
  • Page 5 Preface Conventions xvi Ordering SynOptics Publications...xvii SynOptics Customer Support...xvii Chapter 1 - Introducing the Model 3395 Terminal Server Obtaining Operating Software and Parameters...1-2 Compatibility Issues...1-2 Terminal Server Software Management Tools ...1-3 Software Management Tools ...1-3 Standard DEC Software Installation and Management Tools ...1-3 Chapter 2 - Setting Up the Terminal Server Setting Up the Terminal Server...2-1...

  • Page 6: Table Of Contents

    Configuring a LAT Application Port at a VMS Host ...5-11 Modem Control Operation ...5-12 Device Types...5-12 Supported Modem Control Signals ...5-13 Information About Model 3395 Cabling Methods...5-13 Modem-Related PORT Characteristics...5-14 Server Modem Disconnect Sequence...5-16 Modem Control Signal Interaction...5-17 Using Signal Check...5-26 Flow Control ...5-27...
  • Page 7 Eliminating TFTP Broadcasts ...7-14 Saving Parameters in the Permanent Database...7-15 Dump Transmission ...7-15 Associated Commands...7-16 Using the Terminal Server as a Domain Name Server...7-16 Associated Commands...7-17 Configuring the Terminal Server to Use SLIP ...7-18 Terminal Server and Port Configuration...7-18 SLIP Sessions...7-20 Associated Commands...7-20...
  • Page 8 Helpful Displays...8-11 The SHOW|MONITOR SERVER COUNTERS Display ...8-11 The SHOW|MONITOR SERVER STATUS Display ...8-11 The SHOW|MONITOR SERVER ALTERNATE STATUS Display...8-13 Chapter 9 - Using Terminal Server Security Features Controlling Access to the Terminal Server ...9-1 Terminal Server Passwords...9-1 Privilege Levels ...9-3 The Kerberos Security System ...9-4...
  • Page 9 Associated Commands...11-7 Script File Execution and Processing ...11-7 Examples of Scripts...11-9 Chapter 12 - Model 3395 Support for the Xremote Protocol Terminal Server Support for Xremote Features...12-1 Starting Up the XDM Host...12-3 Configuring the Terminal Server for Xremote Support ...12-5 Enabling the Xremote Protocol on the Terminal Server ...12-5...
  • Page 10 A PC With No Configured Internet Address...13-11 Example of a Two-Node Configuration...13-13 Chapter 14 - Configuring Print Services for Novell Users Using Model 3395 Commands to Configure Novell Printing...14-2 Configuring a Port to Support Novell Printing...14-2 Viewing Available Novell Printer Servers ...14-3 Viewing Status of Xprinter Ports ...14-3...
  • Page 11 SecurID Client Features...20-1 SecurID Client Setup ...20-2 Configuring the SecurID Client at the UNIX Host...20-2 Install the Model 3395 Load Image Which Contains the SecurID Client ...20-2 Enable The Server SecurID Feature...20-3 Specify Server-Related SecurID Characteristics...20-3 Configure Ports To Require SecurID Authentication ...20-4 Chapter 21 - Setting Up ARAP ARAP Features...21-2...
  • Page 12 Modifying CCL Scripts for Macintosh Computers ...21-20 Basic Format of a CCL Script ...21-20 Modify a CCL Script ...21-22 Example Model 3395 CCL Extensions...21-23 Example of a Typical CCL Script ...21-26 Modifying Dial-Back Scripts for ARAP Ports...21-32 ARAP Planning Considerations...21-33 Appendix A - Shared Printer Source Code Sample UNIX Output Filter File...A-1...
  • Page 13 Figure 11-1. Example script server directory structure ...11-3 Figure 12-1. Conventional Xremote implementation ...12-2 Figure 12-2. An Xterminal connected to a System 3000 with a Model 3395 Terminal Server ...12-3 Figure 12-2. Font servers ...12-6 Figure 13-1. PPP single-node configuration ...13-2 Figure 13-2.
  • Page 14 Example SHOW|LIST XPRINTER PORTS display ...14-3 Figure 14-3 Example LIST|MONITOR|SHOW SERVER CHARACTERISTICS display...14-4 Figure 14-4. Network printing environments...14-6 Figure 15-1. A SERVER LOADDUMP characteristics display of a Model 3395 Terminal Server...15-1 Figure 18-1. A three-level menu structure...18-2 Figure 18-2. A sample menu...18-3 Figure 18-3.
  • Page 15 Table 2-1. Memory usage for Model 3395 Terminal Server features and protocols ...2-7 Table 3-1. Model 3395 Terminal Server commands and menu items ...3-8 Table 6-1. IBM display station functions ...6-4 Table 6-2. Screenmap actions...6-6 Table 6-3. Special values for escape sequences...6-8 Table 6-4.
  • Page 16 Chapter 11 Describes the Network Command Script feature, which provides the server manager with the ability to create a script file which contains one or more Model 3395 commands to be executed when the user logs in at a port.

  • Page 17: How To Set Up Shared Printers

    Provides listings of “template” C language shared printer filter programs, a BSD UNIX printcap file, and an AT&T UNIX System V interface file. Appendix B Lists OPCOM messages that may be displayed by the Model 3395 software, and describes the cause of the condition. Appendix C Summarizes the differences between Model 3395 software and the LAT software for a DECserver 200 terminal server unit.

  • Page 18: Ordering Synoptics Publications

    7. The following default user prompts will be shown (different prompt may be in use at your site): UNIX/ULTRIX UNIX/Ultrix Superuser Ordering SynOptics Publications To purchase additional copies of this document or other SynOptics® product publications, order by part number from SynOptics Press™ at the following numbers. You may also request a free catalog of SynOptics Press product publications.
  • Page 19 Preface Technical information is available from the SynOptics InfoFACTS fax-on-demand system by calling: • U.S. and Canada: 1-800-786-3228 • International: 408-764-1002 You can also access technical information in the SynOptics forum on CompuServe. For information about our education services, contact the SynOptics Training Coordinator at 1-800-473- 4911 or 408-764-1018.

  • Page 20: Chapter 5 - Setting Up Modems

    This chapter describes how to configure the terminal server to support several different types of modems. It also describes how modem control operates. You can use this information for trouble shooting. This chapter includes information about the following topics: •...
  • Page 21 <Return> key a few times at initialization time. For the terminal server to use the autobaud feature, however, the modem must use 8-bit no parity or 7-bit even parity characters. If the characters cannot be set to 8-bit no parity or 7-bit even parity, you must disable the PORT AUTOBAUD characteristic and individually set the PORT SPEED, CHARACTER SIZE, and PARITY characteristics to the appropriate values.

  • Page 22: Setting Up Dial-Back Modems

    The Model 3395 Terminal Server software dial-back feature uses the network command script feature. The commands are contained in a file, called a script file, which is stored at a host called a script server. The script server can be a host system that supports the Trivial File Transfer Protocol (TFTP). See Chapter 11 for more information about creating scripts.

  • Page 23: Configuring Port Characteristics

    The modem must use 8-bit no parity or 7-bit even parity characters for the terminal server to use this feature, however. If the characters cannot be set to 8-bit no parity or 7-bit even parity, you must disable the port autobaud feature, and set the PORT SPEED, CHARACTER SIZE, and PARITY characteristics to the appropriate values.

  • Page 24: Setting Up A Dial-Back Script Server

    DEFINE SERVER PROTOCOL LAT TELNET ENABLED.) Define an Internet-address and optionally a domain name. b. Set up directories to contain script files at each script server. For a UNIX host script server, you need to consider the TFTP guidelines in the next section, as well.
  • Page 25 At the UNIX host or PC, use a text editor to create the script file, which contain the instructions that permit the server to dial-back to another modem. The name of file is dialback. At a UNIX host the file name must consist of all lower-case letters (login or dialback).

  • Page 26: Script File Structure And Guidelines

    In a dial-back script, the pound character, when followed by the word modem and one or more spaces, specifies a modem command that the server will pass on to a modem. The phrase "#modem" must be in lower case letters.
  • Page 27 1. The user attempts to log on to a dial-back port. The user specifies a username when the Enter Username> prompt appears. The terminal server immediately disconnects the telephone connection. The terminal server uses the port username to locate the script file and to reauthenticate the user and the port speed.

  • Page 28: Setting Up A Dial-Out Modem

    Step 1, or the port is logged out and the connection is dropped. If the port is set up to use or require a login script, the server unit requests and executes this script.
  • Page 29 To set up a LAT local service, you must use SET|DEFINE SERVICE commands to specify service characteristics, as well as the SET|DEFINE PORT commands to specify appropriate port characteristics. For example, to define a printer service named PRINT, at port 1 of the server, you would use a command such as: TS3395>>...

  • Page 30: Configuring A Lat Application Port At A Vms Host

    TS3395>> define port 10 telnet remote port 3600 A user at a PC whose serial port is connected to a server port, can then connect to the local service while running Kermit or a similar program. A user at a host that uses Internet Protocols, such as a UNIX host, would connect to the server Internet address/Telnet remote port or domain name/Telnet remote port while running Kermit, FTP, etc.

  • Page 31: Modem Control Operation

    There are two types of devices: Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE). Ports on Model 3395 Terminal Servers are considered DTE devices. Typically, terminals are DTE units, and modems (or equivalent) are DCE units.

  • Page 32: Supported Modem Control Signals

    Supported Modem Control Signals The following are the modem control signals that can be asserted or observed by the Model 3395 Terminal Server hardware, and the Model 3395 Terminal Server software port characteristics that control these signals: Signal Name Using the DTR and DCD signal lines for modem control precludes their use as hardware flow control signal lines.

  • Page 33: Modem-Related Port Characteristics

    Model 3395 Terminal Server software supports several characteristics that control the interaction of modem control signals that are available on Model 3395 Terminal Server hardware. The following are the PORT characteristics that affect modem control operation through DEFINE|SET PORT commands:...
  • Page 34 Note that the DSRLOGOUT only logs out a port when the device deasserts DCD. It does not prevent a terminal from being logged on to the server when DCD is negated.

  • Page 35: Lat Services

    3. All sessions on the port are logged out. 4. The terminal server deasserts the DTR modem control signal for 5 seconds. 5. The terminal server returns to the idle state after the 5 second delay has expired. 5-16 893-763-A...

  • Page 36: Modem Control Signal Interaction

    This is the standard configuration for dial-in lines that support the RNG modem control signal. The terminal server asserts the DTR modem control signal in response to the assertion of the RNG modem control signal. Figure 5-2 shows the modem states that the port enters as it observes or asserts various modem signals. In the diagram, circled items indicate port states and arrows indicate activity.
  • Page 37 DCD Not Observed Within 15s Receive Data, No Wait 15s for DCD Observed Within 15s Wait for Login Figure 5-2. State diagram for dial-in modems which support RNG 5-18 S t a r t Observed No Data, No DCD Observed for 60s Assert Observe...
  • Page 38 Server deasserts DTR if DCD is not asserted within 60 seconds of the assertion of DTR. • Server permits data flow without waiting for the modem connected to the terminal server port to assert the DCD signal (you can autobaud the port by pressing the <Return> key to select the port speed, when the PORT AUTOBAUD characteristic is set to ENABLED).
  • Page 39 Server normally asserts DTR. • Server permits data flow without waiting for the modem connected to the terminal server port to assert the DCD signal (you can autobaud the port by pressing the <Return> key to select the port speed, when the PORT AUTOBAUD characteristic is set to ENABLED).
  • Page 40 This is a non-standard configuration for dial-in lines that do not support the RNG modem control signal. The terminal server asserts the DTR modem control signal in response to the assertion of the RNG modem control signal. Dial-in to a port configured as REMOTE ACCESS is useful for automated data collection. This...

  • Page 41: Figure 5-4. State Diagram For Dial-Out Modems

    Server deasserts DTR if DCD is not asserted within 120 seconds of the formation of the server connection. The server increments a failed call count. If the failed call count reaches the value set for the server PASSWORD LIMIT characteristic, the server logs out the port and deasserts DTR.
  • Page 42 This is the standard configuration for dial-in/out lines that support the RNG modem control signal. The terminal server asserts the DTR signal in response to the assertion of the RNG modem control signal or the formation of a remote connection. Figure 5-5 shows the modem states that the port enters as it observes or asserts various modem signals (in the diagram, circled items indicate port states, arrows indicate activity).
  • Page 43 DCD not observed within 15s Receive Wait 15s data, no for DCD Observe observed within 15s high Wait for login Figure 5-5. State diagram for dial-in/out modems which support RNG 5-24 DCD not observed for 120 seconds, increment failed call count Assert DTR, allow data...
  • Page 44 • Server normally asserts DTR. • If a remote connection is formed to the server, the server assumes the port is functioning as a dial-out line, else the port is assumed to be functioning as a dial-in line. • Server permits data flow after the formation of a remote connection for a dial-out line. For a dial-in line,...

  • Page 45: Using Signal Check

    State diagram for dial-in/out modems which do not support RNG Using Signal Check Model 3395 Terminal Server software supports a signal check feature, which is controlled by the PORT SIGNAL CHECK characteristic. The signal check feature is only available on serial ports which have modem control signals.

  • Page 46: Flow Control

    Similarly, a port will stop or start transmitting on request of the device to which it is attached. Model 3395 Terminal Servers support two modes of flow control: software flow control and hardware flow control.

  • Page 47: Hardware Flow Control

    XON or XOFF characters need to be interpreted as data. Hardware flow control is not implemented in all devices which can be attached to the port. Refer to “Information About Model 3395 Cabling Methods” earlier in this chapter for a discussion of signals that are available to be used for hardware flow control.
  • Page 48 This happens when the terminal server empties the type ahead buffer (due to operation of the session). The frequency at which the terminal server empties the type ahead buffer is determined by the setting of the DEFINE|SET SERVER CIRCUIT TIMER characteristic. The effect of the operation described above is that the port tells the device to stop transmitting when the type ahead buffer is nearly full, or to start up again when the buffer is empty.
  • Page 49 When the FLOW CONTROL characteristic is set to CTS or DSR (hardware flow control is selected), modem control signals are used in place of XON and XOFF to control the flow of data. The terminal server treats the CTS flow control and DSR flow control modes as synonymous. Use either of these port characteristics to select hardware flow control.

  • Page 50: Securid Client Features

    (PIN) and the password (PASSCODE) shown on a SecurID card in order to log on to the server. After the user is logged on to the server, the user can connect to resources on the network. These resources may also be protected using authentication or security mechanisms.

  • Page 51: Configuring The Securid Client At The Unix Host

    Configuring the SecurID Client at the UNIX Host Use the procedures described in the ACE/Server Manual, from Security Dynamics Technologies, Inc. to configure the Model 3395 Terminal Server as a SecurID client. The main activities are: installing the server software and getting it running, and specifying clients.

  • Page 52: Specify Server-Related Securid Characteristics

    Specify Server-related SecurID Characteristics At the Model 3395 Terminal Server, you must specify a number of server characteristics which allow the server to communicate with ACE/Servers and control the manner in which they communicate. Most of the values you specify for these characteristics apply only at the Model 3395 Terminal Server client.

  • Page 53: Configure Ports To Require Securid Authentication

    This characteristic controls the number of times that a user at a Model 3395 Terminal Server client can enter a PASSCODE before the Model 3395 Terminal Server will log out the port. A valid value is a number between 1 and 10; the default is 3.

  • Page 54: Arap Features

    Macintosh and an AppleTalk network so that the remote Macintosh acts as if it were directly connected to the network. This chapter describes how to configure the AppleTalk Remote Access Protocol (ARAP) on Model 3395 Terminal Server. The topics contained in this chapter are: •...

  • Page 55: Arap Features

    Figures 21-1 and 21-2 depict the differences between the standard remote access configuration, and an equivalent configuration using a Model 3395 Terminal Server. In the standard configuration (see Figure 21- 1), a Macintosh computer is dedicated for use as a remote access server. The remote Macintosh computer has access to all AppleTalk zones that are available to the Macintosh computer that is configured as a remote access server.
  • Page 56 Figure 21-2. Remote access configuration using Model 3395 Terminal Server Remote access is a "keyed" software feature and requires a password to be enabled at a Model 3395 Terminal Server. Contact your local Model 3395 Terminal Server Sales Representative or distributor for more information about obtaining a password and the documentation which describes how to configure this feature on the Model 3395 Terminal Server.
  • Page 57 CCL script. Since there are many types of modems, the CCL script "language" is flexible enough to accommodate them all. For Model 3395 Terminal Server CCL scripts are stored on script servers (hosts which can transfer files to the terminal server via TFTP). Individual ports are configured to use a specific CCL script. The terminal server downloads the CCL script once, then executes the commands in the script when the terminal server is first initialized and when a remote access connection is disconnected.

  • Page 58: Arap Setup

    8. Edit CCL scripts to support authentication. (This is only needed if you are using Kerberos and/or SecurID authentication and you have a CCL script which does not contain Model 3395 Terminal Server modifications to support these authentication methods. Model 3395 Terminal Server supplies CCL scripts for many modem models which are already modified appropriately.)
  • Page 59 Verify Port Cabling Figure 21-3 is a wiring diagram which shows the cabling that is needed to connect a communication server serial port to a modem for ARAP applications. You can purchase or make your own cables based on the wiring diagram.
  • Page 60 Figure 21-4 is a wiring diagram which shows the cabling that is needed to connect a server serial port directly to a Macintosh computer. You could use this configuration for debugging the remote access configuration on the Macintosh, or for familiarizing yourself with remote access operations. You can purchase modular cables and adapters shown in the figure, or make your own cables based on the wiring diagram.

  • Page 61: Enable The Server Arap Protocol

    Enable the Server ARAP Protocol ARAP is a configurable feature, which is disabled by default. You must obtain a password for the Model 3395 Terminal Server to enable ARAP. For information about obtaining a password, contact your local SynOptics Sales Representative or distributor.

  • Page 62: Specify Server Characteristics

    Specifies the server's AppleTalk name. This is the name that will be displayed in the Client Status window, when a user connects to the server using remote access. The name can be up to 32 characters in length and may not contain the double-quote (") character. If you do not specify a node-name, the server...

  • Page 63: Specify Port Characteristics

    The complete directory path name where the CCL scripts are located would be: /tftpboot/CCL. Refer to the section of this chapter titled “Install CCL Scripts” and Chapter 11 of the Software Management Guide for the Model 3395/3395A Terminal Server for more information about configuring a script server. Specify PORT Characteristics After the server characteristics have been set up, you must configure ports to support ARAP connections.
  • Page 64 The value can be ALL (the default) for access to all AppleTalk zones, NONE for access to no AppleTalk zones, LOCAL for access only to the zone that the server is in, or a single zone-name, for access to a specific AppleTalk zone in addition to the zone that the server is in.

  • Page 65: Install Ccl Scripts

    Many modem vendors supply CCL scripts for use with their products. There are also public domain sources for these CCL scripts. Model 3395 Terminal Server supplies CCL scripts for use with a variety of modems and makes them available publicly and as part of your software kit (depending on the type of kit you have ordered).
  • Page 66 Installing CCL Scripts at Script Servers For the communication server, you specify a CCL for a given port (described in the section titled "Specify PORT Characteristics"). You also install the CCL in a directory at the script server. For communications servers, use the standard CCL for the modem.
  • Page 67 If you have a CCL script that is not included in the tar archive, you can simply copy the script file into the /CCL sub-directory. Note: The section "Specify SERVER characteristics" covers the procedure to configure the Model 3395 Terminal Server to use the UNIX host as a script server. 21-14...

  • Page 68: Using Arap With Authentication And Dial-Back Features

    For the user, this activity is actually under control of the CCL script. During the process establishing the connection, the Macintosh computer passes various information (login name, authentication passwords, etc.) to the Model 3395 Terminal Server. Figure 21-5 does not depict the role of the remote Macintosh computer in these activities.
  • Page 69 Notify user that access was denied. Figure 21-5, Part 1. 21-16 Start Hang up the port. Wait for telephone to ring. Telephone rings, modems negotiate options, and connection is established. Has a PORT USERNAME been defined for the port? Use the value for the PORT USERNAME as the current User Name.
  • Page 70 Notify user that access was denied. Figure 21-5, Part 2. 893-763-A Is SecurID enabled for the port? the current User Name still undefined? Prompt user to specify a User Name from a Macintosh dialog window. Prompt user to specify a SecurID passcode from a Macintosh dialog window.
  • Page 71 Notify user oof current User Name unregistered user match ARAP name error. registered user? Record message in system log. Does server Notify user of bad ARAP password password error. match user-supplied Record message in password? system log. Operation of authentication and security methods...
  • Page 72 Notify user that required dialback script not found. Record message in system log. Figure 21-5, Part 4. 893-763-A Request a dialback current User Name. DIAL BACK dialback script for the enabled at the port? Notify user that a forthcoming, close connection, dial back the user.

  • Page 73: Basic Format Of A Ccl Script

    Model 3395 Terminal Server includes the necessary extensions in a file that is contained in the CCL UNIX tar archive. You will find an example of the Model 3395 Terminal Server extension and the text for a typical CCL at the end of this chapter. (The typical CCL shown does not contain the Model 3395 Terminal Server extensions.) Refer to the documentation supplied by the APDA division of...
  • Page 74 Match strings define all the possible responses that are expected from modem (such as CONNECT at a particular speed, no answer, busy, no carrier or dial tone, or some other error). Each match string also includes a label to which the program should go when the particular condition specified by the match string is met.
  • Page 75 This permits you to edit the file using a program such as TeachText, Mockwrite, or any other text-editing program. 2. Examine the labels used in the CCL script. The Model 3395 Terminal Server extensions were written using seventeen consecutive labels in the range of 100-116. Most CCL scripts do not use labels in this range.
  • Page 76 Example Model 3395 Terminal Server CCL Extensions ------------------------------------------------------------------------------- ! $Id: xooba.ccl,v 1.3 1993/09/01 19:47:43 sale Exp $ ! Xooba - Model 3395 Out Of Band Authentication; Copyright (C) 1993 M3, Inc. ! Uses @LABELs 100-116 and MATCHSTRs 1-13,16. @LABEL 100 ifanswer 116 note "Authenticating..."...
  • Page 77 @LABEL 108 write "\04" note "Card requires new PIN. jump 100 ! Server attempting to supply new PIN anyway. ! This is beyond the capability of a CCL to handle. @LABEL 109 note "Unable to assign new PIN. write "\04\13"...

  • Page 78: Example Of A Typical Ccl Script

    Example of a Typical CCL Script Global Village Teleport without Xooba mods: ! SynOptics CCL $RCSfile: GV_TP_Serial_High_Speed,v $ $Revision: 1.1 $ $Date: 1993/10/26 19:49:32 $ !SynOptics load: y answer: n originate: n ! 08/02/92 TelePort Gold draft ! 10/23/92 CTC Switched to new script written by RBH ! 10/26/92 CTC Fix for International calling(S7=60) ! 11/11/92 CTC Rewrote the Hang up section of the script to use AT\Y ! 12/07/92 CTC Fix for Shiva LanRover/L image 1.0 problem...
  • Page 79 ifstr 2 8 "1" pause 5 matchstr 1 8 "OK\13\10" write "ATM0\13" matchread 30 jump 59 ! The modem is ready so enable answering, or originate a call @LABEL 8 pause 5 ifANSWER 30 note "Dialing ^1" 3 write "ATDT^1\13" @LABEL 9 matchstr 1 11 "CONNECT 1200\13\10"...
  • Page 80 @LABEL 15 HSReset 0 1 0 0 0 0 ifANSWER 16 pause 30 @LABEL 16 exit 0 ! @ANSWER ! Set up the modem to answer @LABEL 30 write "ATS0=1\13" matchstr 1 31 "OK\13\10" matchread 30 jump 59 @LABEL 31 matchstr 1 32 "RING\13\10"...
  • Page 81 Notice that there is a label 125 in this CCL script, and a label 98 just above (five lines up), but labels 100 to 116 are available for use. No need to edit Model 3395 extensions in this case. Add Model 3395 extensions immediately after this line. 893-763-A...

  • Page 82: Modifying Dial-Back Scripts For Arap Ports

    Within command scripts, pound-sign character, followed by a space or tab, indicates a comment; the server ignores the remainder of the line.•At ports which support AppleTalk Remote Access connections, the server ignores "#modem" commands. At ports which support AppleTalk Remote Access connections, only the #ARAP_modem command is processed.

  • Page 83: Arap Planning Considerations

    The formula assumes that the Model 3395 Terminal Server is dedicated for making ARAP connections (i.e., no other features are enabled on the unit), that there is no Ethernet traffic to contend with, and that the processor will not be required to perform data compression activities.

  • Page 84: Configuring Domain Name Server Support

    BSD UNIX printcap file, A-19 CARD protocol, 15-3 CCL scripts, 21-20, 21-27 Clear to Send signal (CTS), 5-14 coldstart, 7-8 configuring domain name server support, 2-2 connected nodes, 8-12 connected sessions, 8-12 conventions, xvi csportd daemon, 16-1, 19-1 cross over cable, 5-12...

  • Page 85: Software Management Tools

    Xremote, 12-15 memory problems, 8-7 memory usage for features and protocols, 2-7, menu feature, 2-7, 3-6, 8-3 Model 3395 software management tools, 1-3 modem cabling, 5-13 modem control operation, 5-12 modem control signal interaction, 5-17 modem-related PORT characteristics, 5-14...

  • Page 86: Password Protection For Lat Services

    18-1 programming guidelines for a, 18-8 setting up a script server for a, 18-4 samples, 18-11 using comment lines in, 18-8 NetWare, 14-1 NetWare print server, adding, 14-7 network command script feature, 11-1 network management, 1-3 network management products, 1-3...

  • Page 87: Viewing Ipx Protocol Packet Type Setting

    PORT ACCESS characteristic, 9-8 privilege levels, 9-3 scripts, 9-16 SecurID, 20-1 SERVER ALTERNATE STATUS display, 8-13 SERVER COUNTERS display, 8-11 server modem disconnect sequence, 5-16 server node limit, 8-8 server packet buffers, 8-10 server queue limit, 8-9 server service groups, 8-9...

  • Page 88: Model 3395 Terminal Servers

    18-6 write parameters to a Model 3395 Terminal Server, 1-3 X Display Manager (XDM), 12-3 X Windows protocol, 12-1 XDM host, 12-3 XON|XOFF flow control, 5-28 Xprinter, 2-7 XPRINTER setup dialog, 14-2 Xremote characteristics, 12-8...

This manual is also suitable for:

3395a

Table of Contents