Compaq t1000 - Terminal Thin Client PC Network Installation Manual
  1. Manuals
  2. Brands
  3. Compaq Manuals
  4. Touch terminals
  5. t1000 - Terminal Thin Client PC
  6. Network installation manual
Compaq t1000 - Terminal Thin Client PC Network Installation Manual

Compaq t1000 - Terminal Thin Client PC Network Installation Manual

Windows-based terminal
Hide thumbs Also See for t1000 - Terminal Thin Client PC:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Manual, Quick Reference Manual
T1500/T1510 W
-
T

INDOWS
BASED
ERMINAL
N
I
G
ETWORK
NSTALLATION
UIDE

Advertisement

Table of Contents
loading

Related Manuals for Compaq t1000 - Terminal Thin Client PC

Summary of Contents for Compaq t1000 - Terminal Thin Client PC

  • Page 1 T1500/T1510 W INDOWS BASED ERMINAL ETWORK NSTALLATION UIDE...
  • Page 3 T1500/T1510 W INDOWS BASED ERMINAL ETWORK NSTALLATION UIDE September 2000...
  • Page 4 Notice The information in this document is subject to change without notice. COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN; NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL. This document contains information protected by copyright.

  • Page 5: Federal Communications Commission Notice

    Federal Communications Commission Notice This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation.

  • Page 6: European Union Notice

    European Union Notice Products with the CE Marking comply with both the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of the European Community. Compliance with these directives implies conformity to the following European Norms (in brackets are the equivalent international standards): •...

  • Page 7: License Agreement

    Control No. 075C License Agreement YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING THIS SOFTWARE (TOGETHER WITH ANY SUPPLIED DOCUMENTATION, HEREAFTER “SOFTWARE”), WHICH IS COPYRIGHTED BY LICENSOR. USING THIS SOFTWARE INDICATES YOUR ACCEPTANCE OF THE FOLLOWING TERMS AND CONDITIONS. Grant You may use the Software in conjunction with Your hardware (Terminal).
  • Page 8 Limit of Liability UNDER NO CIRCUMSTANCES SHALL LICENSOR BE LIABLE FOR LOSS OF DATA, COST OF COVER, OR ANY INCIDENTAL OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. THESE LIMITATIONS SHALL APPLY EVEN IF LICENSOR OR ITS RESELLER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY PROVIDED HEREIN.

  • Page 9: Table Of Contents

    Contents Overview Introduction xi How to Use This Guide xi References xi DHCP/BOOTP xii Time Server xii SNMP xii Other RFCs xii Installation Overview and Planning Overview of Installation Procedure 2 Planning Your Installation 3 Step 1. Complete Worksheets 3 Step 2.
  • Page 10 viii Configuring Terminal Start-Up Resources BOOTP 5 DHCP 8 T1500/T1510-Specific Option Definitions 13 Option 43 Vendor-Specific ID 13 NETSVC 13 NOSWAP 14 REFLASH 14 MF_DIR 14 MF_CFG 15 XFS 15 XDMCP 15 BUDDY_BOOT 15 Packet Size 16 Option Overload 16 Option 18 vs.
  • Page 11 Selecting Browser Location Browser Location 35 Netscape Communicator Constraints 36 Installing CD Software onto the Server(s) CD Contents 39 Running the Installation Program 39 Text-Mode Installation 43 GUI-Mode Installation 44 Installing on Non-Supported Servers 45 Appendices T1500/T1510 Windows-Based Terminal Quick-Start Guide Quick-Start Procedure 48 “G-Key Reset”...

  • Page 13: Overview

    Overview Introduction This guide explains how to install software from the installation CD onto your server and how to configure the resources resident on the server to support Compaq T1500/T1510 Windows-Based Terminals for this software release. How to Use This Guide For full access to all the terminal resources, you will need to plan and configure your server setup as explained in Chapter 1 of this guide.

  • Page 14: Dhcp/Bootp

    DHCP/BOOTP RFC 1534 - Interoperation between DHCP and BOOTP RFC 2131 - Dynamic Host Configuration Protocol RFC 2132 - DHCP Options and BOOTP Vendor Extensions Time Server RFC 868 - Time Protocol SNMP RFC 1155 - Structure and Identification of Management Information for TCP/IP-based Internets RFC 1157 - A Simple Network Management Protocol (SNMP) RFC 1212 - Concise MIB Definitions...

  • Page 15: Installation Overview And Planning

    Installation Overview and Planning This document describes how to install the T1500/T1510 software on the following computer servers: • SCO OpenServer 5.0.5 • SCO UnixWare 7 • Linux (both Slackware and Red Hat) • Windows NT Server • HP/UX For technical support refer to the Compaq Technical Support telephone numbers for your area.

  • Page 16: Overview Of Installation Procedure

    Chapter 1 Server resources can be provided from platforms other than the above-listed ones, but Compaq has not certified other environments and can not be responsible for any problems related to incorrectly configured servers. If you are going to operate in a different server environment, read this entire document very carefully to determine if there are any issues that you might need to resolve.

  • Page 17: Planning Your Installation

    Installation Overview and Planning Planning Your Installation The software installation procedure is broken down into 6 basic steps, including the planning described in this chapter. The following brief descriptions of the basic steps do not by themselves provide enough information for you to fill in the planning worksheets presented in Appendix B of this document;...

  • Page 18: Step 3. Configure Optional Terminal Start-Up Resources

    Chapter 1 Step 3. Configure Optional Terminal Start-Up Resources A set of resources independent of the individual applications on the terminal is strongly recommended for ease of use of the system as a whole. Although these resources are optional, providing them will speed up access of certain items, provide enhanced diagnostic capabilities (for troubleshooting problems), provide for swapping in a local-boot environment, provide for print spooling in a local-boot environment, allow for remote administration of the terminal, provide for Internet (or...

  • Page 19: Configuring Terminal Start-Up Resources

    Configuring Terminal Start-Up Resources Several network resources are either required or recommended for starting up the terminal initially in a network-boot environment. The resources in this category use the following 6 network protocols: BOOTP DHCP TFTP Time Server A brief description of the resources and any special configuration requirements for each protocol are provided in this chapter.
  • Page 20 Chapter 2 When booting in a network environment, BOOTP provides the terminal with the following required information: the terminal’s IP address; the IP address of the TFTP boot server; the pathname of the operating system file to be loaded using the TFTP server;...

  • Page 21: Bootptab File Example

    Configuring Terminal Start-Up Resources Figure 2-1 Bootptab File Example .c_terminal:ht=1:ds=132.237.1.42:gw=132.237.20.1:sm=255.255.255.0:\ :dn=xx.com:sa=132.237.20.2:hd=/tftpboot:bf=vmlinux:\ :T17=”132.237.20.2:/nwt/root”: term1:ha=00800c123456:ip=132.237.20.5:tc=.c_terminal term2:ha=00800c123457:ip=132.237.20.4:tc=.c_terminal Legend: = TFTP boot file = domain name = domain name servers (IP) gw = gateways = hardware address = home directory = hardware type = host IP address = TFTP server address sm = subnet mask = template host (points to similar host entry)

  • Page 22: Dhcp

    Chapter 2 For non-Windows server platforms, bootp can be run either at boot or from inetd. It is recommend that bootp be run from inetd, although with many terminals and a stable environment (i.e., an unchanging list of terminals), it may be faster to run via automatic start-up at server boot.
  • Page 23 Configuring Terminal Start-Up Resources In a local-boot environment, DHCP can provide a set of configuration parameters, which reduces the need to configure the terminal’s Select | System | Setup | Connectivity | Internet | DHCP dialog box. The default (out of the box) configuration assumes DHCP provides all network configuration information.

  • Page 24: Dhcp Options

    Chapter 2 Table 2-1 DHCP Options Option Number Option Description Subnet Mask Router Domain Name Server Host Name Domain Name Root Path Extension Path Broadcast Address Vendor-Specific Information X-Windows Font Server XDMCP Addresses Lease Time Option Overload DHCP Message Type DHCP Server IP Address Parameter Request List Maximum DHCP Message Size...
  • Page 25 Configuring Terminal Start-Up Resources Option 48 assumes TCP and port 7100 for font server access. If other ports are to be used, you must use the vendor-specific option described below. Also, option 49 assumes Query mode. If Direct is wanted, use the vendor-specific option. The terminal uses options 66 and 67 to determine where to obtain the operating system for the network-booted terminal, with option 66 being the server name (as an IP address), and option 67 being the full pathname to the file (such as...

  • Page 26: Additional Vendor-Specific Options

    Chapter 2 Table 2-2 Additional Vendor-Specific Options Option 43 Type/Length/Value for 128-254 Tag Number Description Option 43 Vendor-specific ID. Integer 4, 0x76583A1C NETSVC Network service machine and String, variable, same format directory. as option 18 string. NOSWAP If this option is provided, Integer 1, any value.

  • Page 27: T1500/T1510-Specific Option Definitions

    Configuring Terminal Start-Up Resources In a network-boot environment, the client and vendor identifiers are not modifiable by the user. The terminal provides the ability to change the Client ID, Vendor ID, and Hostname fields consistent with the RFCs. The default Vendor ID is Compaq-T1500. The default client ID is the MAC address with a key (consistent with the RFC specifications).

  • Page 28: Noswap

    Chapter 2 (Windows server) is //machine/share[/directory], where machine is a DNS resolvable machine name, share is the share name, and path is an optional path within that share. For name resolution, an entry in the terminal's host file (Setup | Connectivity | Internet | DNS | Hosts) qualifies. For NFS, the directory MUST be exported with read/write/execute permissions and with root mapping to root, not to nobody.

  • Page 29: Mf_Cfg

    Configuring Terminal Start-Up Resources the share name, and path is an optional path within that share. For name resolution, an entry in the terminal's host file (Setup | Connectivity | Internet | DNS | Hosts) qualifies. For NFS, the directory MUST be exported with read/write/ execute permissions and with root mapping to root, not to nobody.

  • Page 30: Packet Size

    Chapter 2 Packet Size The terminal is capable of sending and receiving the Maximum DHCP Message size option, allowing packets to contain up to 1500 bytes, including the DHCP header in this size. Since some DHCP servers will only respond to packets that are of the smallest size, the packets sent by the terminal are guaranteed to fit in a minimum size.

  • Page 31: Option 18 Vs. Option 43 Vs. Options 128

    Configuring Terminal Start-Up Resources Option 18 vs. Option 43 vs. Options 128+ All three methods (Option 18, Option 43, Option 128+) provide identical capabilities, just in different manners. It is recommended that only one method be used, but you are not restricted to this. Things to take into consideration when choosing include the following: existence of a TFTP server, level of configurability in the DHCP server, availability of a binary file editor, knowledge of DHCP option data format, and the number of other devices that are going to be administered via...
  • Page 32 Chapter 2 Table 2-3 Labels and Data for Text Format Option, Continued Option Number Label Notes NISDOMAINNAME Not currently used. NISSERVER Not currently used. NTPSERVER Not currently used. Not allowed. XFONTSERVER First element; subsequent elements append a number contiguous to the label. XDMCP First element;...

  • Page 33: Option 43

    Configuring Terminal Start-Up Resources Files ending in a .txt name are treated as text files. Any other filename is treated as an RFC-compliant file. Use of this option requires a TFTP server. Since path names are included in the file, the TFTP server must accept UNIX-style file separators, not DOS-style separators.

  • Page 34: Tftp

    Chapter 2 TFTP TFTP is required in a network-boot environment. The TFTP server loads the terminal’s operating system off the server into memory on the terminal. This operating system then controls all other actions performed from the terminal. This resource is used once each time a network-boot terminal is powered-up. If a local-boot environment uses DHCP, and DHCP supplies option 18, the server named in option 18 must support TFTP.
  • Page 35 Configuring Terminal Start-Up Resources The following four requirements are mandatory and must be met in the NFS configuration: Note IMPORTANT! If these requirements are not met, the terminals will not work in a network-boot environment. 1. The client root account map must be able to access the server root account (on Linux, this is called no_root_squash, and on SCO Openserver 5.05, set the NFS option to -anon=0).

  • Page 36: Dns

    Chapter 2 DNS is a protocol designed for converting the relatively easy-to-remember descriptive machine/terminal names into IP addresses, which is their actual representation on the Internet/intranet. Although DNS is not required for the terminals to be functional, its use is strongly recommended. For example www.name.com is a lot easier to remember than a string of numbers (nnn.n.nnn.nnn).

  • Page 37: Configuring Optional Terminal Start-Up Resources

    Configuring Optional Terminal Start-Up Resources Several server resources can enhance terminal operation but are not among the minimum required for the terminal to function. The resources in this category use the following network protocols: SNMP HTTP and may use the following serial line protocols: SLIP CSLIP This chapter provides a brief description of where the above-listed protocols are...

  • Page 38: Nfs

    Chapter 3 Because of limited local storage capacity in the terminal, the fonts resident on the terminal are the minimum set for use with all applications. If a locally booted terminal uses the network services director, additional fonts are automatically made available.

  • Page 39: Snmp

    Configuring Optional Terminal Start-Up Resources For a network printer to be used (via SMB), all the requirements above must be met. Also, for a server with an NTFS file system, the security must be altered to allow guests to have full access to all files and directories in the network services tree. Perform the following steps: 1.

  • Page 40: Http (Help)

    Chapter 3 HTTP (Help) HTTP is the protocol used by the World Wide Web. The server-based user help for the terminal is distributed as a tree of HTTP links and is on the installation CD. Terminal help can be installed on a WWW server, but because of network traffic or your configuration, it may be more desirable to configure a local HTTP server and install the help tree there.

  • Page 41: Cslip

    Configuring Optional Terminal Start-Up Resources CSLIP CSLIP stands for Compressed Serial Line Internet Protocol and is a variant of SLIP that uses VJ header compression. The host and server name requirements mentioned under SLIP also apply to CSLIP. FTP is one of the protocols that will be used to upgrade from the current software release to future releases.
  • Page 42 Chapter 3...

  • Page 43: Configuring Server Application Resources

    Configuring Server Application Resources Several server resources apply to the individual applications that run on the terminal. These resources are not needed for basic functioning of the terminal, but individual applications require them. The resources in this category use the following network protocols: HTTP POP3/IMAP4...

  • Page 44: Pop3/Imap4

    Chapter 4 POP3/IMAP4 POP3 and IMAP4 are the Post Office Protocols used by the e-mail function embedded in Netscape Communicator on the terminal. If you are using the e-mail function to send and read e-mail, you may need to configure a POP3 or IMAP4 server to manage the e-mail.
  • Page 45 Configuring Server Application Resources Note RSH support is not available from Windows NT servers. Even if X clients are installed on NT, RSH support must be available from other server(s) for the X Manager to be able to launch them. The X Manager is the terminal’s interface to RSH;...

  • Page 46: Secure Shell

    Chapter 4 where terminal is the terminal name and user is the user name from the terminal (root is automatically used if security is disabled; guest is automatically used if security is enabled and auto login as guest is selected). In addition, the terminal optionally supports both Kerberos authentication and DES data encryption for RSH commands, although the X protocol packets for an X application will not go through the DES data encryption layer.
  • Page 47 Configuring Server Application Resources Any command executed through this mechanism will be run as that special user, although the SHELL environment variable is replaced with the first entry in the rshsecure.cfg file and the DISPLAY environment variable is set to point back to the terminal, allowing shell scripts that launch sets of X applications to work.
  • Page 48 Chapter 4...

  • Page 49: Selecting Browser Location

    Selecting Browser Location The browser application is designed to run either locally or from a server. Normally it resides and is run locally. Based upon the number of users running an application, the processing power of the server, the types of operations being performed by the users with the application, and the type of network connection between the terminal and the server, it may be more advantageous to run the application from a server rather than locally.

  • Page 50: Netscape Communicator Constraints

    Chapter 5 • Your company has standardized on a browser other than Netscape Communicator. Reasons to execute the browser locally: • Less network bandwidth is available. • You require faster start-up of the browser application. • Many users are on the network. •...

  • Page 51: Netscape Communicator Constraints

    Selecting Browser Location Table 5-1 lists the various configurations of the terminal and the external controls that were imposed on Communicator for each configuration. Table 5-1 Netscape Communicator Constraints Configuration Save/Save As Java Main/News Composer Local Boot: Local Home/No Swap Swap Net Home/No Swap Swap...
  • Page 52 Chapter 5...

  • Page 53: Installing Cd Software Onto The Server(S)

    Installing CD Software onto the Server(s) This chapter describes the procedure for installing the software provided on the T1500/T1510 Windows-Based Terminal product installation CD. The software is installed onto the server(s) you selected when filling out the worksheets for Chapter 1. CD Contents The CD contains a series of installation scripts, the programs necessary to run them on the supported platforms, the software (and other files) to be installed onto...
  • Page 54 Chapter 6 Caution There is currently no check for sufficient disk space and no undo procedure. Total disk space required to install all software on the CD is 650 MB. On UNIX, the script determines if GUI mode will be used based upon the DISPLAY environment variable;...
  • Page 55 Installing CD Software onto the Server(s) Mount the CD-ROM drive using the following command: Platform Command SCO UnixWare mount -r -F cdfs /dev/cdrom/c0b0t510/cdrom SCO OpenServer mount /dev/cd0/cdrom Slackware Linux mount /dev/cdrom/cdrom Red Hat Linux mount /mnt/cdrom /cdrom HP/UX • To mount at the beginning: Make sure /usr/sbin is in the program search path.
  • Page 56 Chapter 6 Change the active directory to the CD-ROM drive (cd /cdrom). Note Windows uses “ \ ” as directory separator, and UNIX uses “ / ”. Prior to start of the TCL/TK runtime, use the appropriate separator. Run the install procedure (./install). Note that ./install explicitly runs the install program in the current directory.

  • Page 57: Text-Mode Installation

    Installing CD Software onto the Server(s) The installation script will not install any software onto your system until after all responses are entered. The last prompt will tell you when the installation is ready to proceed. Up until then, you can abort the installation safely by using the interrupt character (or by typing “q”...

  • Page 58: Gui-Mode Installation

    Chapter 6 Directories are made as required, so a /T1500/root directory extraction will also create /T1500. If the directory and/or file exist at the time the second section of the installation is reached (querying for where to install), and if the user chooses to overwrite the data (applies to install only, not to update), the files and/or directories are removed prior to installing.

  • Page 59: Installing On Non-Supported Servers

    Installing CD Software onto the Server(s) There are five sections to the GUI-mode installation. Each has a distinct background screen. The first section is purely informative to you, the user. The second section contains a series of checklists, asking for which items you wish to install on that server.
  • Page 60 Chapter 6 The upgrade directory contains the scripts necessary for upgrading local-boot terminals from one release to another. The admin directory contains an ever-growing set of scripts that administrators can use or refer to for managing their terminals via NFS. The remaining directories contain the runtime environments for the various supported platforms, including TCL and TK binaries (tclsh and wish, respectively), shared libraries to guarantee a compatible environment (Linux), and other utilities that are used for the...

  • Page 61: T1500/T1510 Windows-Based Terminal Quick-Start Guide

    T1500/T1510 Windows-Based Terminal Quick-Start Guide The T1500/T1510 Windows-Based Terminal is shipped from the factory configured for local boot. Instructions are included in this appendix to convert to network boot if you require this mode of operation. If you require additional network services for a local-boot (default) terminal, you must use the server setup procedure.

  • Page 62: Quick-Start Procedure

    Appendix A Quick-Start Procedure These instructions are for network administrators and end users already familiar with networks and terminals. They provide the minimum information needed to get the terminal into a basic operating mode that permits access to the full help system, services, and upgrade software residing on designated servers on the network.

  • Page 63: G-Key Reset" Procedure

    T1500/T1510 Windows-Based Terminal Quick-Start Guide 7. To further configure the network setup, use the Select | System | Setup window’s Connectivity dialog boxes. Most of the information can be supplied by your network administrator: • For ethernet networking, make entries in the Internet dialog boxes. •...
  • Page 64 Appendix A • If security is enabled, after turning on power you may wait until the Login dialog box displays. Press Ctrl+G and then enter a valid administrator or user login name and password. Follow the prompts displayed on the screen. Note Your security access level may limit the resets available to you.

  • Page 65: Installation Planning Worksheets

    Installation Planning Worksheets The following worksheets should be filled in during the planning phase (Chapter 1) and used during the installation phase (Chapters 2 through 6) of your resource configuration process. The chapter corresponding to each worksheet provides specific information about the entries in the worksheet, and should be consulted as the worksheet is filled in.
  • Page 66 Appendix B In an existing network environment where workstations are on people’s desktops, many server resources may already be configured. In new installations you will have to determine which server resources you must configure for use with the network terminals, based upon your needs and environment (and filled in worksheets).
  • Page 67 Installation Planning Worksheets...

  • Page 68: Optional Terminal Start-Up Resources Worksheet

    Appendix B...

  • Page 69: Server Application Resources Worksheet

    Installation Planning Worksheets...

  • Page 70: Browser Launch Location Resources Worksheet

    Appendix B...

  • Page 71: Other Images Location Worksheet

    Installation Planning Worksheets...

  • Page 72: Software Images From The Cdrom Worksheet

    Appendix B...
  • Page 73 Installation Planning Worksheets...
  • Page 74 T1500/T1510 Windows-Based Terminal Network Installation Guide ® ® Created using FrameMaker and Acrobat The on-line book is provided in PDF and presented on the terminal product CD.

This manual is also suitable for:

T1500T1510

Table of Contents