ica_v2r1p5_internal

ica_v2r1p5_internal
IBM Network Station
Version 2 Release 1 PTF 5
Windows Application Access
( ICA )
February 18, 2000
IBM Internal Use Only
IBM Copyright
(c)
Copyright 1999 International Business Machines, Inc. All rights reserved.
Citrix Copyright and acknowledgment
(c)
Copyright 1998-1999 Citrix Systems, Inc. All rights reserved.
February 18, 2000
IBM Internal Use Only
Contents
INTRODUCTION AND OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Citrix Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Independent Computing Architecture (ICA) protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
ICA Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Window size and borders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Number of colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Color approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
True Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Remote Applications and Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Printer mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Audio mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
COM port mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Data compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Drive Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
SOCKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
User logon parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
National language support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
On-line help associated with panels, commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
USING THE ICA REMOTE APPLICATION MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
To run the ICA Remote Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
To define a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
To open a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Connecting to Citrix MetaFrame Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
To log off from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
To disconnect from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Connecting to Citrix WinFrame Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
To log off from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
To disconnect from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
To quit from the ICA Remote Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
To edit an existing connection definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Entry menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Option menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
To display the connection properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
February 18, 2000
3
IBM Internal Use Only
Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Firewall Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Settings dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Server Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Hotkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Drive mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Firewall Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
USING THE ICA CLIENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
To run the ICA Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
COMMAND LINE PARAMETERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
ICA Remote Application Manager - wfcmgr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
ICA Client - wfica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
.INI CONFIGURATION FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
.INI File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
appsrv.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Wfclient.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Module.Ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
ADVANCED TOPICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Precedence order for ICA connection Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Copying and pasting text and graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Connecting to Local Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Automatic Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Manual Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Connecting to Local Serial Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Low Bandwidth Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Number of colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Tcp buffering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Audio quality levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Persistent caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
TECHNICAL DETAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
NSM variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Kiosk Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
February 18, 2000
4
IBM Internal Use Only
Client Printer Auto Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
ICA Language Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
FLASH Boot Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Migration, Coexistence and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
ICA directories and files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Base package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
128-bit encryption option package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
RESTRICTIONS AND LIMITATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Window Managers Usurp Key Strokes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Multiple Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
ICA protocol limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
TAPI support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
DOS full screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
NT configuration problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
NT server print spooler crash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Lotus WordPro problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
NT keyboard layout mapping problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
CHANGE HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
V2R1 ( August 1999 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Fixes to the Citrix ICA Source Code, Version 3.0.15f . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
PTF-1 ( August 1999 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Defects Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
PTF-2 ( October 1999 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Defects Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
PTF-3 ( December 1999 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Defects Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
PTF-4 ( February 2000 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Defects Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
PTF-5 ( April 2000 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Defects Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
ERROR MESSAGES
February 18, 2000
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5
IBM Internal Use Only
Introduction and Overview
The ICA Client is a V2R1 IBM Network Station application that provides access to a Windows
session running on high-performance Citrix servers. Once the connection to a Citrix server is
established, you can access Windows applications and work with files in a similar way to working on
a local PC.
The ICA Client displays the Windows session in a separate window on the IBM Network Station
screen, and is fully integrated with your other IBM Network Station applications. You can cut and
paste text and graphics between Windows applications in the ICA Client window and your other
applications.
Your IBM Network Station's mouse and keyboard can be used with Windows applications in the
usual way, and you can set up key mappings to enable you to enter PC keys not available on your
IBM Network Station's keyboard.
Citrix Servers
Citrix WinFrame and Citrix MetaFrame are fast and easy Windows NT application server
solutions for delivering Windows applications to the IBM Network Station and other desktops,
including PCs, Apple Macintosh computers, X terminals, and UNIX workstations. Citrix server
software usually runs on a high-performance PC, and a single-processor Citrix server will
typically support up to 15 simultaneous client connections.
The Citrix server communicates with the ICA Client over a standard TCP/IP network connection.
Independent Computing Architecture (ICA) protocol
ICA is a general-purpose presentation services protocol owned by Citrix Systems. Conceptually
similar to the UNIX X-Windows protocol, ICA allows an application's user interface to execute
with minimal resource consumption on a client machine, while application logic executes on the
WinFrame or MetaFrame multiuser application server.
The ICA protocol has been specially designed for transmitting Windows graphical display data,
and keyboard and mouse input, over a network connection.
The key features of the ICA protocol that help to achieve the high performance are:
Ÿ
Intelligent command and object-specific compression
Ÿ
Intelligent caching of Windows objects including bitmaps, brushes, glyphs, and pointers
Ÿ
Run length encoding
The ICA protocol is designed to be client independent.
More information about the ICA protocol is available from the Citrix World Wide Web page at
http://www.citrix.com/
February 18, 2000
6
IBM Internal Use Only
ICA Clients
An ICA Client application allows you to define and initiate ICA connections. On the IBM Network
station, an ICA Remote Application Manager presents a list of the ICA connection definitions you
have set up, and allows you to initiate an ICA connection to a Citrix Server.
Once you are connected to a Citrix server, the ICA Client application presents the ICA Client
window to handle communication with the Citrix server and provide the display, keyboard, and
mouse interface between the server and your IBM Network Station.
The ICA Remote Application Manager also allows you to create new connection definitions, or
edit the definitions of existing connections.
For each connection you can define the following features:
Window size and borders
The ICA Client window size can be set to one of four predefined window sizes, full screen size,
or a custom size (up to the greater of 1280x1024 or your IBM Network Station display size).
Window borders and title bar can be turned off.
Number of colors
The ICA Client window can be set to 256 or 16 colors. This is an ICA Protocol limitation. At some
future time, the ICA Protocol may be extended to support more than 256 colors, e.g., 16-bit
TrueColor.
In addition, you can define default values for the window size and window colors, which are then
used as the default for all new connection definitions.
Color approximation
Color approximation can be used if the IBM Network Station is running in PseudoColor mode. In
this mode, differences in the palettes used between the ICA Client (and the Windows
applications it displays) and the IBM Network Station may cause an annoying flashing that
occurs when switching context. The ICA Client's color approximation scheme eliminates this
flashing by using colors from the local desktop palette to display the ICA Windows sessions.
True Color
The ICA Client maps ICA protocol colors (16 or 256) to true color. Running the IBM Network
Station in TrueColor mode provides the most compatible color management if the ICA Client is
sharing screen space with any other program (including the window manager and desktop).
Remote Applications and Load Balancing
The ICA Client supports two types of connections: ICA connections and remote applications.
An ICA connection allows a user to access a Citrix desktop. The user can run any applications
available on the desktop, in any order.
February 18, 2000
7
IBM Internal Use Only
A remote application is a predefined application and its associated environment (for example
directories and initialization files) that execute on a remote Citrix server.
There are several ways to define a remote application:
Ÿ
By defining an ICA connection that directly executes an application.
Ÿ
By defining an ICA connection that points to a published application created using the
Published Application Manager on the Citrix server. This method also supports load
balancing.
See Chapter 5, "Application Publishing," in the MetaFrame Administrator's Guide , or the
WINFRAME System Guide for more information about application publishing.
The Load Balancing Services can be used with multiple Citrix servers to provide load balancing
capabilities. Citrix load balancing support lets you define a remote application that runs on a
predefined set of Citrix servers. When a user launches the remote application, the Citrix load
balancing software uses a tunable algorithm to select a server to execute the application. The
load balancing parameters are configurable and can be tuned to provide maximum throughput
and system availability.
Another advantage of load balancing is increased reliability. By configuring a pool of servers that
are capable of running your users' applications without your users ever needing to know which
server is actually running the application, you can easily bring servers off-line for maintenance
without affecting application availability, or add more servers for increased performance.
See Chapter 5, "Application Publishing," in the MetaFrame Administrator's Guide, or the WIN
FRAME System Guide for more information about load balancing.
Printer mapping
You can redirect printing jobs from applications you are running on a Citrix server and print them
to a printer connected to your IBM Network Station.
The ICA Client supports any spooled printer available from your IBM Network Station, as long as
the associated printer driver is installed on the Citrix server.
If a Network Station printer has been defined with an associated NT printer device driver name
then the ICA Client will automatically create the printer on the ICA Server during session logon
and delete it when the session ends. Printers can also be explicitly created by using the NT
Printer Wizard to add one or more printers for use in the ICA session.
Audio mapping
Audio mapping allows your client computer to play sounds generated by applications running on
the Citrix server. ICA Client audio support includes configurable sound quality levels that allow
you to customize sound quality based upon the amount of bandwidth available.
NT Server Audio
Ÿ
Ÿ
Ÿ
Ÿ
Wave sound only (server may convert other formats to Wave)
Midi music not supported
CD audio not supported
no sound card is required on the server
February 18, 2000
8
IBM Internal Use Only
Supported audio characteristics
Ÿ
Ÿ
Ÿ
Ÿ
linear PCM
8 and 16 bit
8, 11, 22, and 44 Khz
mono and stereo
Device control (e.g. volume) is not supported
COM port mapping
Client COM port mapping allows devices attached to the client computer's COM ports to be used
from ICA sessions on a Citrix server. This allows local serial devices to be used by applications
running on the Citrix server.
Data compression
Data compression reduces the amount of data transferred across the ICA session to increase
performance over bandwidth-limited connections.
Caching
Caching stores commonly used graphical objects such as icons in a local cache on the client
computer to reduce the amount of data sent over the connection. Caching commonly used
bitmaps tends to increase performance, especially for bandwidth-limited connections.
The ICA Client employs both an internal transient cache and an external persistent cache.
Since the IBM Network Station does not have a hard disk, the external persistent cache is
implemented as an in-memory file system which is created each time the Network Station is
re-booted. By default, this in-memory file system is not enabled due to the finite amount of
memory in the Network Station. (In this release, persistent caching must be enabled by following
the ICA persistent caching directions in the /.profile file.)
Drive Mapping
Client drive mapping makes selected directories on the IBM Network Station available to the
users when they connect to a Citrix server. Access login and read/write permissions can be set
for each selected directory.
SOCKS
ICA connections can use the SOCKS networking proxy protocol to enables hosts on one side of
a SOCKS server to gain full access to hosts on the other side of the SOCKS server without
requiring direct IP reachability. The SOCKS server address and port number can be set for each
connection or for all connections.
February 18, 2000
9
IBM Internal Use Only
Encryption
ICA sessions can be encrypted using 40, 56 or 128 bit encryption keys. The ICA Client must
connect to an Citrix Server that supports an equal or higher number of bits for the encryption
key.
User logon parameters
This feature allows you to set up the user’s name, password and authenticating NT domain for an
ICA session. The user name and password used to login in to the IBM Network Station can be
reused automatically or these parameters can be configured for each connection. If these
parameters are not provided, the user is prompted for them each time he connects to a NT
multi-user server.
National language support
The ICA client supports all languages and keyboards supported by the IBM Network Station. In
addition, an extended list of keyboards is supported by the ICA Client once a connection has
been made to an ICA server.
External Interfaces
There are two executable programs in the IBM Network Station ICA package.
Ÿ
The ICA Remote Application Manager program is a graphical user interface for selecting
ICA servers or Windows applications to connect to. It presents connection records that it
creates and connection records created by Network Station Manager. When a connection is
initiated, the ICA Client program is fork’ed and exec’ed.
When connecting to a description, the ICA Remote Application Manager created a new
process and starts an instance of the ICA Client program. Using information passed by the
ICA Remote Application Manager, the ICA Client connects to a Citrix server and establishes
an ICA session.
Ÿ
The ICA Client program connects to a Citrix application server and establishes a session.
The application window is presented within an X11 window on the Network Station.
On-line help associated with panels, commands
The User Interface section has been translated into HTML and is presented when the user
selects Help-->View detailed help.
Help files are located in the $MRIPATH/$LANG/ICAClient directory.
February 18, 2000
10
IBM Internal Use Only
Using the ICA Remote Application Manager
The following sections describe how to use the ICA Remote Application Manager to connect to a
Citrix server from your IBM Network Station:
Quick Start
To connect to a Citrix server you need to have a user name and password set up for you on the
server, and you need to know the name of the server and domain.
To run the ICA Remote Application Manager
From the launch bar, select Host Access ---> ICA Remote Application Manager.
From the command line, type the following command:
/usr/lib/ICAClient/wfcmgr <Return>
where /usr/lib/ICAClient is the directory in which you installed the ICA Remote
Application Manager.
Note: If the ICA Remote Application Manager has not been installed in the default installation
directory, ensure that the environment variable ICAROOT is set to point to the actual installation
directory.
The ICA Remote Application Manager window is displayed:
To define a connection
Note: If Network Station Manager had been used to define ICA connection entries, they will be
displayed. You may go to “To open a connection” or continue with defining a new connection
entry.
1. Choose New... from the Entry menu, or click the New Entry icon.
The Properties dialog box is displayed to allow you to define a new connection:
February 18, 2000
11
IBM Internal Use Only
2. Edit the Description to describe the connection definition you are creating.
The description is used to identify the connection definition in the ICA Remote Application
Manager window.
3. Select to connect to a Citrix Server or to a Published Application and then choose a Citrix
server or published application from the pull-down list.
4. If you want to log in as a specific user enter the appropriate details in the Username,
Domain, and Password fields.
Alternatively, you can leave the fields blank, in which case you are prompted for them, if
necessary, when you connect.
5. Click OK to create a connection definition containing the properties you have specified.
The ICA Remote Application Manager window shows the connection definition you have
created:
February 18, 2000
12
IBM Internal Use Only
To open a connection
Once you have created a connection file with the appropriate network connection properties set
up, you can connect to the Citrix server as follows:
Double-click the name of the connection definition you want to open in the ICA Remote
Application Manager window.
Alternatively, you can select the name of the connection definition and choose Connect from the
Entry menu, or click the Connect button:
This connects to the server specified in the connection file with the user name and password
details you have entered in the connection definition.
The following message then tells you which ICA server the ICA client is trying to connect to:
When the connection to the ICA server is complete, the following message is presented:
February 18, 2000
13
IBM Internal Use Only
Connecting to Citrix MetaFrame Servers
If you have not specified a user name or password in the connection file, you are prompted
to enter them if they are required by the server:
After a short delay the Windows desktop is displayed in a window on your IBM Network
Station:
To log off from Windows
Choose Logoff... from the Windows Start menu or, if your connection is set up to run an
application, choose Exit from the application's File menu. These two methods close the ICA
session and terminates the ICA Client.
February 18, 2000
14
IBM Internal Use Only
To disconnect from Windows
Choose Disconnect... (if available) from the Windows Start menu.
This leaves your session open on the Citrix server, and you can resume work where you left
off next time you log on to the server with the same user name and password.
When you reconnect, the server forces the ICA Client window to be the same size and
number of colors as in the original session.
Connecting to Citrix WinFrame Servers
If you are connecting to a Citrix WinFrame server, then the login window
and desktop window
have a different appearance.
To log off from Windows
Choose Log off... from the Windows Program Manager File menu or, if your connection is
set up to run an application, choose Exit from the application's File menu. These two
methods close the ICA session and terminates the ICA Client.
Alternatively, choose Close (if available) from the Window menu. This leaves the ICA Client
application running so that you can open another session, if you want.
February 18, 2000
15
IBM Internal Use Only
To disconnect from Windows
Choose Disconnect... (if available) from the Windows Program Manager File menu.
To quit from the ICA Remote Application Manager
Choose Exit from the Entry menu.
This leaves any connections to Citrix servers open.
To edit an existing connection definition
You can edit existing connection definitions, or create new connection definitions, in the ICA
Remote Application Manager window.
When you create a new connection definition, the default window size and window color settings
are those specified by the Settings... command on the Option menu.
For information about the properties you can specify for each connection see the section Editing
connections.
To edit an existing connection definition
1. Select the name of the connection you want to edit in the ICA Remote Application
Manager window.
2. Choose Properties... from the Entry menu, or click the Properties button.
The Properties dialog box shows the current properties of the selected connection.
3. Edit the properties you want to change, and then click OK to close the Properties
window.
Menus
The ICA Remote Application Manager has three menu buttons for managing connection entries,
setting options and presenting help.
February 18, 2000
16
IBM Internal Use Only
Entry menu
New...
Opens the Properties dialog box to allow you to create a new connection definition.
Copy...
Duplicates the currently selected connection definition so that you can create a new connection
based on an existing one.
Delete...
Deletes the currently selected connection definition.
Properties...
Displays the Properties dialog box to allow you to view or edit the properties of the currently
selected connection definition.
Connect...
Makes a connection to the Citrix server specified in the currently selected connection definition.
Exit
Exits from the ICA Remote Application Manager application.
Option menu
February 18, 2000
17
IBM Internal Use Only
Settings...
Displays the Settings dialog box to allow you to specify the default window settings for new
connection definitions, and enter other general settings.
Help menu
About ICA Client...
Displays the ICA Client version number.
View detail help
Display help text for ICA Client.
February 18, 2000
18
IBM Internal Use Only
Properties dialog box
This section explains in detail how to use the ICA Remote Application Manager to create and
edit connection definitions, giving you total control over your access to Citrix servers.
To display the connection properties
1. Select the name of the connection you want in the ICA Remote Application Manager
window.
2. Choose Properties... from the Entry menu, or click the Properties button:
The Properties dialog box shows the current properties of the selected connection:
Network
description, server name, user name, password, domain
Connection
compression, caching, sound, encryption
Window
number of colors, color mapping, window size
Application
application name, working directory
Firewall Settings SOCKS proxy
February 18, 2000
19
IBM Internal Use Only
Network
Description is used to identify the connection definition. It is a required field. The characters
;=#[]- are not allowed.
If Server is selected, enter the network name or address of the Citrix server. Selecting the ...
button will bring up a list of available Citrix servers. This make take some amount of time.
The allowable characters are upper and lower case alphanumeric, plus the special
characters period, underscore and dash. None of the special characters can be first or last.
If Published Application is selected, enter the name of the published application. The
characters ;=#[]- are not allowed. Selecting the ... button will bring up a list of published
applications. This make take some amount of time.
Either the Server name or the Published Application name is required.
The Username, Domain, and Password are used as login parameters and should match
those set up on the specified Citrix server. If you do not provide these login parameters you
are prompted for them each time you connect.
February 18, 2000
20
IBM Internal Use Only
Connection
Select Use Data Compression to reduce the amount of data transferred across the ICA
session. This requires additional processor resources to compress and decompress the data,
but can increase performance over bandwidth-limited connections.
Select Use Disk Cache for Bitmaps to enable persistent caching of frequently used icons
and bitmaps. The persistent cache is always cleared when the IBM Network Station is
re-booted. Internal caching is not affected by this option. Persistent caching must be enabled
by following the ICA persistent caching directions in the /.profile file.
Select Enable Sound to enable sound support. Select High, Medium, or Low quality
depending on the available bandwidth. The higher the sound quality, the more bandwidth is
used.
Select the Encryption Level for the ICA session. The default level is Basic. Strong
encryption is available using RCA RC5 for 40, 56 and 128 bit session keys. Select RC5
128-bit Login Only to use encryption only during authentication. Selecting RC5 encryption
disables automatic login to the Citrix server.
February 18, 2000
21
IBM Internal Use Only
Window
Window Colors allows you to set the number of colors the Windows application should use
to 16 or 256.
No Window Borders allows you to run the ICA Client in a window with out borders or title
bar. Typically, the window manager will attach borders and a title bar to windows that appear
on the desktop.
256 Color Mapping allows you to set up 256 color sessions to use approximate or exact
colors. Use Approximate Colors to eliminate color flashing when switching context. Note that
if other applications have allocated all 256 colors the client will fall back to using a private
colormap.
Window Size allows you to select one of four standard window sizes, Full Screen, or a
Custom size. If Custom is specified then Width must be between 300 and 1280 and Height
is specified, is must be between 300 and 1024.
Select Use Default to use the default window size, window colors or 256 color mapping
setting specified with the Settings... command on the Option menu; refer to Window
Settings....
February 18, 2000
22
IBM Internal Use Only
Application
Allows you to specify the pathname of an application to be run after connecting to the Citrix
server. For example, to run Microsoft Word automatically after connecting to the Citrix
server you might enter:
C:\WINWORD\WINWORD.EXE
If you specify an application then you do not see the Windows desktop, and the connection is
closed when you quit from the application.
The Working Directory allows you to specify the pathname of a working directory to be
used with the application.
Note: If you have selected to connect to a published application the Application dialog box
will not be available.
February 18, 2000
23
IBM Internal Use Only
Firewall Settings
Selecting Connect Via SOCKS Proxy allows your ICA session to connect to an ICA Server
via a SOCKS Proxy Server.
Specify the Address of proxy to use (network name or network address) and the Port
number to use.
February 18, 2000
24
IBM Internal Use Only
Settings dialog box
The Settings dialog box allows you to specify the default window settings used when you create
a new connection file. It also allows you to enter a Citrix name server TCP/IP address.
To display the Settings dialog box choose Settings... from the Option menu.
It contains the following panels:
Preferences
keyboard type and layout, alert sounds, com port devices
Window
default color and size choices
Server Location
server groups, server lists
HotKeys
<Alt><F1-F12>, <Alt><Tab>
Drive Mapping
enable/read/write, directory to drive mapping
Firewall Settings enable alternate network address, SOCKS proxy server
February 18, 2000
25
IBM Internal Use Only
Preferences
Keyboard Layout specifies the keyboard layout used by the ICA Client.
If (Auto Detect) is selected then the ICA Client will automatically detect and use the
keyboard layout configured by the IBM Network Station Boot Monitor.
If (User Profile) is selected then the Citrix server specifies the keyboard layout based on the
user’s Citrix server profile.
If neither of these options are suitable, one of the following explicit keyboard layouts can be
selected:
Bulgarian
French (Canadian 1992)
Croatian
French (Swiss)
Czech
Danish
Dutch
Dutch (Belgian)
English (UK)
English (US)
English (US ISO)
Finnish
German
German (Swiss)
Greek
Hungarian
Icelandic
Italian
Italian (Swiss)
Japanese (ATOK11)
February 18, 2000
26
Polish (Programmer)
Portuguese
Portuguese (Brazilian)
Romanian
Russian
Slovakian
Slovenian
Spanish
Spanish (Latin American)
Swedish
IBM Internal Use Only
French
French (Belgian)
French (Canadian 1988)
Japanese (MS-IME98)
Norwegian
Polish
Turkish (F)
Turkish (Q)
Keyboard Type specifies the keyboard type to be used with the ICA Client. Select (Default).
Enable Windows Alert Sounds if selected causes Windows alert sounds to be played using
the IBM Network Station sound system.
COM Port Devices allows bi-directional mapping of IBM Network Station serial devices, e.g.
/dev/tty00, to Citrix Server COM ports.
Window
These settings are used as the default for all new connection files.
Window Colors allows you to set the number of colors the Windows application should use
to 16 or 256.
No Window Borders allows to manage the window borders and title bar that surround an
ICA session.
February 18, 2000
27
IBM Internal Use Only
256 Color Mapping allows you to setup 256 color sessions to use approximate or exact
colors.
Window Size allows you to select one of four standard window sizes, Full Screen, or a
Custom size. If Custom is specified then Width must be between 300 and 1280 and Height
is specified, is must be between 300 and 1024.
Server Location
Provides a more redundant method for locating the Master ICA Browser. The Master ICA
Browser is queried to create a list of all Citrix servers and published applications on the
network.
If (Auto-Locate) is specified in the Address List box, the ICA Client broadcasts a Get
Nearest Citrix server packet. The first Citrix server to respond is queried for the address of
the ICA Master Browser server.
If Citrix servers are specified in the Address List box, the ICA Client sends a request for the
address of the Master ICA Browser to each of the servers listed in the Primary group. If there
is no response, requests are sent to each of the servers listed in the Backup 1 group. If there
is no response from the Backup 1 group, requests are sent to the servers listed in the
Backup 2 group.
February 18, 2000
28
IBM Internal Use Only
Some network configurations use routers or gateways to filter broadcast packets. Specifying
Citrix servers allows the ICA Master Browser to be located on these types of networks.
Note: If the Master ICA Browser cannot be located, you can connect to Citrix servers directly
by specifying the TCP/IP address as the server location.
Hotkeys
Allows you to define alternative key combinations for the hot keys. The following table shows
the hot keys reserved for X Windows and the default alternative key combinations.
X Window Hot
Key Combination
Default Alternative
Key Combination
<Alt><F1>
to
<Alt><F12>
<Alt><Ctrl><F1>
to
<Alt><Ctrl><F12>
<Alt><Tab>
<Ctrl><Tab>
<Alt><Shift><Tab>
<Ctrl><Shift><Tab>
You can change the definitions by selecting alternative keys from the pop-up menus.
February 18, 2000
29
IBM Internal Use Only
Any <Alt> key combinations not used by your X Window manager can be used as normal
within your Citrix session.
In addition, the key combination <Ctrl><Alt><Enter> can be used to produce the PC key
combination <Ctrl><Alt><Delete>.
Drive mappings
You can configure the ICA Client so that you can access any directory mounted on your IBM
Network Station, including CD-ROMs, from the Citrix server session as PC drive letters.
After changing drive mapping settings you need to log off and reconnect to the Citrix server
for the changes to take effect; simply disconnecting is not sufficient.
For each Windows NT drive letter, the Drive mapping list shows the disk or path name of the
IBM Network Station directory mapped to the drive, and the Enable/Read/Write access.
To map a Citrix server drive to a directory on your IBM Network Station:
1. Select the drive you want to map; for example G:.
February 18, 2000
30
IBM Internal Use Only
If the drive you have mapped is not available on the Citrix server, the directory you have
specified is mapped to another free drive letter.
2. Click Modify to change the drive mapping. A file selection dialog is displayed to allow
you to select the IBM Network Station directory to map.
3. Select the directory (e.g. /tmp) you want to map to and click OK. The directory is shown
in the Drive mapping list.
To enable access to a specific drive, click the check box next to the corresponding drive.
To change the access to a drive, click the appropriate read/write icons corresponding to the
drive. (Typically, only the $HOME and /tmp directories are writable.) The meaning of the
icons areas follows:
Icon
Meaning
Read access
Prompt for read access on first access per session
No read access
Write access
Prompt for write access on first access per session
No write access
To enable drive mapping, select Enable Drive Mapping. This enables drive mapping for all
your connection definitions.
Depending on the setup of the server, your mapped drives may or may not be immediately
available. They may also be mapped to different server drive letters than those you specified
in the Drive Mapping panel, because the drives you specified have already been assigned
by the server.
For WinFrame
To find out the current status of your mapped drives, once connected to the Citrix server,
open the File Manager and click the drive letter pull-down menu in the top left of the File
Manager window.
This displays which local or client drives are mapped to which server drives.
Client drives are shown in the format \\Client\drive where drive is the drive letter
specified in the Drive Mapping panel.
If a drive you specified in the Drive Mapping panel is not shown in this list you can connect
it to a server driver letter as follows:
1. In the File Manager select Connect Network Drive? from the Disk menu.
2. In the Connect Network Drive dialog box, select the server drive you want to map the
client drive to in the Drive pull-down menu.
February 18, 2000
31
IBM Internal Use Only
3. If you want to have this drive available to you each time you log into this server, ensure
that the Reconnect at Logon box is checked.
4. Double-click the Client Network icon in the Shared Directories list, then click the
appropriate client icon for your IBM Network Station directory. This displays a list of the
available local drives, previously set up in the Drive Mapping panel.
5. Select the drive you want to map to the selected server drive and click OK. Your local
drive will now be available.
Repeat the above steps for each of the local drives you wish to attach to the server drives.
For MetaFrame
To find out the current status of your mapped drives, once connected to the Citrix server,
open the NT Explorer. Client drives are shown in the format <drive>$ on 'Client'(<drive>:)
where <drive> is the drive letter specified in the Drive Mapping panel.
File naming conventions
As UNIX is a case sensitive file system and Windows NT is case insensitive, problems may
occur if you use UNIX files within the ICA Client session whose names are identical except
for their case. For example, ReadMe and README.
In such circumstances, although Windows NT displays the names correctly in a file listing,
when a file is referred to, for example as a link in an HTML file, the first file found is used.
It is therefore recommended that any files you intend to use within the ICA Client session
have unique names.
February 18, 2000
32
IBM Internal Use Only
Firewall Settings
The
Use alternate address for firewall connection feature is used to browse for Citrix servers
or published applications that are inside a firewall from a client machine that is outside the
firewall. The firewall and the Citrix servers must be configured to map the internal network
addresses of Citrix servers to external internet addresses. Enter the external internet
addresses in the Address List.
Do not use the Use alternate address for firewall connection check box except on the
advice of your administrator.
Selecting Connect Via SOCKS Proxy allows your ICA session to connect to an ICA Server
via a SOCKS Proxy Server.
Specify the Address of proxy to use (network name or network address) and the Port
number to use.
February 18, 2000
33
IBM Internal Use Only
Using the ICA Client
The following sections describe how to use the ICA Client to connect to a Citrix server from your IBM
Network Station.
Quick Start
To connect to a Citrix server you need to have a user name and password set up for you on the
server, and you need to know the name of the server and domain.
To run the ICA Client
Type the following command at the command line prompt:
/usr/lib/ICAClient/wfica <Return>
where /usr/lib/ICAClient is the directory in which you installed the ICA Client.
Note: If the ICA Client has not been installed in the default installation directory, ensure that the
environment variable ICAROOT is set to point to the actual installation directory.
The ICA Client host name dialog is displayed:
Enter the host name of the Citrix server that you want to connect to and press the Enter key or
click the OK button.
After connecting to the Citrix server, the Citrix server may prompt you to enter your user id and
password. After a short delay the Windows desktop is displayed in a window on your IBM
Network Station.
Command Line Parameters
There are two executable programs in the IBM Network Station ICA package.
Ÿ
The ICA Remote Application Manager program, wfcmgr, is a graphical user interface for
selecting ICA servers or Windows applications to connect to. It presents connection records that
it creates and connection records created by Network Station Manager. When a connection is
initiated, the ICA Client program is fork’ed and exec’ed.
Ÿ
The ICA Client program, wfica, connects to a Citrix application server and establishes a session.
The application window is presented within an X11 window on the Network Station.
ICA Remote Application Manager - wfcmgr
There is a small set of command line parameters for the ICA Remote Application Manager. The
-description, -icaroot and -file parameters came with the Citrix source code. The others have
been added to provide addition value to the IBM Network Station.
Usage: wfcmgr [options]
Where [options] are:
-help
-noupdate
-desc[ription] <string>
-icaroot <directory>
-file <filename>
-g[eometry] <WxH±X±Y>
-UseFullScreen [<bool>]
-NoWindowManager [<bool>]
-log
Show this message
Configuration/Connection updates not allowed
Connection description from connection file
Installation directory (full path name)
Connection file name
X11 window <Width x Height ± X_off ± Y_off>
X11 window full screen [ <true | false> ]
X11 window without borders [ <true | false> ]
Enable ASSERT logging
-help
the usage text (as shown above) is sent to the console.
-noupdate
when this option is specified, updates to the connection file and/or
the configuration file are not allowed.
-description <text>
the full text from the Description field of the connection definition
dialog. If this argument is not specified, then the first description in
the [ApplicationServers] section of the appsrv.ini file will be used.
-file <name>
the fully qualified file name of the file that contains the connection
description to be used. If the HOME environment variable is defined
then the default file name is $HOME/.ICAClient/appsrv.ini.
Otherwise, the default file name is
/usr/lib/ICAClient/config/appsrv.ini.
-icaroot <directory>
the fully qualified directory where the ICA client package was
installed. If not specified then the ICAROOT environment variable is
accessed to get the directory. If neither the -icaroot argument nor
the ICAROOT environment variable are used to define the install
directory, then by default, it is /usr/lib/ICAClient.
February 18, 2000
35
IBM Internal Use Only
-geometry <WxH±X±Y>
the X11 window Width, Height, X offset and Y offset. All values are
in pixels. Positive X offsets are from the top of the screen, negative
from the bottom. Positive Y offsets are from the left side of the
screen, negative from the right. Variations of this specification
include <WxH> and <±X±Y>.
By default, the wfcmgr window is centered on the screen. To
position the wfcmgr window in the upper left corner of the screen,
specify -geometry +0+0.
-UseFullScreen [<bool>] when this option is set to True then the wfcmgr window be the size
of the full screen. Allowable values are True and False. Default
value is False.
-NoWindowManager [<bool>]
when this option is set to True then the wfcmgr window will
not have borders nor title bar. Allowable values are True and False.
Default value is False.
-log
enables ASSERT logging. ASSERTs are program sanity tests that
wfcmgr can make. Typically these test are not enabled because
they tend to impact performance.
ICA Client - wfica
The Version 1 Release 3.0 ICA command line parameters will continue to be supported. This
allows for Version 1 Release 3.0 ICA migration. The command line parameters have precedence
over the .ini files.
Usage: wfica [ica_options] [ns_options [-- <application>]]
Where [ica_options] are:
-help
-version
-quiet
-desc[ription] <string>
-file <filename>
-protocolfile <filename>
-clientfile <filename>
-icaroot <directory>
Show this message
Show version information
Suppress connection dialogs
Connection description from connection file
Connection file name
Protocol file name
Configuration file name
Installation directory (full path name)
And [ns_options] are:
-s[erver] <name>
-b[rowser] <namelist>
-u[sername] <name>
-p[assword] [<password>]
-do[main] <name>
-na[me] [<name>]
-c[olor] <16 | 256>
-en[cryption] <level>
-WorkingDirectory <path>
-g[eometry] <WxH±X±Y>
-UseFullScreen [<bool>]
-NoWindowManager [<bool>]
February 18, 2000
NT server name
NT browser name list <name[:name: ... :name]>
NT login user name
NT login password
NT domain name
NT CLIENTNAME
NT number of colors
NT encryption level <basic | login | 40 | 56 | 128>
NT working directory
X11 window <Width x Height ± X_off ± Y_off>
X11 window full screen [ <true | false> ]
X11 window without borders [ <true | false> ]
36
IBM Internal Use Only
-ti[tle] <title>
-ca[che] <size>
-shm <size>
-log
-<keyword> <value>
-- <application>
X11 Window title
Cache size in Kbytes
Shared memory size in Kbytes
Enable ASSERT logging
Override .ini files with “keyword=value”
Initial program OR published application
ICA Options
-help
the usage text (as shown above) is sent to the console.
-version
the following message is sent to the console:
IBM Network Station ICA Client
Version 2.0 (Build dd/mm/yyyy - hh:mm:ss)
Copyright International Business Machines Corp. 1999
All rights reserved
Citrix ICA Client for Unix
Version 3.00.15
Copyright 1998-1999 Citrix Systems, Inc.
All rights reserved
-quiet
connection dialogs will not be presented to the user. By default, the
ICA client will present a “connecting to” dialog followed by a
“connected to” dialog. Both of these dialogs are informational and
require no response by the user.
-description <text>
the full text from the Description field of the connection definition
dialog.
Either -description or -server or -- <application> must be
specified. If neither of these parameters are specified then the user
will be prompted for a server name.
-file <name>
the fully qualified file name of the file that contains the connection
description to be used. If the HOME environment variable is defined
then the default file name is $HOME/.ICAClient/appsrv.ini.
Otherwise, the default file name is
/usr/lib/ICAClient/config/appsrv.ini.
-protocolfile <name>
the fully qualified file name of the file that contains the protocols
supported by the ICA client. By default, the file name is
/usr/lib/ICAClient/config/module.ini. This is a system
configuration file and not meant to be modified.
-clientfile <name>
the fully qualified file name of the file that contains the options and
defaults for all connection descriptions. If the HOME environment
variable is defined then the default file name is
$HOME/.ICAClient/wfclient.ini. Otherwise, the default file
name is /usr/lib/ICAClient/config/wfclient.ini.
-icaroot <directory>
the fully qualified directory where the ICA client package was
installed. If not specified then the ICAROOT environment variable is
accessed to get the directory. If neither the -icaroot argument nor
February 18, 2000
37
IBM Internal Use Only
the ICAROOT environment variable are used to define the install
directory, then by default, it is /usr/lib/ICAClient.
NS Options
Note: NS Options can not be combined with the -description
parameter.
-server <name>
specifies the ICA application server to connect to. The name can be
a fully qualified network host name, an abbreviated network host
name or a dotted decimal network address.
Either -description or -server or -- <application> must be
specified. If neither of these parameters are specified then the user
will be prompted for a server name.
-server and -browser are mutually exclusive.
-browser <namelist>
specifies the name of a master browser. The master browser is an
ICA server that tells the ICA client which ICA application server to
connect to and which application to run on that server.
A colon “:” separated list of master browsers can be specified. Each
name can be a fully qualified network host name, an abbreviated
network host name or a dotted decimal network address.
If neither -server nor -browser is specified and -- <application>
is specified then the ICA Client will broadcast (typically to the local
subnet) to get a master browser name.
Either -description or -server or -- <application> must be
specified.
-server and -browser are mutually exclusive.
-username <name>
specifies the NT server login user name.
-password [<password>] specifies the NT server login password. The following password
formats are supported:
NSM Format:
The NSM format is checked first. This is a repeating
sequence of the ‘%’ character followed by two
hexadecimal characters. For example, the following
is an NSM encrypted password:
%B2%86%C8%78
ICA Format:
The ICA format is checked second. This is a
string of hexadecimal decimal characters. The first
four characters specify the number of bytes required
to contain the binary form of the remaining
hexadecimal characters. For example, the following
is an ICA encrypted password:
0005a986568f51
February 18, 2000
38
IBM Internal Use Only
In-the-clear:
If the password is neither an NSM password nor an
ICA password then it is assumed to be an
unencrypted password. For example, the following
is neither an NSM nor an ICA encrypted password.
Hence it is an unencrypted password:
mypw
If -password is specified without a <password> then an NSM
formatted password is requested from the actlogind daemon.
-domain <name>
specifies the NT server domain name.
-name <clientname>
specifies the client name to be used by the ICA application server. If
the client name is longer than 20 characters (an ICA protocol
limitation) then it is truncated to 20 characters.
If -name is specified but is not followed by a host name then the
fully qualified host name will be obtained from the system and
converted to a simple host name. A simple host name is defined to
be the first name in a fully qualified dotted name string. (In other
words, everything is truncated after the first decimal point.) If the
resulting string is longer than 20 bytes (an ICA protocol limitation)
then it is truncated to 20 bytes.
If -name is not specified then the fully qualified host name is
obtained from the system. If it is longer than 20 characters (an ICA
protocol limitation) then the dotted decimal IP address string will be
used.
-color <number>
specifies the number of colors that the ICA application server should
use to generate application graphics. Allowable values are 16 and
256.
-encryption <level>
specifies the level of encryption to be used between the ICA client
and the ICA application server. Supported encryption levels are:
basic
login
40
56
128
simple encryption (this is the default)
128-bit RSA encryption for login only
40-bit RSA encryption
56-bit RSA encryption
128-bit RSA encryption
If any level of encryption is specified other than basic, then any
client side specification of username, password and/or domain,
whether from the command line or from an INI file, will not be used.
(The intent here is to insure the user logs into the NT server via the
NT login dialog.)
-WorkingDirectory <path>
-geometry <WxH±X±Y>
February 18, 2000
specifies the NT working directory path.
the X11 window Width, Height, X offset and Y offset. All values are
in pixels. Positive X offsets are from the top of the screen, negative
from the bottom. Positive Y offsets are from the left side of the
39
IBM Internal Use Only
screen, negative from the right. Variations of this specification
include <WxH> and <±X±Y>.
The window width may range from 300 to 1280. The window height
may range from 300 to 1024.
By default, the wfica window is centered on the screen. To position
the wfica window in the upper left corner of the screen, specify
-geometry +0+0.
-UseFullScreen [<bool>] when this option is set to True then the wfica window be the size of
the full screen. Allowable values are True and False. Default value
is False.
-NoWindowManager [<bool>]
when this option is set to True then the wfica window will
not have borders nor title bar. Allowable values are True and False.
Default value is False.
-title <text>
puts the specified text into the X11 window title bar.
-cache <size>
size in kilobytes of the internal ICA Client transient cache.
-shm <size>
size in kilobytes of shared memory to be allocated. If size is greater
than zero then the X11 Shared Memory extension is enabled.
-log
enables ASSERT logging. ASSERTs are program sanity tests that
wfica can make. Typically these test are not enabled because they
tend to impact performance.
-<keyword> <value>
any unrecognized arguments will be analyzed to see if they qualify
as a command line keyword=value pair. Any such keyword=value
pairs are assumed to be valid .INI file entries and will be
concatenated with the keyword=value pairs extracted from the INI
files.
<keyword>=<value> pairs are not checked for validity. Hence, the
ability for the ICA client to detect and report command line errors is
limited.
-- <application>
specifies the program that the ICA application server should run if
the -server argument is also specified. Otherwise it specifies a
published application and a master browser will be contacted to get
both the program to run and the ICA application server to run it on.
This parameter must be last.
Either -description or -server or -- <application> must be
specified. If neither of these parameters are specified then the user
will be prompted for a server name.
If -- <application> is not specified then a default description must
exist in an accessible connection file.
Deprecated Command Line Arguments
The following V1R3 command line arguments have been deprecated. They can still be used in the
V1R3-to-V2R1 migration strategy but they should not be published.
February 18, 2000
40
IBM Internal Use Only
-host <name>
same as -server <name> if -lb is not specified. If -lb is specified
then it is the same as -browser <name>
-lb
governs how the -host parameter will work.
-restart
ignored.
-geometry fullscreen
same as < max_screen_width x max_screen_height + 0 + 0 >
FLASH Boot Support
When booting the IBM Network Station from a flash card, several Boot Monitor fields may be
available. In particular, one of the three Boot Host fields can be used to specify the IP address of an
ICA server or ICA master browser.
Additional unused Boot Monitor (text) fields may be also used to specify ICA command line
parameters. The Boot Monitor storage for these additional ICA command line parameters is limited.
The ICA Client supports the following additional command line parameters to support flash boot:
-server1
indirectly specifies the -server parameter where the server <name>
comes from the First Boot Host parameter in NVRAM.
-server2
indirectly specifies the -server parameter where the server <name>
comes from the Second Boot Host parameter in NVRAM.
-server3
indirectly specifies the -server parameter where the server <name>
comes from the Third Boot Host parameter in NVRAM.
-browser1
indirectly specifies the -browser parameter where the browser
<namelist> comes from the First Boot Host parameter in NVRAM.
-browser2
indirectly specifies the -browser parameter where the browser
<namelist> comes from the Second Boot Host parameter in
NVRAM.
-browser3
indirectly specifies the -browser parameter where the browser
<namelist> comes from the Third Boot Host parameter in NVRAM.
-nvram <fieldname>
specifies the name of a text field in nvram. The text field will be
analyzed and, if the first non-blank character is a dash (-), then the
text will be used to replace the -nvram <fieldname> specification.
Use the Boot Monitor to enter text in selected fields. The table below
give the NVRAM filed name for selected Boot Monitor fields which
may be available.
Series 2xxx Boot Monitor Field Name
February 18, 2000
NVRAM Field Name
Boot file server dir and file name (second)
second-boot-path
Boot file server dir and file name (third)
third-boot-path
Workstation directory (second)
config-unix-directory2
41
IBM Internal Use Only
Series 1xxx Boot Monitor Field Name
Configuration file
NVRAM Field Name
config-custom-file
For example, to specify multiple ICA browsers on a Series 2800, the
following text could be entered in the Boot Monitor field called Boot
file server dir and file name (third):
-b 9.8.7.201:9.8.7.104:server2 -- MyApplication
Then the command
wfica -nvram third-boot-path
will actually be interpreted as
wfica -b 9.8.7.201:9.8.7.104:server2 -- MyApplication
The -server1, -server2, -server3, -browser1 , -browser2 and -browser3 arguments are
mutually exclusive.
Locking Keys
By default, the operator controls the locking state of the keyboard on the Network Station. When the
operator presses a locking key (CapsLock or NumLock), the keyboard goes into the appropriate lock
state. If the active window is the ICA client, then the locking key is sent to the active Windows
application on the ICA server. Typically, this synchronizes the locking state and the LEDs between
the Network Station and the ICA server.
However, a few Windows applications (notably VT100 emulators) process the NumLock key as a
function key. As a result, the NumLock state of the ICA server is not changed and NumLock
synchronization between the ICA server and the Network Station does not end until the NumLock
key is pressed again.
To help control this situation, the ICA client (wfica) supports the following command line option:
-NumLockSync <bool>
when this option is set to False then the ICA server controls the
NumLock state of the wfica window. Default value is True.
The keyboard locking state will always be in sync with the active window. In effect, each Network
Station window, including the window that ICA is running in, will perceive that the keyboard is in the
correct lock state. However, the Network Station windowing system (X11) always toggles the
NumLock LED every time the NumLock key is pressed. As a result, the NumLock LED may not
always reflect the NumLock state of the ICA window if -NumLockSync False is specified.
February 18, 2000
42
IBM Internal Use Only
.INI Configuration Files
The four configuration files associated with the ICA Client are:
appsrv.ini
defines the properties for each application server connection configured. This
file is modified by the ICA Remote Application Manager when the user modifies
any of the properties in the Entry-->Properties... menu.
wfclient.ini
defines global user settings, such as keyboard layout and hotkeys. This file is
modified by the ICA Remote Application Manager when the user modifies any of
the settings in the Option-->Settings... menu.
module.ini
defines the default communications stack settings. This file cannot be modified
by the ICA Remote Application Manager and should not be modified by the user.
keyboard.ini
defines keyboard menus, references to keyboard definition files. This file cannot
be modified by the ICA Remote Application Manager and should be modified by
the user.
These files are styled after Microsoft Windows .ini files with named sections containing entry names
and entry values. The client user interface, ICA Remote Application Manager, reads and writes the
appsrv.ini and wfclient.ini files.
The .ini files are located in a system mounted (remote) read-only file systems. The base directory
path name for these .ini files comes from the full path name of the executable (wfcmgr or wfica).
This can be over ridden by the ICAROOT environment variable.
In addition, the appsrv.ini and wfclient.ini files are created in the $HOME/.ICAClient directory.
(This mode of operation is triggered by the existence of an $ICAROOT/config/.server file. It
serves no other purpose.) If the HOME environment variable does not exist, then the ICA Remote
Application Manager goes into “no update” mode and will only display connection records from the
Registry.
.ini files reside in the following locations:
r--r--r-r--r--r-r--r--r-r--r--r-rw-r--r-rw-r--r--
$ICAROOT/config/module.ini
$ICAROOT/config/wfclient.ini
$ICAROOT/config/appsrv.ini
$ICAROOT/keyboard/keyboard.ini
$HOME/.ICAClient/wfclient.ini
$HOME/.ICAClient/appsrv.ini
New user .ini files are created by the ICA Remote Application Manager when and if new connection
records are created. The ICA Remote Application Manager creates the user .ini files by copying their
counterpart files from the $ICAROOT/config directory. Connection records are then added to the
appsrv.ini file in the user’s $HOME/.ICAClient directory
.INI File Contents
The parameters listed in each file are grouped into sections. Each section begins with a name in
square brackets indicating parameters that belong together; for example, [ClientDrive] for
parameters related to Client Drive Mapping (CDM).
In most cases, uniquely named parameters (for example, TcpNoDelay) may be placed under
different headings, or even in a different file, without effect. This is possible because all the .ini
February 18, 2000
43
IBM Internal Use Only
files are read into contiguous memory before being parsed. However, some settings may be put
in the connection-specific section in appsrv.ini, or in the [Thinwire3.0] section of wfclient.ini. In
these cases, the value in [Thinwire3.0] is a default which applies to all connections unless
overridden by a connection-specific value. Examples of this are DesiredColor, DesiredHRES,
and DesiredVRES.
Defaults are automatically supplied for any missing parameters except where indicated. If a
parameter is present but is not assigned a value then the default is automatically applied; for
example, if InitialProgram is followed by '=' but no value then the default (not to run a program
after logging in) is applied.
Note
Boolean parameters may use 'No', 'False', 'Off' or '0' to indicate FALSE, and 'Yes', 'True',
'On' or '1' to indicate TRUE.
For all parameters, spaces are significant and values are case-sensitive.
Parameters that may be modified from the user interface are in bold typeface. Parameters
that cannot be modified from the user interface, but are read by the client, are in normal
typeface. Those marked as 'ignored' are not currently used by the client, but may be
reserved for future use, redundant, or used by other versions of the client; for example,
Win32 or Macintosh. In the last case the parameter is read by the client but the result
discarded.
appsrv.ini
This .ini file maintains a description for each defined server connection. There is a section for
each connection. The section header contains the name of the connection. Within the section
are parameters that define the target logon. They also contain parameters that can override
those found in Module.ini. Also in this file (section [WFClient]) are user interface settings.
Item
[WFClient]
Version=1
[ApplicationServers]
connection_definition=
[connection_definition]
Description
This section is used by the engine. It contains default
session-oriented parameters
fixed value; ignored
This section contains an entry for each defined
server connection. For each name there is a section
to describe the connection.
One connection definition for each configured
connection
Each connection definition has its own section
DesiredColor=[1|2]
1 = 16 color, 2 = 256 colors, default = 2. If not
present, default value from the [Thinwire3.0] section
of wfclient.ini used.
DesiredVRES=integer
vertical window size; default = 480. If not present,
default value from the [Thinwire3.0] section of
wfclient.ini used.
February 18, 2000
44
IBM Internal Use Only
Item
Description
DesiredHRES=integer
horizontal window size; default = 640. If not present,
default value from the [Thinwire3.0] section of
wfclient.ini used
Password=string
encrypted password, default = 000100
Domain=string
login domain, no default
UserName=string
login user name, no default
Address=string
application name, server, or IP address with optional
port, no default
InitialProgram=string
program to run after login, no default
WorkDirectory=string
working directory after login, no default
UseDefaultSettingsForColormap=boolean
use default setting for color approximation, default =
True
ApproximateColors=boolean
use colors from the local desktop palette to display
the ICA Windows sessions; default = False. If not
present, default value from the [Thinwire3.0] section
of wfclient.ini used
PersistentCacheEnabled=boolean
default = False
ServerToClientPowerOf2=integer
0 if data compression off; default = 15 if on
ServerToClientNormalPowerOf2=integer
default is 18
ServerToClientMaximumPowerOf2=integer
default is 17
ClientToServerPowerOf2=integer
0 if data compression off; default = 12 if on
ClientToServerNormalPowerOf2=integer
default is 15
ClientToServerMaximumPowerOf2=integer
default is 16
ClientAudio=boolean
client audio enabled; default = On
AudioBandwithLimit=[0|1|2]
audio quality; 0=low, 1=medium, 2=high, default is 1
UseFullScreen=[Yes|No]
attempt to use full screen mode with allowance for
window manager, default=No
NoWindowManager=boolean
disables scroll bars around client, assumes no
window manager, default=0
WinStationDriver='ICA 3.0'
fixed value
TransportDriver='TCP/IP'
fixed value
February 18, 2000
45
IBM Internal Use Only
Item
Description
ConnectTTY=False
fixed value
ConnectTTYDelay=1000msec
fixed value
The password in appsrv.ini must be encrypted as follows:
1. Encrypt the string using the following algorithm
seed = 0x43
encrypt[i] = string[i] ^ (encrypt[i-1] ^ seed)
2. Prepend the encrypted string (which is now binary) with the single-byte Seed value.
3. Prepend the encrypted string with its length in bytes as a 16-bit big-endian value.
4. Convert the encrypted string, including length and Seed, back to ASCII a nibble at a time
(from left to right) by converting each nibble value 0x0 to 0xf to characters '0', '1'...'9',
'A'...'F'.
Wfclient.ini
This .ini file contains a section for parameters specific to the client’s user interface, such as
version number and desired resolution.
Item
[WFClient]
Description
This section is used by the engine. It contains default
session-oriented parameters
Hotkey1..12Char=[F1...F12,Plus,Minus,Tab]
function key to use for mapping hotkey sequences
Alt+Fn, Alt+Tab, Alt+Shift+Tab
HotKey1..14Shift=string
shift state to get hotkey mapping for Alt+Fn; for
example, 'Alt+Ctrl'
DisableSound=boolean
disable Windows alert sounds, default=False
DrivePathA..Z=string
UNIX file path for Client Drive Mapping, no default
DriveEnabledA..Z=boolean
True if drive is mapped, default=False
DriveReadAccessA..Z=[0|1|2]
0=full access, 1=no access, 2=ask user, default=0
DriveWriteAccessA..Z=[0|1|2]
0=full access, 1=no access, 2=ask user, default=0
KeyboardLayout=string
keyboard layout from module.ini,
default='(Auto Detect)'
KeyboardMappingFile=string
name of file in /usr/lib/ICAClient/keyboard,
default='automatic.kbd'
KeyboardDescription=string
description of keyboard mapping, default='Automatic
(Default)'
ClientDrive=[On|Off]
determines if Client Drive Mapping is on, default=On
ClientManagement=[On|Off]
determines if Client Management is on, default=Off
February 18, 2000
46
IBM Internal Use Only
Item
Description
TcpBrowserAddress=string
server name or IP address to use for browsing, no
default, use broadcast
TcpBrowserAddress1..14=string
server name or IP address to use for business
failover, no default
TcpGroupName1..3=string
business failover group name, no default
UpdatesAllowed=boolean
allow client management updates, default=False
UseAlternateAddress=boolean
use alternate address for firewall connections,
default=False
ComPort1..4=string
com port device name, no default
LastComPortNum=integer
last com port device number used, default =0
MouseDoubleClickTimer=integer
mouse double-click time, default=500msec
MouseDoubleClickWidth=integer
mouse double-click width in pixels, default=4
MouseDoubleClickHeight=integer
mouse double-click height in pixels, default=4
ClientUnicodeEnabled=boolean
client can use Unicode, default=False
SaveSettingsOnExit=boolean
determines if wfcmgr settings are saved on exit,
default=True
SplashDelay=integer
length of time splash screen appears, default=2
seconds
DisableCtrlAltDel=boolean
disable Ctrl+Alt+Del event, default= False
MinimizeOnUse=boolean
minimize wfcmgr on connection, default=False
ClientPrinter=boolean
determines if Client Printer Mapping is on,
default=On
ClientComm=[On|Off]
determines if Client Comm Port Mapping is on,
default=On
IgnoreFileChangeSize=boolean
stops timeout copying large files to floppies,
default=False
KeyboardTimer=integer
keyboard event flush interval, default=100msec
MouseTimer=integer
mouse event flush interval, default=100msec
MapMouseButton2=boolean
map mouse button 2 to right mouse button,
default=False
LanaNumber=integer
NetBIOS LanA number, ignored
NetBiosBrowserAddress=string
NetBIOS server name or address to use for
browsing, ignored
IpxBrowserAddress=string
NetWare server name or IPX address to use for
browsing, ignored
Version=integer
fixed value=2, overrides value in appsrv.ini, ignored
LogKeyboard=boolean
turn on keyboard event logging, default=False,
ignored
February 18, 2000
47
IBM Internal Use Only
Item
Description
LogReceive=boolean
turn on packet receipt event logging, default=False,
ignored
LogTransmit=boolean
turn on packet transmission event logging,
default=False, ignored
LogErrors=boolean
turn on protocol error event logging, default=True,
ignored
LogConnect=boolean
turn on connection event logging, default=True,
ignored
LogAppend=boolean
append to existing logfile, default=False, ignored
LogFile=string
logfile name, default=wfclient.log, ignored
DisableClientAutoQuit=boolean
quit client on disconnect, default=True, ignored
XmsReserve=integer
default=0, ignored
LowMemReserve=integer
default=51200, ignored
BufferLength=integer
input buffer length, default=2048
WindowManagerWidthAllowance=integer
number of pixels to allow for Window Manager
decoration, default=20
WindowManagerHeightAllowance=integer
number of pixels to allow for Window Manager
decoration, default=60
PaletteChangeTimeout=integer
how long to leave between palette changes,
default=1 second
RedrawAfterPaletteChange=boolean
redraw screen after each palette change, default=1
ForcePlaneMask=boolean
force planemask to all 1's for SCO UW2.1 with 16
colors, default=False
ClientName=string
allows client name to be overidden, normally this is
obtained from the system, default=none=no overide
ClientSN_2.0=string
client serial number, no default, fixed
[Thinwire3.0]
Thinwire Virtual Driver configuration
DesiredColor=[1|2]
default number of colors to use, 1 = 16 colors, 2 =
256 colors, default=2
DesiredVRES=integer
default window size vertical, default=480
DesiredHRES=integer
default window size horizontal, default=640
ApproximateColors=boolean
default color approximation setting, default=True
PersistentCacheSize=integer
persistent cache size in K, default=0, ignored
PersistentCachePercent=integer
persistent cache size as percentage of file system
size, default=100
February 18, 2000
48
IBM Internal Use Only
Item
Description
PersistentCacheMinBitmap=integer
minimum size of bitmap for caching, default=8192
PersistentCachePath=string
location of persistent cache, default=/tmp/.ICACache
UseServerRedraw=boolean
allow server to control screen redraws, default=Yes
AllowBackingStore=boolean
allow X server backing store to be used, default=Yes
UseDefaultVisual=boolean
allow default X visual to be used, default=No; client
selects visual
UseUserVisualIID=boolean
allow user-specified X visual, default=No
UserVisualID=integer
user-specified visual ID, default=0
LargeCacheSizeInK=integer
large cache size in K, default=2048
ScreenPercent=integer
percentage of screen to use, fixed value=0, ignored
IgnoreXErrors=string
comma separated list of entries such as m.n/p
meaning ignore error code p on X protocol request
with major type m and minor type n, no default
[Xdpy - X server vendor identification string]
X server vendor multimod requirements. These
parameters identify vendors’ X server versions that
produce both key up and key down events in
response to each key up or key down for the Caps,
Scroll and/or Num lock keys
All=string
n-=string
one or more of Caps, Scroll or Num; multimod refers
to all versions of the server
one or more of Caps, Scroll or Num; multimod refers
to version n and upwards ofvserver
-n=string
one or more of Caps, Scroll or Num; multimod refers
to version up to n inclusive of server
m-n=string
one or more of Caps, Scroll or Num; multimod refers
to server versions between m and n inclusive
Module.Ini
This file contains a comprehensive listing of parameters used to select and configure the
communications stack modules. The section headings identify the target module by name. The
stack element types are:
Ÿ
Transport Drivers (TD) - manage the communications connection
Ÿ
Protocol Drivers (PD) - manage intermediate data stream filters
February 18, 2000
49
IBM Internal Use Only
Ÿ
WinStation Drivers (WD) - manage the presentation data stream
Ÿ
Virtual Drivers (VD) - manage ICA protocol extensions
These elements are all loaded depending on the user configuration and the required stack
relationships. The transport driver is loaded first, then protocol drivers, the WinStation driver,
and virtual drivers. Each of the supported types has a section that describes the module name
and default parameters. Most parameters in this file are defaults. They can be overridden by
equivalent entries in appsrv.ini.
Item
[WFClient]
Version=2
[ICA 3.0]
Definition
This section is used by the engine. It contains default
session-oriented parameters.
fixed value; overrides value in appsrv.ini; ignored
client module configuration
VirtualDriver=string
list VDs to load, fixed value='Thinwire3.0, Clipboard,
ClientDrive, ClientPrinter, ClientAudio,
ClientManagement, ClientComm'
ThinWire3.0=boolean
turn on Thinwire, default=Off, fixed value=On
Clipboard=boolean
turn on Clipboard, default=Off, fixed value=On
[TCP/IP]
transport driver configuration
TcpNoDelay=boolean
turn off Nagle algorithm, default=Yes
BrowserRetry=integer
number of attempts to locate master browser,
default=3
BrowserTimeout=integer
number of milliseconds to wait before retry,
default=1000
ICAPortNumber=integer
server port to use for ICA connection, default=1494
(from the Internet Assigned Numbers Authority
(IANA))
ProtocolSupport=string
list Protocol drivers to load, fixed value='RFrame,
Encrypt'
RFrame=boolean
turn on reliable framing, default=Off, fixed value=On
Encrypt=boolean
turn on basic encryption, default=Off, fixed value=On
OutBufLength=integer
size of output buffer, default=512, fixed value=530
OutBufCountHost=integer
number of server output buffers to allocate,
default=8
OutBufCountClient=integer
number of client output buffers to allocate, default=6
InterfaceAddress=string
IP address (dotted quad) for binding, no default;
“INADDR_ANY” recommended
InterfacePort=integer
TCP port number for binding; no default, ephemeral
port (in the range 1025 - 65535) recommended
February 18, 2000
50
IBM Internal Use Only
Item
Definition
[RFrame]
reliable framing Protocol Driver configuration, no
parameters
[Encrypt]
encryption Protocol Driver configuration, no
parameters
[Reliable]
reliable transport, Protocol Driver, ignored
[Compress]
compression Protocol Driver configuration, ignored
[OemFilter]
OEM filter Protocol Driver configuration, ignored
[OemConnect]
OEM connection Protocol Driver configuration,
ignored
[Framing]
Framing Protocol Driver configuration, ignored
[Modem]
Async Protocol Driver configuration, ignored
[Thinwire3.0]
Thinwire Virtual Driver configuration, overridden by
parameters in wfclient.ini
[Clipboard]
Clipboard Virtual Driver configuration, no parameters
[ClientDrive]
Client Drive Mapping Virtual Driver configuration
MaxWindowSize=integer
window size for flow management, fixed value=6276
MaxRequestSize=integer
for flow management, fixed value=1046
CacheTimeout=integer
cache timeout, default=600 seconds
CacheTimeoutHigh=integer
cache timeout for times greater than 18 hours,
default=0
CacheTransferSize=integer
amount of data to transfer per operation, default=0
which means use ICA Buffer size
CacheDisable=boolean
disable cache, default=False, ignored
CacheWriteAllocateDisable=boolean
disable cache for write operations, default=False
[ClientPrinter]
Client Printer Mapping Virtual Driver configuration
WindowSize=integer
write window size for flow management, fixed
value=1024
MaxWindowSize=integer
maximum windows size from management, fixed
value=2048
UnicodeEnabled=boolean
enable unicode printer names, defaults=True
ClientPrinterList=string
allow specified named printers to be used, no
default, i.e. enumerate client printers
UnixPrintCommand=string command to use for
February 18, 2000
51
IBM Internal Use Only
Item
Definition
printing, default ='lpr -P' for BSD systems, 'lp -d' for
SYSV systems
WindowsPrinter=string
default Windows queue name to use, no default,
ignored
UnixPrintCommand
default=/usr/local/nc/bin/nclpr -P”%s”
[ClientAudio]
Client Audio Mapping Virtual Driver configuration
NumCommandBuffers=integer
number of client buffers to use for Audio commands,
default=64
NumDataBuffers=integer
number of client Audio data buffers, default=32
MaxDataBufferSize=integer
max size of each data buffer, default=2048
CommandAckThresh=integer
number of free client command buffers causing a
'resource free' message to be sent to the server ,
default=10
DataAckThresh=integer
number of free client data buffers causing a
'resource free' message to be sent to the server,
default=10
PlayDelayThresh=integer
delay between being asked to open audio device and
actually opening it in order to build up a backlog of
sound, default=250 msec
AckDelayThresh=integer
max time between sending 'resource free' message if
any resources free, default=350msec
AudioDevice=string
audio device name, default=/dev/audio
[ClientManagement]
Client Management (Client Auto Update) Virtual
Driver configuration
ForceUpdate=boolean
force client update, default=True, ignored
MaxDataBufferSize=integer
max amount of data that server should send in one
packet , default=2048 bytes
[ClientComm]
Client Com Port mapping Virtual Driver configuration
WindowSize=integer
window for flow management, default=1024
CommPollSize=string
use asynchronous polling, default=On
CommPollWaitMin=integer
time to delay after receiving data, default=0 msec
CommPollWaitMax=integer
slowest com port polling rate, default=500 msec
CommPollWaitInc=integer
see CommPortWaitInc, default=1 msec
CommPollWaitIncTime=integer
time polling will poll before slowing by
CommPollWaitInc msec, default=100 msec
[KeyboardLayout]
Keyboardname=locale
February 18, 2000
list of possible keyboards supported
keyboard name; for example, 'British', 'German', 'US'
52
IBM Internal Use Only
Item
Definition
and NT locale identifier, fixed value
[Hotkey Shift States]
fixed values for hotkey masking
(none)=0
fixed value
Alt=2560
fixed value
Ctrl=1280
fixed value
Shift=3
fixed value
Alt+Ctrl=3840
fixed value
Alt+Shift=2563
fixed value
Ctrl+Shift=1283
fixed value
Alt+Ctrl+Shift=3843
fixed value
[Hotkey Keys]
fixed scancode values for hotkey keys
(none)=0
fixed value
F1...F12=112...123
scancode values for function keys
Minus=105
scancode value for numpad minus key
Plus=106
scancode value for numpad plus key
Tab=16
scancode value for Tab key
February 18, 2000
53
IBM Internal Use Only
Advanced Topics
Precedence order for ICA connection Records
The current schema for precedence of ICA connection records in the ICA Remote Application
Manager is: NSM (NC Registry) first, then user's appsrv.ini file if it exists or if it does not exist,
the system appsrv.ini file. This precedence information is important for understanding what
connection records will appear in the Remote Application Manager (wfcmgr). Since the ICA code
was designed to use the connection description as the unique field, two records cannot be added
with the same description.
A problem will occur if/when NSM has a connection record with a description that is the same as
one found in either of the appsrv.ini files. Currently the NSM connection record will take
precedence and the duplicate will not be shown to the user.
Another problem could occur since NSM doesn't guarantee unique names for each connection
record. So it is possible for 2 records to exist in NSM with the same description. In this case only
the first record encountered will be shown to the user.
Copying and pasting text and graphics
The ICA Client automatically transfers simple text, RTF text and DIB/BMP graphics between the
X Windows and Windows clipboards, so that you can copy or cut and paste freely between X
Windows and Windows applications or between Windows applications on the same or different
Citrix servers.
RTF
Rich Text Format. Both sending and receiving applications must be using the
same code page.
DIB
Windows Device Independent Bitmap
BMP
Windows Bitmap
All applications involved with copy/paste operations must be capable of handling the data
formats involved. The ICA Client does no data conversions.
To copy text or graphics from Windows to X Windows
1. Select the text or graphic you want to copy from the Windows application.
2. Choose Copy from the Windows application's Edit menu. The text or graphic is copied to
the Windows clipboard.
3. Switch to the X application you want to use.
4. Choose the appropriate command from the X application to paste in the text or graphic you
copied.
To copy text or graphics from X Windows to Windows
1. Select the text or graphics you want to copy.
February 18, 2000
54
IBM Internal Use Only
2. Choose the appropriate command from the X application to copy the text or graphics. The
text or graphic is copied to the Windows clipboard.
3. Switch to the ICA Client.
4. Choose Paste or Paste Special... from the Edit menu of the Windows application to paste
the text or graphic.
Connecting to Local Printers
With the ICA Client you can print to any spooled printer available from your IBM Network
Station. Such printers might be connected to the parallel port or the serial port. Printers can be
connected automatically or manually.
Automatic Connection
Using Network Station manager (NSM), local printers need only be set up once to enable
automatic connection to ICA sessions.
In order to automatically connect printers during the ICA logon two things need to happen. First,
the ICA client needs to be able to provide the ICA server with the NT printer driver name for
each of the Network Station printers. And second, the NT printer driver must be installed on the
ICA server. The correct printer driver name can be found by using the Printer Wizard on the ICA
server ( see Note 1 below). The Network Station ICA client takes the NT printer driver name
from the Network Station Manager (NSM) description field of the printer. The printer driver name
is entered into the description field via the NSM printer configuration screens.
Once the printer driver name has been added via NSM and the Network Station in question has
been rebooted, the user can log in to the ICA server and bring up the Control Panel-> Printers
window and see the printers that were auto created. If they do not see the printers, they should
bring up the Programs->MetaFrame Tools->Client Printer Configuration screen and make
sure that the data they entered was correct and available to the ICA server.
Steps for determining the correct NT printer driver name:
1. On the ICA server computer, click Start, click Settings, then click Printers.
2. Double-click the Add Printer icon, select My Computer, then click Next.
3. In the Available Ports list box, select LPT1, then click Next.
4. In the left pane, select the Manufacturer of the printer you have installed on your Network
Station. In the right panel, scroll to the model of the Printer you want the Terminal Server to
load as the printer driver.
This is the server printer driver name that you want to use. Write this name down. This exact
name will be entered via NSM into the description field of the printer you are configuring.
Manual Connection
Manual connections to local printers must be done each time an ICA session is established.
To print to a local printer in WinFrame
February 18, 2000
55
IBM Internal Use Only
1. In the Main program group double-click the Print Manager icon.
In the Printer Manager window you should see an icon, or open dialog box, for a network
printer with a name similar to workstation#printer where workstation is the IBM Network
Station name and printer is the IBM Network Station name for the printer.
2. If no client printer is available, select Connect to Printer? from the Printer menu.
3. Double-click the Client Network icon in the Shared Printer list.
4. Double-click the Client icon.
5. Select the client printer icon, which will have a name similar to workstation#printer, and
click OK.
6. If you want this printer to be your default printer select it in the Default menu at the top of
the Printers window.
To print to a local printer in MetaFrame
1. Click Start on the taskbar, point to Settings, then click Printers on the submenu.
In the Printers window you should see an icon for a network printer with a name similar to
workstation#printer, where workstation is the IBM Network Station name and printer is
the IBM Network Station name for the printer.
2. If no client printer is available, double-click the Add Printer icon in the Printers window to
run the Add Printer Wizard.
3. Click the Network printer server then click Next.
4. Double-click Client Network, and double-click Client.
5. Select the printer from the list displayed, and click OK.
Spooled printers available on the IBM Network Station have a name similar to
workstation#printer.
6. If you want this printer to be your default printer, click Yes then click Next.
7. Click Finish to complete the process.
Note: The ICA Client printer support is not bi-directional. This means that the printer cannot
answer or originate messages.
Connecting to Local Serial Devices
With the ICA Client you can use serial devices attached to any of the COM ports on your IBM
Network Station.
COM port mapping does not happen automatically. To map a client COM port
1. Start the ICA Client and logon to the Citrix server.
2. Start a DOS command prompt: ...
February 18, 2000
56
IBM Internal Use Only
At the prompt type net use comX: \\client\comZ: where X is the number of the COM port
on the server (ports 1 through 9 are available for mapping) and Z is the number of the client
COM port you want to map to. Press ENTER.
3. To confirm the operation, type net use at the prompt. The list that appears contains mapped
drives, LPT ports and mapped COM ports.
To use this COM port in a session on a Citrix server, install your device to the mapped name.
For example, if you map COM1 on the client to COM5 on the server, install your COM port
device on COM5 during the session on the server. Use this mapped COM port as you would a
COM port on the client computer.
The IBM Network Station ICA Client can map any of the four virtual serial ports (com1 through
com4) to any of the defined tty ports (/dev/tty00 through /dev/ttynn) on the Series 300, Series
1000 and Series 2800 Network Stations.
On the Series 2200 Network Station there are USB ports, not serial ports. However, USB to
serial port boxes can be used and any of the four virtual serial ports (com1 through com4) can be
mapped to any of the defined USB/tty ports (/dev/utty00 through /dev/uttynn).
Series 300 and Series 1000
/dev/tty00
/dev/tty01
/dev/tty02
/dev/tty03
/dev/tty04
base serial port on the planar board
A plug on the multiport serial card
B plug on the multiport serial card
C plug on the multiport serial card
D plug on the multiport serial card
Series 2200
/dev/utty00
/dev/utty01
A plug on USB to serial port box
B plug on USB to serial port box
...
Series 2800
/dev/tty00
/dev/tty01
/dev/tty02
/dev/tty03
/dev/tty04
/dev/tty05
serial port 1 on the planar board
serial port 2 on the planar board
A plug on the multiport serial card
B plug on the multiport serial card
C plug on the multiport serial card
D plug on the multiport serial card
Note: COM port mapping is not TAPI-compatable. TAPI devices cannot be mapped to client
COM ports.
Low Bandwidth Considerations
The ICA Client has several performance tuning options that can be set, most of which address
network traffic reduction. Network topologies vary greatly as does the instantaneous load they
bear. You may need to experiment with the following tuning options to see how they best work in
your network.
February 18, 2000
57
IBM Internal Use Only
Number of colors
The ICA protocol supports 16 and 256 colors. Selecting 16 colors produces less network traffic
than 256 colors. Operating the ICA server in the same color mode (16 or 256 colors) saves a
color conversion on the server side. On the IBM Network Station, 16 color image data takes
more processing power than 256 colors.
The default is 256 colors.
Tcp buffering
If your network topology involves any low bandwidth segments and you are noticing slow
performance due to the large number of ica packets being sent over the wire, you can configure
the ica connection to use a low bandwidth optimization algorithm for small packet transmissions.
This will decrease the overall number of packets sent on the wire, which in some low bandwidth
situations may improve the overall performance. This should not be used in high bandwidth
environments since it can actually slow down the user interface performance.
To enable the low bandwidth optimization algorithm, add the following option to the extra options
section of your connection in NSM or add it to your command line parameters if you are creating
your own ICA Client commands:
-TcpNoDelay No
The default is -TcpNoDelay Yes.
Audio quality levels
There are three selectable audio quality levels - low, medium and high. These levels also
represent the amount of network traffic that audio requires, i.e., low audio quality produces less
network traffic than high audio quality.
The default is medium.
Persistent caching
Persistent caching only helps in very low bandwidth situations ,e.g., connecting through a
modem. In high bandwidth networks, persistent caching may actually decrease
performance.
The default is no persistent caching.
Compression
ICA protocol compression results in reduced network traffic at the expense of processing power
required to run the compression algorithms.
The default is compression on.
February 18, 2000
58
IBM Internal Use Only
Technical Detail
Environment variables
Available before user authentication:
MRIPATH
The set of language specific directory paths that applications and library
packages use to look for language catalogs. ICA parses this variable
into a set of directories to search for ICA application defaults and help
text.
ICAROOT
specifies the ICA installation directory path. If not specified then
/usr/lib/ICAClient is assumed.
WFCMGR_OPTS
a string of ICA Remote Application Manager command line parameters
that are inserted into the ICA command line immediately after the
program name
NCS_OPTS
a string of ICA Client command line parameters that are inserted into the
ICA command line immediately after the program name.
Note: The ICA Remote Application Manager (wfcmgr) invokes the ICA
Client (wfica) with the -description command line parameter. This
imposes restrictions on the content of this environment variable. (See
Command Line Parameters section.)
Available after user authentication:
HOME
directory path for data for this user. This is used by ICA to construct a
directory path, $HOME/.ICAClient, in which to read or write appsrv.ini
and wfclient.ini files.
NSM variables
The ICA Remote Application Manager processes ICA connection records created by NSM and
stored in the Registry. Each NSM connection record is a string that contains the command line
parameters used to invoke the ICA client. When the ICA Remote Application Manager processes
the command line arguments, any token that matches the pattern ${XXX} is replaced by
getenv(“XXX”).
The exception to this is ${PASSWORD}. In this case, the ICA Client requests the current user’s
password from the actlogin daemon.
Kiosk Mode
Originally, Kiosk Mode was defined to be:
Ÿ
A single application running full screen without window borders. If another application is
run concurrently, that application too will run full screen without window borders. (Not all
applications behave this way.)
February 18, 2000
59
IBM Internal Use Only
Ÿ
The environment variable NSM_KIOSK_MODE is set.
Ÿ
There is a window manager.
Ÿ
There is no desktop. The application is the desktop.
Ÿ
No login screen is presented when the Network Station boots up. Authentication, if
required, is the responsibility of the host program to which the application connects.
Ÿ
The $HOME environment variable is set to /tmp or some other writable file system.
However, customer feedback pointed out that this methodology was not flexible enough. There
was a desire to manage Kiosk Mode on an application by application basis. To provide this
flexibility, the NSM_KIOSK_MODE environment variable is no longer processed by ICA
applications (wfcmgr, wfica).
In order to run in KIOSK mode two new command line parameters need to be added to your ICA
client invocation. These parameters are -UseFullScreen and -NoWindowManager. Adding
these parameters to the command line enable the both ICA Remote Application Manager and
the ICA Client to launch in full screen mode without borders on the client window. In addition,
you will need to use the -noupdate parameter when invoking the ICA Remote Application
Manager.
Using the above parameters as described will provide the same look and feel as the no longer
used NSM_KIOSK_MODE environment variable. In addition, the above parameters can be used
in various combinations to give a custom look and feel to individual ICA application invocations.
Note: If you would like to have all ICA Client sessions start up in full screen without window
borders, you can edit the system wide ICA configuration file called:
<top>/<nws>/usr/lib/ICAClient/config/wfclient.ini
where
<top> depends on the host system where you install NSM
Host
<top>
NT
/NetworkStationV2/prodbase
AIX
/usr/NetworkStationV2/prodbase
AS400
/QIBM/ProdData/NetworkStationV
2
<machine> depends on the type of IBM Network Station
Network Station
<nws>
Series 2800
x86
Series 2200
x86
Series 1000
ppc
Bring this file up in an editor and add the following lines to the end of the section starting with
[WFClient] (see section on INI files).
UseFullScreen=TRUE
NoWindowManager=TRUE
(See the section on .ini files.)
February 18, 2000
60
IBM Internal Use Only
If you choose to run in Kiosk Mode you may need to add predefined ICA connections to your
kiosk configuration files. This can be done in either of two ways:
Ÿ
Ÿ
generate XML data for the ICA connection(s) and add to kiosk configuration files
generate INI data for the ICA connection(s) and add to ICA configuration files
Adding ICA connections using XML data
Generating the ICA connection records can be done using NSM or an editor. Bring up NSM on
the server, login as the NSM administrative user. In the Set Preference Level dialog box, select
User and enter the username in the User filed. Then select Applications and then ICA Remote
Application Manager. Use the NSM screens to add a connection. Add one or more ICA
connections and select Save.
Now edit the <top>/userbase/profiles/users/<username>.nsm file where <username>
is the name of the user whose preferences were modified above. This file should look similar to
the file below.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE NCREGISTRY SYSTEM "registry.dtd" >
<NCREGISTRY VERSION="1.0">
<OBJECT NAME="/ica/connections">
<CATEGORY NAME="ICA">
<PROPERTY NAME="ica-connect-records" TYPE="LIST" ACTION="APPEND">
<ELEMENT>
<FIELD NAME="id">test-connection-WINC-user-1</FIELD>
<FIELD NAME="command">nsm_wrapper /usr/lib/ICAClient/wfica -s ICA_SERVER
-UseFullScreen</FIELD>
<FIELD NAME="name">test-connection</FIELD>
</ELEMENT>
</PROPERTY>
</CATEGORY>
</OBJECT>
</NCREGISTRY>
Now that the data has been generated it needs to be copied out of this file and into your kiosk file
on the server. The file that this data is placed into depends on whether or not you would like the
ICA connection records to be available for ALL machines booting from this server, or just a
specific machine. If you would like ALL machines to have this connection record available then
copy to the <top>/userbase/profiles/allncs.nsm file.
If you just want one Network Station be have the ICA connection records then copy to the
<top>/userbase/profiles/ncs/<ip_addr>.nsm file where <ip_addr> is the network
address of the specific Network Station. This file should already exist since this station is
configured for kiosk mode.
Copy the section starting with <OBJECT and ending with </OBJECT to one of the above files just
below the last instance of </OBJECT in the file. Save the file. Voila! We can now reboot the
Network Station in question and should have the ICA connection records show up in the ICA
Remote Application Manager.
Adding ICA connections using INI data
You can use the ICA Remote Application Manager to generate a set of ICA connection records.
By default, the ICA connection records will be put into the $HOME/.ICAClient/appsrv.ini
file where $HOME is the home directory of the Network Station user. Once the set of ICA
connection records have been built, go the boot server host machine and copy the
February 18, 2000
61
IBM Internal Use Only
<top>/userbase/$HOME/.ICAClient/appsrv.ini file to some location that all users can
access, e.g., <top>/prodbase/<nws>/.ICAClient/appsrv.ini.
Alternatively, you can use an editor to create the common appsrv.ini file. Start by copying the
<top>/userbase/usr/lib/ICAClient/config/appsrv.ini file to some location that all
users can access, e.g., <top>/prodbase/<nws>/.ICAClient/appsrv.ini. To add a new
ICA connection, use your editor to copy the [(IBM) Common Default Information] section and
rename it, e.g., [My First Attempt]. The string between the brackets is known as the ICA
connection description. Add the description to the list of description under the
[ApplicationServers] section. Format is the description followed by an equal sign, e.g., My First
Attempt=.
The final step is to bring up NSM on the server, login as the NSM administrative user and select
System Level Preferences. Select Applications and then ICA Remote Application Manager.
Add or select an existing ICA Connection Entry. In the ICA Connections Entry Settings, add
the -file <file_name> parameter to the Additional Parameters filed where <file_name> is the
fully qualified file name of the connection file created above. To continue the example above,
this would be /.ICAClient/appsrv.ini.
Client Printer Auto Creation
The ICA client has had the ability to export the list of printers on the Network Station to the ICA
server during an ICA session since the release of V2R1. Previously this required the user to use
the Printer Wizard to add the printer for use in the ICA session. With this new version of the ICA
client comes the ability to automatically create client printers during the ICA session logon and
automatically delete client printers during logoff.
The following example walks step by step through the NSM printer configuration and then
reviews the outcome on the ICA server. Several printers will be defined using NSM, connected
to an ICA server and then confirmed that printers correctly configured have been automatically
created, while the ones that had not been completely configured or were incorrectly configured
were not automatically created.
For this example we have pre-installed two NT printer drivers on our ICA server, the “HP
LaserJet 5/5M Postscript” driver and the “HP Color LaserJet 5/5M PS” driver. We have
purposely not installed the “IBM 4019 Laser Printer” driver on the server. The default NSM
printer configuration is to have 3 printers configured, PARALLEL1, SERIAL1, and SERIAL2. All
of these printers have a description field of “Generic Postscript”, which does not correspond to a
valid NT printer driver name.
1. Bring up NSM and log in as an NSM admin.
2. Make sure that the System button is checked, click on Hardware on the left panel and then
select Printers.
3. Confirm that the Local Parallel Printer has “printer attached” equal to YES and the
description is "Generic Postscript".
4. Confirm that Serial 1 and Serial 2 queues exist and both have "Generic Postscript" as their
description.
5. Fill in the number 3 for the Port Number on the empty entry in the Local Serial Printer list.
And enter "HP Color LaserJet 5/5M PS" for the Description.
February 18, 2000
62
IBM Internal Use Only
6. Click on Add another Serial Printer. Fill in the number 4 for the Port Number on the new
empty entry and then enter "IBM 4019 Laser Printer" for the Description
7. Click on Add another Serial Printer. Fill in the number 5 for the Port Number on the new
empty entry and then leave the Description field blank.
8. Click on Add another Serial Printer. Move down to the Remote Printer Server section
and fill in the Server Name with "ncdprt", the Queue Name with "monops" and the
Description with "HP LaserJet 5/5M Postscript".
9. Click on Add another Remote Printer. Fill in the Server Name with "ncdprt", the Queue
Name with "colorps" and leave the Description field blank.
10. Click on Add another Remote Printer and then click on Save at the bottom of the screen.
Now that NSM has been configured, reboot the Network Station and bring up the ICA Remote
Application Manager ( by way of the Host Access icon ). Create a connection to test the ICA
server and launch the connection. Once logged in to the ICA server, go to
Start->Programs->MetaFrame Tools->Client Printer Configuration. When the window
launches, the following information should appear:
Printer Name
Type
Port
Status
<clientname>#ncdprt:colorps
Unavailable
ncdprt:colorps
Disconnected
<clientname>#ncdprt:monops
HP LaserJet 5/5M PostScript
ncdprt:monops
Connected
<clientname>#SERIAL5
Unavailable
SERIAL5
Disconnected
<clientname>#SERIAL4
IBM 4019 Laser Printer
SERIAL4
Disconnected
<clientname>#SERIAL3
HP Color LaserJet 5/5M PS
SERIAL3
Connected
<clientname>#SERIAL2
Generic Postscript
SERIAL2
Disconnected
<clientname>#SERIAL1
Generic Postscript
SERIAL1
Disconnected
<clientname>#PARALLEL1
Generic Postscript
PARALLEL1
Disconnected
Where <clientname> is by default the IP host name of the Network Station client that we are
testing with. So why are some listed in Connected state, while others are Disconnected? Let’s
start at the top. The colorps queue we created above did not contain a description field at all, so
we could not supply this value to the ICA server and therefore it could not create the printer
automatically. This does not mean that the printer cannot be created, it simply means that we will
have to use the Printer Wizard to manually create the printer and select the correct NT printer
driver for this particular printer. Next, monops, we supplied a valid NT printer driver name that
was pre-installed on the server, so it was correctly configured and automatically created at login
time. SERIAL5, this one was not automatically created for the same reason as the first, we did
not supply a value in the description field. SERIAL4, we supplied a valid NT printer driver name,
so why didn’t it automatically create the printer? The driver is not installed on the server, which is
a prerequisite for automatic printer creation. SERIAL3, configured correctly and was
automatically created just like monops. SERIAL2, SERIAL1, and PARALLEL1, all of these failed
to automatically create printers. This is because they did not supply a valid NT printer driver
name.
You might have noticed that the list is in the reverse order of how it was created. This is because
the ICA client follows the NSM precedence rules when dealing with defined printers. Since
printers can be created at either the System level or the Workstation level, duplicate queues can
exist. The rule states that printers defined at the Workstation level have precedence over queues
defined at the system level. Since the Workstation level configuration is concatenated to the
February 18, 2000
63
IBM Internal Use Only
bottom of the System level configuration, they must be processed in reverse order to ensure that
the precedence rule is followed.
How does this affect the administrator? An issue can occur if the system level PARALLEL1
queue is left to it’s default, but the administrator would like to add a PARALLEL1 queue with a
different description field for one or more workstations. If a PARALLEL1 queue is added at the
Workstation level of NSM, without deleting the System level PARALLEL1 queue, there will be 2
PARALLEL1 queues defined for the Network Station. But, since ICA processes from the bottom
up, removing duplicates, only the Workstation level queue will be sent to the ICA server during
an ICA connection. This honors the NSM precedence rule listed above.
To summarize, this new release of the ICA client provides the ability to automatically create
client printers on the NT server at login time via an ICA connection. This requires that the printer
driver be pre-installed on the NT server and that the Network Station provides a VALID NT
printer driver name during login time. This new feature should dramatically increase the number
of static printer queues on the ICA servers and reduce the Network Station related NT printer
administration work dramatically.
Printer Mapping on the ICA Server
It is possible to map the client printer driver name to a server printer driver name via a text file
on the ICA server. The full instructions can be found in Microsoft support document Article ID:
Q221509. The following is a very succinct summary of this document.
A printer mapping template document is located on the ICA server in the
<system_root>\System32 folder. It is called WTSUPRN.TXT. The file is fairly self-explanatory.
Basically to add a new printer mapping go to the bottom of the document and use the format:
CLIENT_PRINTER_DRIVER_NAME = SERVER_PRINTER_DRIVER_NAME
For the Network Station an administrator might use the following mapping:
“Generic Postscript” = “HP LaserJet 5/5M PostScript”
Simply adding the above line to the bottom of the WTSUPRN.TXT file and saving it as
WTSUPRN.INF will cause new connections to map “Generic Postscript” which is the default
description for Network Station queues to the valid NT printer driver name “HP LaserJet 5/5M
PostScript”. As noted above, this printer driver still has to be pre-installed on the NT server for
the auto creation to work. Please see the Microsoft support document for more information.
ICA Language Translations
The ICA translatable information has been translated into the following languages:
Danish
French
Italian
Dutch
French (Belgian)
Norwegian
Dutch (Belgian)
French (Canadian 1988)
Portuguese
English (UK)
French (Canadian 1992)
Portuguese (Brazilian)
English (US)
French (Swiss)
Spanish
English (US ISO)
German
Spanish (Latin America)
Finnish
German (Swiss)
Swedish
The ICA translatable information has not been translated into the following languages:
February 18, 2000
64
IBM Internal Use Only
Bulgarian
Latvian
Serbian Latin
Arabic
Byelorussian
Lithuanian
Slovakian
Chinese (Simplified)
Catalan/Spanish
Polish 214
Slovenian
Chinese (Traditional)
Czech
Polish Programmer 457
Turkish
Hebrew
Greek
Romanian
Turkish
Japanese
Hungarian
Russian
Ukrainian
Japanese (US)
Icelandic
Russian/Cyrillic
Korean
Italian (Swiss)
Serbian/Cyrillic
Thai
Vietnamese
FLASH Boot Support
The ICA Remote Application Manager writes new or modified connection records to
$HOME/.ICAClient/appsrv.ini and writes modified options to
$HOME/.ICAClient/wfclient.ini. Through clever use of setting the HOME environment
variable, e.g. HOME=/tmp, a place can be found to write temporary records. What the ICA
Remote Application Manager does not do is create or update connection records and/or options
in memory only. It always writes updates to either of the previously mentioned two files.
Migration, Coexistence and Compatibility
This version of the IBM Network Station ICA Client is upward compatible with all previous
versions of the IBM Network Station ICA Client.
ICA directories and files
ICA for the IBM Network Station consists of two packages - the base package (includes 56-bit
encryption) and an optional 128-bit encryption package.
Base package
The base package contains the following directories and files:
$ICAROOT/
README
config/appsrv.ini
config/wfclient.ini
config/module.ini
config/Wfcmgr
config/Wfica
keyboard/keyboard.ini
keyboard/*.kbd
wfcmgr-export
wfica-export
wfcmgr
wfica
wfreport
-
$MRIPATH/
ICAClient/Wfcmgr
ICAClient/Wfica
- ICA Remote Application Mgr app-defaults
- ICA Client app-defaults
February 18, 2000
current information for ICA component
connection file template
configuration file template
protocol file
backup wfcmgr prompts, messages, defaults
backup wfica prompts, messages, defaults
keyboard selection menu configuration
keyboard definitions
ICA Remote Application Manager (56-bit)
ICA Client (56-bit)
symbolic link to wfcmgr-export
symbolic link to wfica-export
RAS information gathering tool
65
IBM Internal Use Only
ICAClient/help/*.gif
ICAClient/help/*.htm
- dialog image files
- html text files
128-bit encryption option package
The 128-bit package contains the following additional directories and files:
$ICAROOT/
wfcmgr-us
wfica-us
wfcmgr
wfica
-
ICA Remote Application Manager (128-bit)
ICA Client (128-bit)
symbolic link to wfcmgr-us
symbolic link to wfica-us
Note: If using a copy instead of a symbolic link, make sure wfcmgr and wfica are executable.
February 18, 2000
66
IBM Internal Use Only
Restrictions and Limitations
Window Managers Usurp Key Strokes
Window managers usurp key stroke combinations for their own use. This can cause functional
interference when running the ICA Client as shown in the following table.
Key Sequence
NWS Window Manager
NT Window Manager
Alt
Activate NT program menu bar
Alt + <alpha>
NT application menu bar shortcuts
Alt + F4
Close current X11 window
Close current NT window
Alt + F10
Pop up X11 root menu
Delete NT (doskey) macro
definitions
Alt + Space
Pop up X11 window menu
Display NT program’s System menu
Alt + Esc
Cycle through NT programs
Alt + Enter
Toggle NT window <-->full screen
Alt + Minus
Same as Alt + Space
Alt + Tab
Switch X11 windows forward
Switch NT windows forward
Alt + Shift + Tab
Switch X11 windows backwards
Switch NT windows backwards
Alt + Shift + Ctrl + F11
Toggle key sequence processing
Ctrl + X
Cut selection
Ctrl + C
Copy selection
Ctrl + V
Paste selection
Ctrl + Z
Undo
Ctrl + Esc
Display NT Start menu
Ctrl + Shift + Esc
Display NT Task Manager
Ctrl + Alt + V
Show X11 desktop version
Ctrl + Alt + L
Show logged-in X11 user
Ctrl + Alt + I
Shoe X11 IP address info
Ctrl + Alt + Backspace
Logout of X11 server
Ctrl + Alt + Delete
Hit twice to kill X11 active window
Display NT Security menu
Print Screen
Capture X11 screen image
Capture NT screen image
Alt + Print Screen
Capture X11 active window image
Capture NT active window image
There are three workarounds to this problem:
1. Redefine the conflicting NWS Window Manager key sequences in the NWS Registry. Users
familiar with the X11 window managers may have to relearn some key sequences.
2. Use the ICA Remote Application Manager’s HotKey dialog to define a set of alternative key
sequences that map into conflicting NT Window Manager key sequences. The ICA Client
would do the actual run-time mapping. Users familiar with the NT window manager would
have to relearn some key sequences. (Most Citrix ICA Clients supports this method, in part
because the Windows 95/98/NT window manager cannot be changed.)
February 18, 2000
67
IBM Internal Use Only
3. Use the Alt-Shift-Ctrl-F11 toggling key sequence which tells the NWS Window Manager to
stop/start processing key sequences. User must remember the toggle state as there is no
visual state indicator.
Caveat:Since this is a user interface issue, there probably are as many solutions as there are
people who study the problem.
Caveat:No matter what key sequence one assigns to the Window Manager, some where there is
a Windows program that expects to receive it.
Multiple Hosts
The ICA Client and the ICA Remote Application Manager support two types of host specification;
one for direct ICA application server connection and one for communicating with an ICA master
browser in load balancing situations.
The ICA Client and the ICA Remote Application Manager only support multiple hosts to specify a
list of ICA master browsers. Multiple hosts to support a list of ICA application servers is not
supported.
ICA protocol limitations
The ICA protocol sets restrictions that can not be circumvented by any ICA Client. This includes
not only the IBM Network Station ICA Client but those for Windows 95/98/NT as well. Some of
these restrictions include:
Number of Colors
The ICA protocol supports 16 and 256 color Windows applications. It
does not support Windows applications that use true color.
When the IBM Network Station is configured in true color mode, the
ICA Client maps the 16 or 256 color sent through the ICA protocol to
equivalent true colors on the Network Station.
Screen Resolution
The maximum screen size in the ICA protocol is 1280 pixel wide by
1024 pixels high. Increasing either dimension causes the ICA server
to disconnect. The ICA Client will automatically adjust the screen
resolution if it is out of bounds.
Virtual Comm Support
The ICA protocol only supports four virtual serial ports.
Virtual Parallel Support
The ICA protocol does not support virtual parallel ports.
Virtual Printer Support
The ICA protocol does not support bi-directional data
communication for the parallel port. Do not configure virtual printers
for bi-direction.
TAPI support
COM port mapping is not TAPI-compatable. TAPI devices cannot be mapped to client COM
ports.
February 18, 2000
68
IBM Internal Use Only
DOS full screen
When run as an ICA Client, the Windows 95/98/NT DOS Command Prompt window cannot be
made full screen by pressing the <Alt><Enter> key sequence nor by selecting full screen in the
DOS Command Prompt properties. (This only works for DOS and Windows 95/98/NT ICA
Clients because they literally go into DOS mode; something the Unix based ICA Clients are
unable to do.)
NT configuration problems
A good test of the Windows NT Terminal Server configuration is to (1) set the NT locale, (2)
specify and attach an applicable keyboard and (3) run both NotePad and WordPad (directly from
the NT). This usually identifies any problems that must be corrected before an ICA client will
work correctly.
NT server print spooler crash
Citrix "hot fix" ME100002.exe (available from http://www.citrix.com/support/ftp_meta.htm) is
required to fix a Citrix MetaFrame 1.7 server problem with print spooler crashes.
Lotus WordPro problems
The Lotus WordPro default font is "Times New Roman". For Turkish, select "Times New Roman
(Turkish)". For Hungarian or Czechoslovakian, select "Times New Roman (Central European)".
February 18, 2000
69
IBM Internal Use Only
NT keyboard layout mapping problems
The following keyboard mapping problems where found when the keyboard was directly
connected to the Windows NT Terminal Server console. These NT server keyboard mapping
problems are not ICA related.
Keyboard
NT Problem
Belgian Dutch
The key with base character is "superior 2", and shift character is "superior 3". With
"shift lock" on, it should print "superior 3", and it prints "superior 2" instead.
Belgian French
Character Aring prints "ring" followed by "A" as 2 separate characters instead of
being printed as 1 composed character.
The key with base character is "<", and shift character is ">", with "shift lock" on, it
should print ">", and it prints "<" instead.
The key with base character is "superior 2", and shift character is "superior 3". With
"shift lock" on, it should print "superior 3", and it prints "superior 2" instead.
Characters are showing when they are not defined on the physical keyboard.
- The alt_gr "4" prints "{" when there is no character defined on the keyboard.
- The alt_gr "5" prints "}" when there is no character defined on the keyboard.
Czech
The key to the left of "Y" has three characters on it. The base character is a "&" but
when selected it prints as a "\".
The shift "+" key is suppose to be a "*" but it is "|".
The alt_gr "+" key is suppose to be "<" but nothing prints.
The alt_gr "y" is supposed to be a ">" but nothing prints.
Danish
Characters show when they are not defined on the physical keyboard.
- The alt_gr "m" prints mu when there is no character defined on the keyboard.
French
The key with base character is "<", and shift character is ">", with "shift lock" on, it
should print ">", and it prints "<" instead.
German
Character Aring prints "ring" followed by "A" as 2 separate characters instead of
being printed as 1 composed character.
Hungarian
Characters are showing when they are not defined on the physical keyboard.
- The alt_gr "e" prints Adiaeries when there is no character defined on the
keyboard.
- The alt_gr "i" prints Iacute when there is no character defined on the keyboard.
Polish 214
The "[" and "]" on the alt_gr position are not printing.
Russian Cyrillic
All characters on the alt_gr position of the number keys on the first row are not
printing.
The key with character "|" prints as "/".
Swiss French
Characters are showing when they are not defined on the physical keyboard.
- The alt_gr "4" prints degree when there is no character defined on the keyboard.
- The alt_gr "5" prints section when there is no character defined on the keyboard.
Turkish F
Characters are showing when they are not defined on the physical keyboard.
- The alt_gr "-" prints "|" when there is no character defined on the keyboard.
- The alt_gr "u" prints "ae" when there is no character defined on the keyboard.
- The alt_gr "v" prints cents when there is no character defined on the keyboard.
Turkish Q
Characters are showing when they are not defined on the physical keyboard.
- The alt_gr '"' prints "<" when there is no character defined on the keyboard.
- The alt_gr "1" prints ">" when there is no character defined on the keyboard.
- The alt_gr "2" prints pound when there is no character defined on the keyboard.
- The alt_gr "5" prints "1/2" when there is no character defined on the keyboard.
- The alt_gr "-" prints "|" when there is no character defined on the keyboard.
- The alt_gr "s" prints beta when there is no character defined on the keyboard.
February 18, 2000
70
IBM Internal Use Only
Change History
V2R1 ( August 1999 )
The V2R1 IBM Network Station ICA Client is derived from the Citrix ICA Client for Linux SDK
3.0.15f. The Linux source code was ported to NetBSD and then to NCOS. The NetBSD port was sent
back to Citrix.
Fixes to the Citrix ICA Source Code, Version 3.0.15f
Ÿ
The ICA Client source code had to be ported from Linux to NetBSD. As a result several
major changes had to be made just to get it to run:
- Several makefiles had to be completely rewritten
- Linux specific files for directory access had to be rewritten
Ÿ
Both the ICA Remote Application Manager and the ICA Client can be built for either Motif or
Athena widgets. The ICA Remote Application Manager had Motif enabled but the ICA Client
had Athena enabled. There were several build problems that needed to be solved to build
the ICA client with the Motif.
Ÿ
The Xcapture program was built with Athena widgets and had to be converted to use Motif
widgets.
Ÿ
App-default files had to be moved because both AS400 and NT did not recognize case
sensitive file names.
Ÿ
Dialog border colors did not work with 16-bit true color.
Ÿ
Large object cut and paste did not work.
Ÿ
Discarded the provided install procedures. Reworked Makefiles to fit IBM’s install
procedures.
Ÿ
Audio had several timing glitches in it.
Ÿ
Serial support did not work.
Ÿ
Virtual print did not work if a dummy printer was not configured.
Ÿ
Names of ttys had to be changed.
Ÿ
Several problems with scroll bars (color, unable to get rid of them).
Ÿ
Dialogs were too big for 640x480 screens. Had to add scroll bars.
Ÿ
Hot key dialogs were collected into a single dialog. Additional hot key settings were added.
Ÿ
ICA focus policy did was broken. Could not always type into an ICA window that had
keyboard focus.
Ÿ
Audio and serial byte swapping problems.
Ÿ
Added code to check maximum screen size to avoid ICA protocol violation.
February 18, 2000
71
IBM Internal Use Only
Ÿ
Several keyboard fixes:
- no single international keyboard worked 100%. Had to rewrite the keyboard event handler.
- hot keys did not work smoothly (alt-tab in particular). Had to rewrite hot key event handler.
- some X11 events were directed to the wrong event handlers.
New Features
Ÿ
The ICA Client command line was extended to provide:
- compatibility with previous releases
- a list of ICA browsers to try
- additional Flash support
- ICA .ini configuration file statements
- debug and trace options to collect information from the field
Ÿ
Bitmap caching for diskless work stations
Ÿ
A host connect dialog if the ICA Client is started without any ICA server or browser
information.
Ÿ
Problem determination tools (additional trace options, data collection tools)
Ÿ
Support for 19 languages (HTML help text, app-defaults, keyboards).
Ÿ
Removed words or sections from HTML help and from run time dialogs that did not apply to
the IBM Network Station. For example, client program update, bitmap persistent cache size
and location, competitor keyboard definitions.
Ÿ
Full screen option to dialogs
Ÿ
Alt-Tab and Alt-Shift-Tab added to the HotKeys dialog
Ÿ
KIOSK support (single application, full screen, no window borders)
Ÿ
NCOS Registry support to access ICA connection records, keyboard layout and, in the case
of flash, ICA command line parameters
Ÿ
Actlogin support (including Actlogin's decoding algorithms) to get current user’s password
and pass to NT login screen
Ÿ
Syslog support
Ÿ
DES and RC5 encryption using 40, 56 and 128 bit keys
Ÿ
Keyboard support for any language
Ÿ
Unique ICA icon pixmaps
Ÿ
HTML help which can be launched from the Help->View Detail button. The HTML help is
displayed by a light weight HTML browser
February 18, 2000
72
IBM Internal Use Only
PTF-1 ( August 1999 )
Also know as PTF-GA, a continuation of V2R1 work.
Defects Fixed
10601 translated text truncated in “Bitmap Caching” field
10838 invalid NSM connection record causes wfcmgr to fail
11009 specifying a long host name causes wfica to segment fault
11117 wfreport uses /usr/bin/env but /usr/bin/env is not shipped with the product
11136 Shockwave causes wfica hang/core after about 5 minutes
11171 put untranslated X11 resources into Xtra file
11235 change “KIOSK” to “NSM_KIOSK_MODE” in wfica
11253 “Server Location” dialog fails to display the entire translated text
11267 wfcmgr needs to check wfica command line parameters in NSM connection records
11399 clicking on “Apply” twice locks up Properties list in wfcmgr
11430 allow -NSM_KIOSK_MODE on wfica command line
11462 (code maintenance)
11469 wfcmgr accepts null entry in Connection List
11479 bi-directional serial port does not work on a S1000
11485 specifying -en 40 in wfica on a S1000 causes ICA server to reboot
11528 change “KIOSK” to “NSM_KIOSK_MODE” in wfcmgr
11538 Xtra file not shipped in all builds
56880 screen size of 1281-2047 x 1025-2047 won’t launch ICA session
PTF-2 ( October 1999 )
Normal maintenance.
Defects Fixed
11543 wfica terminates if specified window size is 1600x1200
11648 default wfica keyboard buffering (TcpNoDelay=Off) causes performance problem
11653 an ‘=’ character in the Description field corrupts the appsrv.ini file
February 18, 2000
73
IBM Internal Use Only
11673 underscore is not allowed in host name
11719 .ica files not supported
11745 USB serial ports are not displayed in COMM Ports dialog
11781 selecting “Full Screen” does not work in wfcmgr
11782 full screen has scroll bars
11798 Registry connection failure in KIOSK mode
11879 wfica serial port performance fix
12074 x86 ICA client not packaged in driver 400
PTF-3 ( December 1999 )
Normal maintenance.
Defects Fixed
08001 syslog support on S1000
12146 Copy/Paste between 2 ICA sessions fails on S1000
12178 implement new KIOSK mode support
New Features
Ÿ
Concurrent ICA applications (wfcmgr, wfica) can individually be set to run in KIOSK
mode. Previously, all concurrently running ICA applications had to run in the same
mode.
PTF-4 ( February 2000 )
Normal maintenance.
Defects Fixed
12337 spaces are not allowed in “Published Application” field
PTF-5 ( April 2000 )
New source code base from Citrix, ICA Client for Linux SDK 3.0.80. This was a special (Linux)
source code tree that Citrix made for IBM. IBM made modifications to this tree and gave it back
to Citrix in December 1999. IBM then ported this source code tree to NCOS in January 2000.
February 18, 2000
74
IBM Internal Use Only
Defects Fixed
12682 multiple NumLock keys sent to Reflection VT100 emulator
12678 encryption for export raised from 40-bit to 56-bit
12737 change ICA version number format to IBM Network Station <version>.<release>.<ptf>
In addition, we picked up the fixes that Citrix had done since the 3.0.15f SDK.
New Features
Ÿ
Mark II Reducer Engine from the Citrix Windows ICA Client.
Ÿ
X11 Shared Memory Extension
Ÿ
SOCKS Proxy Server support
Ÿ
RTF Clipboard support
Ÿ
Window Border and Title Bar management
Ÿ
Printer auto-create
Ÿ
Support for “Flying Window” keys
Ÿ
Citrix Client Test Kit compliance
February 18, 2000
75
IBM Internal Use Only
Error messages
1:
An internal error occurred in the ICA Client.
An internal error has occurred. Contact your IBM representative and report the problem.
Provide a detailed description of the scenario that caused the problem.
2:
unused
3:
The option "..." is not valid.
Option "..." is not valid in this context.
4:
Missing argument for the option "...".
Option "..." requires an argument.
5:
The option "..." has an invalid argument: "...".
The configuration file has been edited directly, or is corrupt.
6:
Insufficient memory available.
The client does not have enough memory to continue program execution.
7:
Internal Error: E_CLIPPING
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
8:
Invalid ICA Protocol data received.
This probably indicates a network error.
9:
Internal Error: E_TOO_MANY_CALLS
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
10: Cannot read file: "..."
There was a problem reading a connection database file.
11: Error in configuration file: "..." Cannot find section "...".
The configuration file has been edited directly, or is corrupt.
12: Error in configuration file. Section "..." must contain an entry "...".
The configuration file has been edited directly, or is corrupt.
13: Internal Error: E_DESTROY_WITHOUT_INIT
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
February 18, 2000
IBM Internal Use Only
76
14: Cannot open visual: ...
The visual ( ID = ... ) cannot support the required number of colors.
15: The visual ( ID = “...” ) cannot support the required number of colors.
Cannot open visual.
16: Cannot allocate sufficient colors. Continuing in 16 color mode.
A suitable visual has been found but it can only support 16 colors.
17: Cannot find a suitable visual on this display.
Unable to allocate a private colormap on this display.
18: Unable to allocate a private colormap for this display.
Unable to get all the color cells needed for a private colormap on this display.
19: Internal Error: E_BUFFER_OVERFLOW
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
20: X Server cannot allocate sufficient resource. Request “...”
The X Server was unable to allocate the resources required by Request ... .
21: An error occurred in the graphics system.
There is a problem with the display. Try killing other applications such as Netscape
Navigator to release the colors on your display.
22: Cannot find keyboard mapping file "...".
The keyboard mapping file specified in the Preferences page of the Settings dialog box is
invalid or cannot be located.
23: A server must be entered.
A server name must be entered in the Network page of the Properties dialog box.
24: Window size must be between 300x300 and 1280x1024.
The Custom Width field in the Window page of the Properties and Settings dialog boxes
can take values between 300 and 1280.
The Custom Height field in the Window page of the Properties and Settings dialog boxes
can take values between 300 and 1024.
25: Data has been changed. Are you sure you want to quit?
You are quitting from the ICA Client without saving changes to the current connection entry.
26: Data has been changed. Are you sure you want to continue?
February 18, 2000
IBM Internal Use Only
77
You are continuing to execute the ICA Client without saving changes to the current
connection entry.
27: Invalid serial number.
Unable to obtain or generate a unique serial for this ICA client.
28: Cannot write file: "..."
There was a problem saving the connection database file; for example, no disk space.
29: Cannot create file: "..."
There was a problem creating a new connection database file
30: The X Request “...” caused error: "..."
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
31: Invalid error: Cannot start NCS with this connection.
The connection entry is invalid.
32: unused
33: Internal Error: E_HH_INVALID_DISPLAY
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
34: Internal Error: E_HH_UNSUPPORTED
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
35: Unable to start child program. Fork failed error: “...”.
The ICA Remote Application Manager was unable to start the ICA Client.
36: unused
37: Cannot read file: "..."
Unable to open an ICA configuration file.
39: Cannot find specified connection.
The configuration file is corrupt. Create a new configuration file.
38: Cannot find specified connection.
The configuration file is corrupt. Create a new configuration file.
40: Error in configuration file: "..." Missing section: "..."
February 18, 2000
IBM Internal Use Only
78
The configuration file is corrupt. Create a new configuration file.
41: Inconsistency in configuration file: "..." Missing section: "..."
The configuration file is corrupt. Create a new configuration file.
42: This description is already in use. The Description must be unique.
The Description field in the Network page of the Properties dialog box must be unique.
43: This description is already in use. The Description must be unique.
The Description field in the Network page of the Properties dialog box must be unique.
44: You must enter a serial number for Net Client to run.
Enter serial number.
45: Invalid Demonstration License. Check that the Authorization Code and Expiry Date are
correct.
Not used.
46: Cannot locate executable file "..." ( ... )
The executable file does not exist or the working directory/ path is incorrect.
47: Cannot execute file "...” ( ... )
The ICA Remote Application Manager was unable to start the ICA Client.
48: Cannot get address for server "..."
Unable to resolve the server name.
49: Cannot connect to server "..."
Unable to connect to server.
50: Your license does not allow you to connect to this server.
Not used.
51: A Master Browser cannot be located.
The query server cannot locate the Master Browser or the query server cannot be located.
52: No servers were found.
ICA servers were searched for but none were found. You may have to (re)set Server
Locations in the Settings dialog.
53: Invalid Citrix Server Browser command header received.
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
February 18, 2000
IBM Internal Use Only
79
54: Invalid Citrix Server Browser command received.
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
55: Invalid Citrix Server Browser command received on request.
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
56: Invalid Citrix Server Browser command sequence received.
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
57: Citrix Server Browser command contains an invalid parameter.
An internal error occurred in the ICA Client. Contact your IBM representative and report the
problem. Provide a detailed description of the scenario that caused the problem.
58: Not enough memory.
The client does not have enough memory to continue program execution.
59: I/O Error.
One of the following problems occurred when attempting to contact a Citrix Master Browser:
unable to bind socket, unable to get socket name, unable to set socket broadcast option,
unable to set non-blocking option, connection refused, unable to connect.
60: Read Timeout.
Overdue response fro a Citrix Master Browser after multiple attempts. In addition, this may
cause a request for the election of a new Citrix Master Browser.
61: IPX protocol is not available.
IPX protocol is not supported on the IBM Network Station.
62: TCP/IP protocol is not available.
Network error. Contact your system administrator.
63: NETBIOS protocol is not available.
NETBIOS protocol is not supported by the IBM Network Station.
64: The Citrix Server you have selected can not located.
The Citrix Server name cannot be resolved.
65: The Citrix Server cluster you have selected can not located.
Not used.
66: Unable to contact the Citrix Server Browser. Either your network is not functional, or
you need to configure your an address under Server Browsing.
February 18, 2000
IBM Internal Use Only
80
Either your network is not functional, or you need to configure your an address
under Server Browsing.
67: Error in configuration file: "..." Bad Key "...".
The configuration file has been edited directly, or is corrupt.
68: Error in configuration file: "..." Bad Value "...".
The configuration file has been edited directly, or is corrupt.
69: Error in configuration file: "..." Bad Vendor Range "...".
The configuration file has been edited directly, or is corrupt.
70: Unable to perform update: not running as super user.
You must be running as super user to perform a client update.
71: Unable to perform update: client is not on local file system.
The client cannot update an installation on a non-local (e.g. NFS mounted) file system.
72: Unable to perform update: not running $ICAROOT/wfica.
The client cannot update an installation other than its own.
73: Error loading dynamic module: "..." ...
Not used.
74: Must specify proxy server address.
Enter proxy server address in the Firewall Settings under the Properties Box.
75: The option "..." is required.
Missing option “...” when using another option.
76: Cannot connect to the Citrix server. Your Citrix server does not support the encryption
you required.
Your Citrix server does not support the encryption you required. Please change
the encryption.
February 18, 2000
IBM Internal Use Only
81
Citrix Copyright and acknowledgments
(c)
Copyright 1998-1999 Citrix Systems, Inc. All rights reserved.
The CitrixTM ICA Client for UNIX(R) software and portions of this documentation are copyrighted materials. Making unauthorized
copies is prohibited by law. No part of the Citrix ICA Client for UNIX software or documentation may be reproduced, transmitted,
transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without
the prior written permission of Citrix.
Citrix specifically retains title to all Citrix computer software. The software described in this guide is furnished under a license
agreement and may only be installed, used, or copied in accordance with the terms of that agreement.
Notice to US Government End Users
Restricted Rights Legend
For units of the Department of Defense:
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in paragraph
Technical Data and Computer Software Clause at DFARS252.227-7013 (May 1987) or equivalent.
(c)(1)(ii)
of the Rights in
For civilian agencies:
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraphs (a) through (d) of the
Commercial Computer Software - Restricted Rights Clause at 52.227-19 of the Federal Acquisition Regulations.
Citrix Systems, Inc., Customer Service, 6400 Northwest Sixth Way, Fort Lauderdale, Florida, 33309.
Microsoft, MS-DOS, and Windows are registered trademarks of Microsoft Corporation. IBM is a registered trademark, and IBM PC,
IBM PC/AT are trademarks of International Business Machines Corporation. SPARC is a registered trademark, and SPARC system
is a trademark of Sun Microsystems. Silicon Graphics is a registered trademark, and IRIS and Inde are trademarks of Silicon
Graphics, Inc. DEC is trademark of Digital Equipment Corporation. Intel is a registered trademark of Intel Corporation. UNIX is a
registered trademark licensed exclusively through X/Open Company, Limited. CSO is a registered trademark of The Santa Cruz
Operation, Inc. in the USA and other countries.
All other product names are trademarks or registered trademarks of their respective owners.
Various trademarks and registered trademarks are referred to in this document. Such references do not imply any endorsement of,
or other affiliations with, this guide. Where trademarks or registered trademarks are referred to, every effort has been made to
adhere to the holder's preferred style of spelling and capitalization.
The information in this guide is believed to be correct as of the date of publication. However, it is subject to change without notice,
and does not represent a commitment on the part of Citrix.
CITRIX'S LICENSOR(S) MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE
SOFTWARE. CITRIX'S LICENSOR(S) DOES NOT WARRANT, GUARANTEE OR MAKE ANY REPRESENTATIONS
REGARDING THE USE OR THE RESULTS OF THE USE OF THE SOFTWARE IN TERMS OF ITS CORRECTNESS,
ACCURACY, RELIABILITY, CURRENTS OR OTHERWISE. THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE
OF THE SOFTWARE IS ASSUMED BY YOU. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME
STATES. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU.
IN NO EVENT WILL CITRIX'S LICENSOR(S), AND THEIR DIRECTORS, OFFICERS, EMPLOYEES OR AGENTS
(COLLECTIVELY CITRIX'S LICENSOR) BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, INCIDENTAL OR INDIRECT
DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF
BUSINESS INFORMATION AND THE LIKE) ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE EVEN IF
CITRIX'S LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES DO
NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE
ABOVE LIMITATIONS MAY NOT APPLY TO YOU.
February 18, 2000
IBM Internal Use Only
82
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement