home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 3 Comm
/
03-Comm.zip
/
nos2eval.zip
/
manual.txt
next >
Wrap
Text File
|
1996-01-22
|
123KB
|
3,176 lines
------------------------------------------
NetOp for OS/2, Version 5.2 UK (Jan 1996)
------------------------------------------
User's Guide
Please send any comments to:
Danware Data A/S
Herlev Hovedgade 195
DK-2730 Herlev Denmark
Fax: int + 45 44 53 15 51
Internet: danware@danware.dk
WARRANTY
Danware Data A/S makes no guarantees with respect to the evaluation copy.
DISCLAIMER
Danware Data A/S denies any and all responsibility for damages
caused directly or indirectly as a result of any faults with the enclosed
programs and/or documentation.
LICENSE
Danware Data A/S retains the copyright to the user manual and the
programs on the enclosed diskettes. Your evaluation copy gives you the right
to copy and use the programs for a limited period only. Furthermore, you may
not use the programs in production, but only for test purposes to verify that
the software will work in your environment. At the end of the evaluation period,
you must either purchase the software, or destroy all copies you might have.
TRADEMARKS
NetOp and the red kite are registered trademarks of Danware Data
A/S. All other products mentioned in this manual are trademarks of their
respective manufacturers.
THE NETOP FAMILY
----------------
NetOp is a family of remote control products which support multiple operating
systems and various communication interfaces. The NetOp family provides the
most comprehensive cross platform support available today.
Below you will find a short description of NetOp products. For each product
please request fact sheet for a complete description of features and
requirements.
NetOp for OS/2 version 5
------------------------
The new generation of Danware remote control. Supports multiple protocols in
one package - IPX, NetBIOS, Serial (Modem), APPC, TCP/IP and ISDN (Capi).
Utilizes a new advanced Danware communication engine. Includes advanced
features such as integrated, bi-directional file transfer, non-polling
communication architecture, and support for high resolution graphics. NetOp
for OS/2 version 5 introduces the gateway concept, which allows you to dial
into a non-dedicated NetOp gateway PC on your network, and from the external
PC access all network PCs. NetOp for OS/2 version 5 is compatible with NetOp
for Windows version 5, providing support for remote control of Windows PCs
from an OS/2 PC, or remote control of OS/2 PCs from a Windows PC. NetOp for
OS/2 version 5 is also backwards compatible with RemPCs version 4.30,
protecting your previous investment in NetOp technology, and providing
support for remote control of DOS PCs.
NetOp for Windows version 5
---------------------------
The new generation of Danware remote control. Supports multiple protocols in
one package - IPX, NetBIOS and TCP/IP as well as dial-up via Serial (Modem)
and ISDN CAPI.
Utilizes a new advanced Danware communication engine. Includes advanced features
such as integrated, bi-directional file transfer, non-polling communication
architecture, and support for high resolution graphics. NetOp for Windows
version 5 uses advanced techniques to obtain optimal perfomance under Windows -
without replacing a single driver in your .INI files. NetOp for Windows version
5 is compatible with NetOp for OS/2 version 5, providing support for remote
control of Windows PCs from an OS/2 PC, or remote control of OS/2 PCs from a
Windows PC. NetOp for Windows hosts can be remotely controlled through a NetOp
for OS/2 gateway.
NetOp Dial
----------
Modem remote control of DOS from a DOS program. Supports up to VGA
+ many SVGA (DOS). Tiny TSR, fast screen transfer and file transfer feature.
NetOp Dial/2
------------
Modem remote control of OS/2 from a DOS program. Supports
graphics up to standard VGA. Remote control OS/2 from a less pow- erful
DOS/Windows based portable or home computer. File transfer feature.
NetOp ISDN
----------
ISDN Remote control of DOS/Windows from a DOS program. NetOp ISDN supports any
ISDN adapter with a CAPI 1.1 interface. Advanced file transfer feature.
NetOp DOS/Win
-------------
Network remote control of DOS and Windows from a DOS program.
Supports NetBIOS and Novell/IPX network protocols. Incredible low memory
requirement, only 3 to 6 KB of RAM. Peer to peer file transfer feature.
NetOp DOS/Win/OS2
-----------------
Network remote control of DOS, Windows and OS/2 from a DOS
program. Supports NetBIOS and Novell/IPX network protocols. Incredible low
memory requirement, only 3 to 6 KB of RAM. Supports standard VGA graphics for
OS/2. Very fast screen updates of OS/2. Peer to peer file transfer feature.
Other
-----
Should our current line of standard products not satisfy your needs,
please let us have a word from you. If what you miss is not already planned
for upcoming versions, the Danware expertise can be made available to do a
customized solution for you.
CONTENTS
--------
1.INTRODUCTION
1.1 SUMMARY
1.2 WELCOME TO NETOP FOR OS/2
1.3 ABOUT THIS MANUAL
1.4 EXAMPLES OF USE
1.5 THE NETOP SYSTEM
1.6 CROSS PLATFORM SUPPORT
1.7 USING THE NETOP PROGRAMS
1.7.1 The On-line Help System
2.INSTALLATION
2.1 SUMMARY
2.2 PREREQUISITE TASKS
2.2.1 Technical Requirements
2.2.2 Checking Your Package
2.3 INSTALLATION
2.4 MANUAL INSTALLATION
2.4.1 Installation
2.4.2 Win-OS2 Full Screen support
3. QUICK START
3.1 SUMMARY
3.2 THE HOST
3.3 THE GUEST
4. THE GUEST
4.1 SUMMARY
4.2 INTRODUCTION
4.2.1 Starting the Guest
4.2.2 The Guest Screen
4.3 CONFIGURATION
4.3.1 Communication Settings
4.3.2 Display Settings
4.3.3 Modem database
4.3.4 Modem dialog
4.3.5 Hotkey Assignments
4.3.6 Font Assignments
4.4 ESTABLISHING A SESSION
4.4.1 Host IDs
4.4.2 Calling a Host
4.4.3 Hang-up
4.5 HOST TABLES
4.5.1 Add Host
4.5.2 Build Host
4.5.3 Edit Host
4.5.4 Remove Host
4.5.5 Multiple Host Tables
4.5.6 Finding an Entry in the Host table
4.5.7 Miscellaneous
4.6 REMOTE CONTROL
4.6.1 Getting Started
4.6.2 Keyboard control
4.6.3 Mouse control
4.6.4 Lock Host Keyboard and Mouse
4.6.5 Boot Host
4.6.6 Chat with Host
4.6.7 Blank screen
4.6.8 Screen resolution
4.6.9 Zoom
4.6.10 Window manipulation
4.6.11 Hotkeys
4.6.12 File Transfer
4.6.13 Printer re-direction
4.7 HELP SERVICE
4.8 COMMAND LINE OPTIONS
5. THE HOST
5.1 SUMMARY
5.2 STARTING THE HOST
5.2.1 From the desktop
5.2.2 From an OS/2 prompt
5.2.3 Automatically at Startup
5.2.4 Initialization
5.3 SETTING UP THE HOST
5.4 SECURITY
5.4.1 Maintenance Password
5.4.2 Guest Rights
5.4.3 Public name
5.4.4 Password
5.4.5 Confirm access
5.4.6 Inactivity time-out
5.4.7 Call-back
5.5 ON-LINE CHOICES
5.5.1 Request Chat
5.5.2 Hangup
5.5.3 File Transfer
5.5.4 Call for Help
5.6 COMMAND LINE OPTIONS
5.7 PRINTER RE-DIRECTION
5.7.1 Description
5.7.2 Installing support for printer re-direction
6. THE GATEWAY
6.1 SUMMARY
6.2 INTRODUCTION
6.3 STARTING THE GATEWAY
6.3.1 From the desktop
6.3.2 From an OS/2 Prompt
6.3.3 Automatically at startup
6.3.4 Initialization
6.4 CONFIGURATION
6.4.1 Line Setup
6.4.2 Host Setup
6.4.3 Network setup
6.5 SECURITY
6.5.1 Line security
6.5.2 Host security
6.5.3 Maintenance password
6.6 NET NUMBERS
6.7 ON-LINE CHOICES
6.8 COMMAND LINE PARAMETERS
7. PROTOCOLS
7.1 SERIAL/MODEM
7.1.1 Description
7.1.2 Configuration
7.1.3 Protocol Specific Settings
7.1.4 How to Define New Modems
7.1.5 Host ID format
7.2 NETBIOS
7.2.1 Description
7.2.2 Configuration
7.2.3 Protocol Specific Settings
7.2.4 Host ID format
7.2.5 NetOp resource needs
7.3 IPX
7.3.1 Description
7.3.2 Configuration
7.3.3 Protocol Specific Settings
7.3.4 Host ID format
7.3.5 NetOp resource needs
7.4 TCP/IP
7.4.1 Description
7.4.2 Protocol Specific Settings
7.4.3 Host ID format
7.4.4 NetOp resource needs
7.5 APPC
7.5.1 Description
7.5.2 Protocol Specific Settings
7.5.3 Configuration
7.5.4 Host ID format
7.6 ISDN / CAPI
7.6.1 Description
7.6.2 Configuration
7.6.3 Protocol Specific Settings
7.6.4 Host ID format
8. TROUBLESHOOTING
8.1 THE NATURE OF REMOTE CONTROL
8.2 ANSWER TO COMMON PROBLEMS
8.3 NETOP ERROR MESSAGES
1. INTRODUCTION
---------------
1.1 SUMMARY
-----------
This chapter gives a brief introduction to remote control, the NetOp
products, examples of NetOp applications and an introduction to this
manual.
1.2 WELCOME TO NETOP FOR OS/2
-----------------------------
Welcome to NetOp for OS/2, an OS/2 product from Danware for re-
mote control of PCs over a wide variety of communication standards.
NetOp for OS/2 will allow you to remote control any OS/2 PC. Over
modems, LAN, WAN or ISDN (Capi). Furthermore, NetOp for OS/2
will interface with other NetOp remote control modules, such as Net-
Op for Windows.
By installing the guest software on a PC, that PC will be able to con-
nect to, and remotely control, a PC which has the host software in-
stalled.
The controlling PC, which is termed the guest, will show the screen of
the controlled PC - the host. Keystrokes and mouse action will be
transferred from the guest and executed on the host, screen updates
will be transferred from the host to the guest.It is as if you were
sitting in front of the controlled PC, even though it may be placed
anywhere on the globe.
NetOp for OS/2 contains advanced features, such as communication
via multiple standards, non-polling communication architecture, in-
tegrated bi-directional file transfer and support for hi-resolution
graphics.
1.3 ABOUT THIS MANUAL
---------------------
This manual contains documentation for the NetOp OS/2 Guest, the NetOp OS/2
Host and the NetOp OS/2 Gateway. You do not necessarily have all of these
modules, please ignore sections referring to pro- grams you do not have.
Read chapter 2 for information on installing NetOp, this chapter also contains
information about technical requirement and registration. Chapter 3 contains a
quick start guide. You should be able to get up and running by reading
chapters 2 and 3. Chapter 4 contains infor- mation about configuring and
running the NetOp Guest. Chapter 5 contains information about configuring and
running the NetOp Host. Chapter 6 contains information about configuring and
running the NetOp gateway. Chapter 7 presents detailed information about the
various communication protocols supported by NetOp. Chapter 8 is about
troubleshooting the NetOp programs.
It is important that you read the file README.TXT, which is supplied on your
NetOp distribution disks, this file contains important last minute
information.
1.4 EXAMPLES OF USE
-------------------
This section shows you a few examples of how you can benefit from using NetOp.
Support
Use NetOp to provide qualified help to users anywhere. Take over the
user's screen and on-line demonstrate the solution to a problem. NetOp's Help
service feature eases support in larger organisations. Transfer updated files
with NetOp's file transfer utility.
Remote configuration
Use NetOp to remotely configure servers and workstations.
Transfer configuration files and change the setup of PCs everywhere.
Using Your Office Computer From Your Home
NetOp will let you access your office PC from anywhere. You can execute
programs, and exchange data, read your E-mail, and access all your network
resources from your home computer.
1.5 THE NETOP SYSTEM
--------------------
NetOp for OS/2 consists of one or more of the following OS/2 modules:
Guest (NetOp for OS/2 Guest):
An OS/2 Presentation Manager application that allows a PC to remotely control
any PC which is running the NetOp host software.
Host (NetOp for OS/2 Host):
An OS/2 Presentation Manager application that allows an OS/2 PC to be
controlled from a NetOp Guest.
Gateway (NetOp for OS/2 Gateway):
An OS/2 Presentation Manager application that allows an OS/2 PC to function
as a non-dedicated gateway PC. The gateway PC can route external guest calls
to any NetOp host PC on the network.
1.6 CROSS PLATFORM SUPPORT
--------------------------
NetOp for OS/2 modules can access other NetOp modules, such as NetOp for
WINDOWS modules and RemPC v. 4.3 modules for DOS support.
With NetOp's Cross Platform Support you can remote control Windows PCs from
an OS/2 PC. You can also remote control OS/2 PCs from a Windows PC. For example,
you can remote control OS/2 based Lotus Notes Servers from your Windows
workstation. NetOp for OS/2 is backwards compatible with RemPC v. 4.3.
permitting you to remote control DOS PCs using as little as 3 - 6 Kb of memory.
1.7 USING THE NETOP PROGRAMS
----------------------------
If you are familiar with the OS/2 Presentation Manager interface, we trust you
will find NetOp's interface fairly easy. You can click with the mouse on
elements on the screen to activate them. If an element has a highlighted
letter, that element can also be activated, by pressing ALT combined with the
highlighted letter on your keyboard.
1.7.1 The On-line Help System
-----------------------------
The NetOp for OS/2 Guest contains an on-line, context-sensitive help
system.
You can get context-sensitive help on any action you are attempting,
by pressing F1. This brings up a window, which contains help for the
current action.
2. INSTALLATION
---------------
2.1 SUMMARY
-----------
This chapter describes the necessary steps for installing the NetOp
for OS/2 software on your computers.
Installation of all the NetOp for OS/2 modules is described. In case
your NetOp package does not contain some modules, please disregard the
sections that describe installation of modules you do not have.
It is very important that you read through any README file. These
files contains important information, which is not in this manual.
2.2 PREREQUISITE TASKS
----------------------
2.2.1 Technical Requirements
----------------------------
Your system must meet certain technical requirements to use the
NetOp system:
HARDWARE
- Computer IBM PS, IBM PC, or 100% compatible
- Modem Null modem, or modem with support for the AT command set.
- Video Guest: All resolutions supported by OS/2.
Host: All resolutions supported by OS/2
- Disk space Host, guest and gateway less than 1 Mb each
SOFTWARE
- OS/2 Version 1.3 or higher (including Warp)
- TCP/IP IBM's TCP/2 and FTP PC/TCP for OS/2 or compatible.
- APPC IBM Communication Manager/2 or compatible
- NetBIOS IBM, Microsoft, Novell or compatible
- ISDN Capi 1.1, 16 bit dll.
- IPX Netware Requester for OS/2 or compatible.
2.2.2 Checking Your Package
---------------------------
Your package should contain a manual, a registration card, and 3.5"
disk(s). If you need 5.25" disk(s), this can be accomodated. Please
contact your supplier or Danware.
NetOp packages consist of one or more NetOp modules. The follow-
ing OS/2 modules exists: The guest module, the host module and the
gateway module.
Table 2-2 lists the files, which are used by the NetOp for OS/2
modules.
Table 2-2 NetOp files
FILE NAME DESCRIPTION USED BY MODULE(S)
SETUP.EXE Installation program Guest/Host/Gateway
SETUP.INS Data file used by SETUP.EXE Guest/Host/Gateway
SETUP.DLL Library used by SETUP.EXE Guest/Host/Gateway
NGUEST2.Z Data file used by SETUP.EXE Guest
NHOST2.Z Data file used by SETUP.EXE Host
NGW2.Z Data file used by SETUP.EXE Gateway
NSHARED2.Z Data file used by SETUP.EXE Guest/Host/Gateway
NGUEST2.EXE The guest program Guest
NGUEST2.HLP Guest help file Guest
NGUEST2.SYS Library module Guest
DTL2.DLL Library module Guest/Host/Gateway
MODEMS.DAT The modem definitions Guest/Host/Gateway
README.TXT Important last-minute info Guest/Host/Gateway
NHOST2.EXE The host program Host
NHOST2.DLL Library module Host/Gateway
LOMEM.DLL Library module Host/Gateway
NHOST2WD.DLL Library module Host/Gateway
NHOST2.SYS Host device driver Host/Gateway
NHOST2W.SYS Host device driver Host/Gateway
NHOST2W.EXE Windows program Host/Gateway
NPRINT.PDR Printer re-direction Host/Gateway
NGW2.EXE The gateway program Gateway
In addition to these files, NetOp generates files with the extension
.CFG in which configuration information is saved. Also, the Setup
program will generate the file NLIB.Z on the floppy diskette.
2.3 INSTALLATION
----------------
The installation program requires OS/2 version 2.0 or newer.
To install NetOp on a PC running OS/2 version 1.3, please refer to
section 2.4, "Manual Installation".
To install the Guest, Host or the Gateway simply run the setup program
1. Insert the evaluation diskette into a floppy drive.
2. At an OS/2 prompt type a:setup and press ENTER. If the floppy
drive is not labelled A:, please substitute a: with the appropriate
letter.
3. Follow the on-screen instructions.
Actions performed by Setup:
Setup copies the NetOp files to the directory specified by the user.
It creates a program group if requested. After creating a back-up of the
config.sys file, the NHOST2.SYS and the NHOST2W.SYS files are added to the
config.sys file on the host PC and on the gateway PC. The NGUEST2.SYS file is
added to the config.sys file on the guest PC.
2.4 MANUAL INSTALLATION
-----------------------
This section explains how to manually install the NetOp programs.
Manual installation must be used for OS/2 version 1.3 systems, as the
installation program does not support OS/2 1.3. In order to install on
OS/2 1.3, you must first perform installation on OS/2 version 2.0 or
higher. Then you must copy the files to your OS/2 1.3 systems. If you
do not have an OS/2 version 2.0 or higher, then your supplier or
Danware can provide you with the files.
2.4.1 Installation
------------------
To manually install, please do the following:
1. Make a NetOp directory. E.g. by issuing the command md netop
ENTER from an OS/2 command prompt.
2. Copy all the files to the NetOp directory, either all guest, host or
gateway files depending on which module you want to install. See
Table 2-2 NetOp files". Please note that you do not need to copy
the Setup program and the files used by the Setup program.
3. On the host or gateway PC, add the device drivers NHOST2.SYS and
NHOST2W.SYS to the CONFIG.SYS. To do this load the CONFIG.SYS with an editor,
and add the lines:
DEVICE=C:\NETOP\NHOST2.SYS
DEVICE=C:\NETOP\NHOST2W.SYS
On the Guest add the device driver NGUEST2.SYS to the CONFIG.SYS
4. If desired the NetOp guest, host and gateway can be installed as
an icon on the OS/2 desktop or in a folder on the desktop, please
refer to OS/2's documentation for a description of how to do this.
5. Re-boot the PC.
2.4.2 Win-OS2 Full Screen support
---------------------------------
In order to remote control Win-OS2 Full Screen sessions, it is necessary to load
a windows program when the Win-OS2 Full Screen session is loaded.
The program is NHOST2W.EXE. You can either load this program manually, or add
it to the run= line in your Win-OS2 WIN.INI file. For example:
RUN=C:\NETOP\NHOST2W.EXE
This way, the program will automatically load when you start a full screen
Win-OS2 session.
2.4.3 Large scale deployment
----------------------------
NetOp contains features that are very helpful in the process of installing the
programs on a large number of PCs. Configuration information can be supplied as
command line parameters or from a configuration file. When unique IDs are
required, those can be passed on from the command line or generated by the
program.
For example, for the host program this procedure can be followed:
1. Install the host program to a "master" directory on a PC.
2. Load the host program and enter the necessary configuration information, such
as protocol specific settings and security settings. This information will be
saved in the file NHOST2.CFG.
3. Copy the files, including the NHOST2.CFG, from the master directory to your
target PCs.
4. Make sure the necessary few changes to the config.sys file are done on the
target PC.
5. For NetBIOS and IPX, the program needs a unique ID. You can specify this ID
on the command line. However, if no ID is specified, the program will use the
MAC address from the network adapter.
3. QUICK START
--------------
3.1 SUMMARY
-----------
This chapter presents a brief guide to getting started with NetOp.
After reading this chapter you should be able to set up the guest and
host, and start a remote control session. To set up the gateway, please
refer to chapter 6 "The Gateway".
3.2 THE HOST
------------
To start the host, double click on the host icon in the NetOp folder
on the OS/2 desktop, or start the program NHOST2.EXE from an
OS/2 command line.
The first time the host is run, the program prompts for various con-
figuration information.
First select the protocol to use for communication between the guest
and the host. This is done by clicking the appropriate radio button in
the Select protocol section of the setup dialog. After selecting a proto-
col, it might be necessary to fill in additional protocol specific infor-
mation.
Network remote control
For remote control via network, one should choose NetBIOS, IPX,
TCP/IP or APPC, if you are in doubt, please ask your network admin-
istrator. After selecting a protocol, enter a name in the Host ID field.
This is used by the guest to identify this PC. For some network proto-
cols (APPC and TCP/IP), the Host ID field is grayed out, these proto-
cols do not need the name, since a name is already inherent in the
protocol.
Modem remote control
For remote control via modem choose Serial/modem in the protocol
section of the setup. For serial communication a modem and a port
must be specified. If the host PC is using a modem which is not avail-
able in the list choose Hayes compatible (2400 bps or slower modems)
or Hayes compatible fast (other). If the host PC is using an external
modem, the COM port is the port the modem is connected to, the
COM port number can be read on the back of the PC. If the host PC
is using an internal modem, the COM port number is specified in the
modem card, refer to your modem documentation for further information.
ISDN remote control
For remote control via ISDN (Capi) choose ISDN/CAPI in the proto-
col section of the setup. Make sure that Local Number (EAZ) is cor-
rectly defined.
After having filled in the appropriate information, the host is started
by clicking the OK button. The host minimizes and awaits an incom-
ing call from a guest.
The host remembers the setup information for future use. The next
time the host is run simply click OK to initialize it.
To bypass the setup screen completely use the -L command line
switch. This loads the host directly, using the settings which were
specified the last time the host was run.
3.3 THE GUEST
-------------
To start the guest, either double click the guest icon in the NetOp
folder on the OS/2 desktop, or start the program NGUEST2.EXE
from an OS/2 command line.
The guest needs to know which communication protocols to initialize.
The first time the program is run it prompts the user for this protocol
information with a dialog. The information entered in this dialog can
later be changed.
The dialog is divided into a host section and a RemPC section. The RemPC
section is used to initialize support for backwards compatibility with
version 4.3 RemPCs. This is also being used to provide support for remote
control of DOS PCs. The Host section initializes support for ver. 5 Hosts,
both OS/2 and Windows based Hosts.
For remote control using a modem (or a null modem cable) Serial/Modem
should be chosen. For remote control via the Capi ISDN interface choose
ISDN/CAPI. For network remote control choose one of the network protocols
(please refer to the network administrator if in doubt about protocols).
The various properties sections of this dialog can normally be ignored,
unless the guest is going to communicate using FTP Software's implementation
of TCP/IP, in this case the guest PC's local IP address should be entered
in dot decimal notation (e.g. 208.0.0.1) in the IP Address field.
When the information is complete, click the OK button, this starts the
main NetOp Guest program.
Network remote control
To remote control via network do the following:
1. Click the combo box in the tool bar
2. Enter the name of the host PC in the Host ID field (for NetBIOS
and IPX, the name is specified by the host user. For APPC use the
LU name or alias. For TCP/IP use the IP address in dotted-
decimal notation or the TCP host name).
3. Click the call button in the tool bar.
Modem remote control
Press the EDIT button. Select Serial/Modem as protocol. In the Serial/Modem
properties section, the Phone number field should contain an `*', Modem Type
should be the modem attached to the PC (if the modem is not in the list choose
Hayes compatible for 2400bps or slower modems, otherwise Hayes com-
patible fast). If the host PC is using an external modem, the COM port
is the port the modem is connected to, the COM port number can be
read on the back of the PC. If the host PC is using an internal mo-
dem, the COM port number is specified in the modem card, refer to
your modem documentation for further information. After the dialog
box is completed click the OK button.
To call a host PC via modem do the following:
1. Click the combo box in the tool bar
2. Enter the phone number of the host PC in the Host ID field
3. Click the call button in the tool bar
ISDN remote control
1. Click the combo box in the tool bar
2. Enter the ISDN number of the host PC in the Host ID field
3. Click the EDIT button and select ISDN/CAPI. Press OK.
4. Click the CALL button in the tool bar
4. THE GUEST
------------
4.1 SUMMARY
-----------
This chapter describes how to use the NetOp Guest software. This is
the NetOp module that is used to remotely control a host PC.
Areas covered in the chapter include: How to start the guest, how to
configure the guest, and operation during remote control sessions.
For a description of how to install the guest please refer to chapter 2,
"Installation".
4.2 INTRODUCTION
----------------
4.2.1 Starting the Guest
------------------------
If the guest is available from the OS/2 desktop the guest can be
started by double clicking the guest icon
It is also possible to start the guest from an OS/2 command prompt:
Open an OS/2 command prompt, use the CD command to change to
the NetOp directory, and start the guest by typing nguest2 ENTER. It
is also possible to supply the guest with command line parameters,
see section 4.8, "Command line options" for a description of this.
4.2.2 The Guest Screen
----------------------
The guest program contains a menu bar where all NetOp commands
are available. There is also a tool bar with shortcuts to the most com-
mon commands.
The status line at the bottom of the NetOp Guest window contains
various information, for example (from left to right):
1. Hint for current command
2. The name of the current host table
3. Number of seconds connected to the active host PC
4. Keyboard mode (local or remote)
5. Current protocol (red if protocol not initialized)
4.3 CONFIGURATION
-----------------
4.3.1 Communication Settings
----------------------------
The communication settings dialog box is activated by choosing
Communication Settings from the Options menu.
This dialog controls which protocols are initialized at startup, and
properties for those protocols.
To remote control via a specific protocol this protocol must have
been initialized during startup. A consequence of this is that remote
control via a currently uninitialized protocol, involves first enabling
the protocol in the communication settings dialog and then restarting
the guest program.
The protocols are divided into two groups, namely Host (ver 5) and
RemPC (ver. 4.3). Host protocols are used to communicate with
NetOp version 5 hosts, whereas the RemPC protocols are used to
communicate with older version (4.3) NetOp hosts, this allows for a
mixed environment, where the hosts are gradually upgraded to
version 5.
For NetBIOS, IPX and TCP/IP some additional properties are
needed. Table 4-1 describes the properties:
Table 4-1 Protocol properties
PROTOCOL PROPERTY DESCRIPTION
NetBIOS Max Host sessions This is the maximum number of NetBIOS
hosts (ver. 5) the guest should be
able to remote control simultaneously.
Max RemPC sessions This is the maximum number of NetBIOS
RemPCs (ver. 4.3) the guest should be
able to remote control simultaneously.
Adapter Specify primary or alternate. Refer to
your network documentation for further
information
IPX Auto Bridge Support When Auto bridge support is enabled
NetOp will automatically build an inter-
nal list of all known IPX networks. The
guest will be able to find hosts on any
of the IPX networks in the list.
List Lets the user maintain a list of IPX net-
works. The guest will be able to find
hosts on any of the IPX networks in the
list.
TCP/IP IP Address For FTP's implementation of TCP/IP it is
necessary to specify the IP address of
the guest. The address should be in
dotted-decimal notation (e.g. 208.0.0.1).
APPC Mode This refers to which CM/2 mode NetOp
should use. This should normally be the
standard CM/2 mode #INTER.
4.3.2 Display Settings
----------------------
The Display Settings dialog box is activated by choosing Display Set-
tings... from the Options menu.
Display
In this section of the dialog various options with relevance to the
guest display can be set.
Status line
If this option is enabled the guest will display a status line in
the lower part of the main window. The status line contains
such information as time connected, current protocol, key-
board status, name of current host table, help for the current
action.
Large buttons
If this option is enabled NetOp will use large buttons in the
tool bar.
NetOp logo
If this option is enabled the NetOp logo will be displayed in
the background of the guest window.
Time connected
If this option is enabled total connection time to the active
host PC will be displayed in the status line.
Sound
If this option is enabled NetOp will beep whenever an error situation
occurs.
Press the OK button to accept changes, click Cancel to reject changes.
4.3.3 Modem database
--------------------
To activate the modem database dialog choose Modem database... from the
Options menu.
From this dialog NetOp's modem database can be maintained. Modem definitions
can be added, changed or deleted.
Section 7.1, "Serial/modem" contains a detailed description of the use
of modems with NetOp.
The modem name field contains the name of the current modem. To
change to another modem in the database activate the drop down
icon next to the modem field, and choose a modem from the list.
For some modems the string Fixed will be displayed in the lower left
part of the dialog. This means that the current modem has been de-
fined by Danware, and cannot be changed. To alter the settings for a
fixed modem make a copy of the modem definition and make the
desired changes on the copy:
1. Make the modem which is to be changed the current modem
(select from the Modem name drop down list).
2. Press the New... button.
3. Enter a name for the copy of the modem.
This new modem will not be fixed, and any desired changes can be
made to it.
To add a modem to the database, press the New... button, this will
add a modem similar to the current modem. Only the name, which
the user is prompted for, is different.
To change the name of the current modem press the Edit name...
button.
To delete the current modem press the Delete... button.
It is not possible to change the name of, or delete, fixed modems.
Therefore the Edit name... and the Delete... buttons will be disabled
when the current modem is fixed.
Each modem definition consists of a number of settings and a collec-
tion of modem strings. The settings are changed from the main mo-
dem database dialog, the strings are changed from a sub-dialog,
which is activated by pressing the Modem strings... button.
Table 4-5 contains a description of settings and strings.
The modem definitions are saved in the file MODEMS.DAT. If the
guest and host are installed in the same directory, this file is shared
among the two programs. Because of this changes made to the data-
base in one of the programs will be reflected in the other.
Table 4-5 Modem settings and strings:
Null modem
Should only be enabled for direct connections.
RTS/CTS
Often referred to as Hardware flow control. Should be en-
abled if supported by the modem.
Ignore DCD
Should usually be disabled. Some older modems are too slow
in establishing the carrier signal, causing NetOp to wrongly
report the connection to be lost. If your modem is old, and
unprovoked loses the connection, try enabling this option.
Baud Rate
Choose the maximum speed supported by the modem. Note
that this should typically be higher than the modem's line
speed. Typically, for a 9,600 bps modem, the baud rate
should be set to 38,400. Refer to the modem manual to
check the maximum speed supported by the modem.
Dial
This string is transmitted to the modem together with the
phone number whenever a dial attempt is made. This string
should normally be ATD?D (also see section 7.1,
"Serial/modem").
Hangup
This string is transmitted to the modem when a hangup is
performed. This string should usually be ATH0S0=0.
Setup 1/Setup 2
These are the initialization strings that are transmitted to the
modem before a connection is attempted, and before incom-
ing calls will be accepted. There is no difference between
Setup1 and Setup2, they can be considered two lines of the
same initialization string.
Send
This string is transmitted to the modem after the setup
strings from the guest, when a call is attempted. This field
should usually be left blank.
Answer
This string is transmitted to the modem from the host to
ready the computer for incoming calls. This string should
usually be ATS0=<number of rings>, where <number of
rings> should be substituted with a number. For example
ATS0=1, if the modem should go off hook after 1 ring.
4.3.4 Modem dialog
------------------
Choose Modem dialog... from the Options menu to display a window,
which lists all the commands the guest transmits to the modem, and
the modems responses. Useful for debugging purposes.
4.3.5 Hotkey Assignments
------------------------
Certain key combinations have special functions when pressed on the
guest. These combinations are referred to as hotkeys.
NetOp provides special hotkeys used to execute specific NetOp tasks
or used to substitute hotkeys reserved by the OS/2 operating System.
Initially most of these special hotkeys are not active.
To change/activate the hotkey assignments choose Hotkey assignment
from the Option menu.
Use the mouse or TAB to select the hotkey for which the definition
should be changed. Then simply change the key combination you
want to use. Press SPACE to turn a hotkey off.
If the Default button is pressed, all hotkeys will be set to the default
value defined by Danware.
Save changes by pressing the OK button. Changes are saved in the
file NGUEST2.CFG.
See section 4.6.11, "Hotkeys" for a description of the hotkey actions.
4.3.6 Font Assignments
----------------------
The font size used by NetOp during remote control of text mode
applications can be defined by the NetOp user
NetOp supports 4 different character modes, and for each mode it is
possible to assign the font resolution. To activate the font assignment
dialog choose Font assignment from the Option menu.
Choose the character mode and select the font resolution to be used
with that mode.
Press the OK button to save changes. The font assignments are stored
in the file NGUEST2.CFG.
Press the Default button to use the default font assignments defined
by Danware.
4.4 ESTABLISHING A SESSION
--------------------------
4.4.1 Host IDs
--------------
A host PC is prepared for remote control by loading the NetOp host
program. If NetBIOS or IPX is selected as the protocol the host user
has typically supplied a name. For Serial, ISDN, TCP/IP and APPC a
host id is inherent to the protocol (phone number, IP address/TCP
name, LU name). Table 4-6 gives an overview of host ids for the vari-
ous protocols.
Table 4-6 Host IDs:
Serial/Modem
The host is identified with its telephone number.
NetBIOS
The host is identified with a name which is specified in the NetOp host
program. Its a string with a maximum length of 32 characters.
IPX
The host is identified with a name which is specified in the NetOp host
program. It is a string with a maximum length of 32 characters.
TCP/IP
The IP address or the TCP host name. IP Address: Dotted-decimal notation
(a.b.c.d, e.g. 208.0.0.1). TCP host name: e.g. petere.sales.danware.com
APPC
The LU name. It is the fully qualified LU name or alias. e.g. DANWARE.PETERE
or PETER
ISDN
The host is identified with its ISDN number.
If no name is entered when using NetBIOS or IPX, the host will
automatically use the burnt-in network adapter address (typically the
MAC address) as a host ID. This is especially useful in large installa-
tions where manually specifying a name for each host might not be
feasible. These hosts can be reached by using a special syntax when
entering the host ID on the guest: 0xnnnnnnnnnnnn where
nnnnnnnnnnnn is the 12-digit hexadecimal burnt-in address. For in-
stance 0x08005AABD3EF.
4.4.2 Calling a Host
--------------------
To call a host enter the host ID in the combo box in the tool bar. The
guest is now ready to connect to the host, provided the host can be
reached, using the default protocol (shown inthe status bar at the bottom).
Press the call button on the tool bar to connect to the host. A connec-
tion can also be established by double clicking the name in the combo
box, or by pressing the ENTER key.
If the host has been called before, or has been manually added to the
host table, it can be called by selecting it from the combo box drop
down list (see section 4.5) and pressing the call button.
To call a host using another protocol than the default protocol, enter
the host name in the combo box and then activate the Edit button in
the tool bar.
Table 4-7 Edit host dialog fields
FIELD DESCRIPTION
Host ID The string which identifies the host PC.
Select Protocol Specify the protocol used to communicate with the
host PC.
Properties A detailed description of the protocols and their
properties is given in section7 "Protocols".
Resolution The setting AUTOMATIC tells NetOp to transmit the
screen resolution of the host screen to the guest.
Its possible to shrink the resolution either to the
resolution of the guest screen (the value SCREEN) or
to a specific resolution, eg. 800 x 600. Use this
feature to gain performance over slow speed links.
A lower resolution results in faster screen transfer.
Please note this setting can be changed on-line.
Compression The level of compression decides how much processing
NetOp uses for reducing the amount of data to be
transmitted between guest and host. For slow
communication links choose High. For faster links
choose Low. Normally this value should be Automatic
where NetOp automatically uses a compression level
based on the protocol selection. Eg. Low for NetBIOS
and High for Modem.
Color This value determines how many colors are transmitted
from the Host to the Guest. Choosing a lower number can
increase performance considerably, especially over slow
speed lines. Please note this setting can be changed
on-line.
Advanced keyboard This setting only relates to remote control of Hosts
running RemPC 4.30. It should always be on when
controlling OS/2 PCs. Remote controlling some DOS
applications might require Advanced keyboard to be off.
Max Call This setting only relates to remote control of Hosts
running RemPC 4.30. It determines how often the Guest
polls the RemPC 4.30 Host. This value should normally
not be changed.
When the call is initiated the guest might be asked to enter certain
data depending on the security settings used by the host. The guest
might have to enter a password, a guest ID and/or a call back num-
ber (serial/modem only). Furthermore, the guest might have to wait
for the host to confirm the access.
After this the host screen will appear as a window. It is possible to
connect to multiple PCs simultaneously. It is even possible to connect
to multiple PCs using different communication protocols.
When connected to multiple PCs use the mouse to switch between the
PCs. Click on the window to activate a PC. This can also be done
from the menu bar, make sure the host name is shown in the combo
box.
Serial/modem, ISDN and APPC Host IDs
For the serial/modem, ISDN and APPC protocols a special host ID
convention is used. Normally the host ID entered should be the
phone number (serial/ISDN) or the LU name/alias (APPC). Some-
times it is useful to use another ID, for instance "Johns Work PC"
might be a better name than 44532525. To address this NetOp in-
cludes a special phone number field for serial and ISDN, and a LU
Name field for APPC. This lets the user enter any ID in the Host ID
field, and then the phone number/LU name in a separate field.
Use the reserved value * in the phone number/LU name field to indi-
cate that the host ID should be used as phone number/LU name.
Calling a gateway
When a call is made via the APPC, ISDN or serial/modem protocol
the guest automatically senses if it has called a gateway (see section 6,
"The Gateway"). If it did reach a gateway the guest user is presented
with a screen, permitting the user to control the gateway itself, enter a
specific host ID, or ask the system to build a list of hosts available through
the gateway (including the gateway itself).
To bypass the list and reach a host through a gateway directly do the following:
1. Enter the Host ID of the network host in the Host ID field.
2. Enter the phone number, ISDN number or APPC LU of the gateway
in the phone number or LU name field in the Protocol specific
section of the Edit Host dialog box.
4.4.3 Hang-up
-------------
To stop controlling a PC, make sure the name of the host PC is
shown in the combo box. Then do one of the following:
1. Activate the hangup button on the tool bar.
2. Select Disconnect from selected Host PC from the Connection menu.
3. Close the window displaying the host screen.
4.5 HOST TABLES
---------------
NetOp stores information about hosts in host tables. The list dis-
played in the combo box in the tool bar, is the active host table. One
host table can contain up to 150 host definitions.
NetOp includes support for multiple host tables allowing the guest
user to switch between an unlimited number of host tables.
All host table information is stored in the file NGUEST2.CFG.
4.5.1 Add Host
--------------
Whenever the guest connects to a host PC not already listed in the
host table, this PC will be automatically added to the active host table.
It is also possible to add a PC to the host table without connecting to
it. This is done by choosing Add Host... from the Host menu, enter the
name of the host. This adds a host with the settings, specified in the
Default Host Settings dialog. To change the settings press the Settings...
button.
4.5.2 Build Host Table
----------------------
NetOp includes a facility which automatically scans the network and
collect host PC names.
Activate this facility by pressing the Build button on the tool bar, or by
selecting Build Host Table from the Host menu.
The build feature works on the NetBIOS and the IPX protocol. Fur-
thermore only initialized protocols (see section 4.3.1,
"Communication Settings") are scanned.
Please note that for security reasons the host must have declared its
name public to be picked up on the list.
If a network is accessed through a NetOp gateway, the build function
will pick up all the hosts on the network. However the network hosts
will be removed from the list when the connection to the gateway is
terminated.
4.5.3 Edit Host
---------------
When a host name is manually added to the host table NetOp will use
those host settings which were used for the previous entry.
The current settings for a host name can easily be changed. Select the
host name in the combo box and press the Edit button on the tool
bar, or select Edit Host... from the Host menu. This will activate a
dialog box.
Hosts which are added to the table using the build feature (see sec-
tion 4.5.2, "Build Host Table") will automatically have the correct
settings.
4.5.4 Remove Host
-----------------
Hosts can be removed from the host table one at the time. Select the
host name in the combo box, then choose Remove host... from the Host
menu.
Please note that a host name cannot be removed while the host is
being controlled. To remove a PC which is being controlled, first
press the Hangup button in the tool bar, then remove the name as
described above.
It is also possible to delete an entire host table. Select Delete Host ta-
ble... from the Host menu. It is not possible to delete a host table if
one or more PCs are being controlled.
4.5.5 Multiple Host Tables
--------------------------
NetOp includes the possibility of maintaining multiple host tables.
Use this feature to group the PCs for instance into departmental or
geographical units, or to break the 150 PC per table barrier.
Only one host table can be active at any given time. The active host
table's name is displayed in the status line. The contents of the active
table is displayed in the combo box in the tool bar.
To manage multiple host tables choose Management Host tables... from
the Host menu. From the resulting dialog box it is possible to add, delete,
rename and activate host tables.
Select a host table from the list with the mouse and choose an action
by pressing the appropriate button.
New...
Creates a new empty host table.
Delete...
Deletes the selected host table. Please note that the active host table
cannot be deleted. To delete the active host table, first activate another
table.
Edit...
Renames the selected host table.
Activate
Activates the selected host table.
Shortcuts
The Manage Host tables dialog box can be activated by double-clicking
the combo box in the tool bar with the mouse. A name can be acti-
vated from the Manage Host tables dialog by double-clicking the name
with the mouse.
4.5.6 Finding an Entry in the Host table
----------------------------------------
NetOp's host tables are alphabetically sorted (case insensitively). To
find a specific entry in the active host table do the following:
1. Activate the host table, by choosing List all Hosts from the Host
menu.
2. Now the entry field in the combo box is the active element, enter-
ing a string in this field will select the first element in the table
which starts with this string.
3. Select the specific entry by clicking it with the mouse, or by using
the UP ARROW or DOWN ARROW keys.
4.5.7 Miscellaneous
-------------------
Combo box
The combo box is used to enter names quickly. Click the combo box
with the mouse to activate it. The combo box can also be activated by
choosing Activate combo box from the Host menu.
View Host table
The host table can be viewed by clicking on the ε icon to the right of
the entry field. This can also be done by pressing ALT+DOWN ARROW
when the combo box is active, or by selecting List all Hosts from the
Host menu.
View connected Hosts
NetOp provides a feature for listing all PCs it currently is connected
to. Choose List connected Hosts from the Host menu. From this list it is
possible to switch the active window by selecting a host from the list
and clicking Select or by double-clicking the host name with the
mouse.
4.6 REMOTE CONTROL
-------------------
4.6.1 Getting Started
---------------------
When connected to a host PC, the host screen will be shown on the
guest display and the keyboard and mouse can be used to remote control
the host's keyboard and mouse.
The host screen is shown in a maximized NetOp Guest child window.
This window can be zoomed to full screen, restored to a smaller win-
dow, or otherwise manipulated.
4.6.2 Keyboard control
----------------------
NetOp provides two ways of controlling the host keyboard, local
mode and remote mode.
Local keyboard
When remote controlling most keys will be transferred to and exe-
cuted on the host PC, just as if the guest keyboard was physically
connected to the host PC. However a number of keys and key combi-
nations are reserved for local use by NetOp and are therefore not
transferred when NetOp is running in Local keyboard mode. Exam-
ples of such keys are the arrow keys, which are used for scrolling the
host window and are therefore not transferred to the host.
Remote keyboard
In order to get the most complete control of the host keyboard
NetOp should run in Remote keyboard mode. If this mode is selected
all keys are transferred to the host, except for a few combinations
which are used locally by OS/2 and NetOp (see section 4.6.11,
"Hotkeys").
Remote keyboard is the default mode. When running in full screen
mode (see section 4.6.9, "Zoom") the keyboard is always in remote
mode.
Switch between local and remote keyboard by activating the keyboard
mode button in the tool bar, this is the button with at keyboard on it,
the caption on the button is either Remote or Local. Please note that
the caption on the keyboard button is not the current mode, but
rather the mode which pushing the button will activate.
It is also possible to toggle the keyboard mode from the menu bar:
Choose Local keyboard from the Options menu. This will toggle the
mode.
The current mode is displayed in the status bar in the bottom of the
NetOp Guest window, which contains either the word Remote or Local,
indicating the current status.
4.6.3 Mouse control
-------------------
NetOp provides mouse support for applications running OS/2
Presentation Manager, and windowed Win-OS2 applications. Mouse
support is also available when controlling a NetOp for WINDOWS
host or when controlling DOS PCs via NetOp for OS/2's 4.30
compatibility mode.
There are two different ways to remote control the mouse in NetOp,
local mouse and remote mouse
Local mouse
When the guest mouse pointer is moved (the local mouse) this action
will not be transmitted to the host. As soon as a mouse button is acti-
vated, the host's mouse position will be updated to the local mouse
position, and the click will be executed. This method yields high
performance, since mouse activity generates a minimum of communi-
cation traffic.
The default mouse mode when initiating a remote control session is
local.
Remote mouse
In remote mouse mode, the host's mouse will always follow the guest
mouse. This is a slower method, but in some cases this is the best
choice: If the guest user is instructing a host user on how to accom-
plish a specific task, which involves the mouse, in this case remote
mouse is best since this mode lets the host user follow every guest
mouse movement.
The mouse mode is toggled by choosing Local mouse from the Options
menu.
4.6.4 Lock Host Keyboard and Mouse
----------------------------------
NetOp allows the guest user to lock the keyboard and mouse on the
host PC.
Choose Lock keyboard and mouse on Host from the Options menu. It will
not be possible to use host keyboard and mouse until the guest un-
locks them.
Use this feature to prevent a user to interfere while working on a
host, e.g. when re-configuring a server. The host keyboard and mouse are
unlocked by choosing Lock keyboard and mouse on Host from the Options menu.
Please note that the host program must have been configured to al-
low lock of keyboard and mouse, otherwise the menu item will be dis-
abled on the guest. Refer to section 5.4.2, "Guest Rights" for a de-
scription on how to configure guest rights on the host.
4.6.5 Boot Host
---------------
NetOp includes a feature which lets the guest boot the host PC.
Choose Boot Host PC from the Options menu.
A confirmation dialog box will be displayed to ensure that the host
PC is not booted by mistake.
Please note that the host program must have been configured to al-
low boot from the guest, otherwise the menu item will be disabled on
the guest. Refer to section 5.4.2, "Guest Rights" for a description on
how to configure guest rights on the host.
4.6.6 Chat with Host
--------------------
The chat function brings up a window on the host and guest which
allows the users to communicate.
Press the chat button on the tool bar or choose Chat with Host PC
from the Options menu to initiate a chat.
A similar dialog will be displayed on the host. Everything typed on
the host and guest will be communicated between the users, and dis-
played in the dialog boxes.
Please note that chat has to be enabled in the host security settings
(see section 5.4, "Security"), otherwise the chat button and the chat
menu item will be disabled.
TIP: You can minimize the chat window. This way you can remote control another
PC, quickly switch back to your chat window and continue your dialogue.
Host Chat Request
NetOp allows a host user to request chat. When a host user requests
chat, the guest PC will beep shortly to notify the guest user. When not
running in full screen mode the guest user will be notified by a mes-
sage flashing on the windows bar of the remote PC requesting chat.
Chat can be initiated as described above.
4.6.7 Blank screen
------------------
Use this feature to blank the screen on the host PC. For security rea-
sons, this is only possible if this feature has been enabled on the host.
4.6.8 Screen resolution
-----------------------
Depending on the screen resolution of the guest and host PCs, the
complete host screen or only part of it will be visible.
For example it is possible to control an XGA PC from a PC running
VGA resolution.
If the host is running a higher video resolution than the guest, the
guest will normally display as much of the host screen as possible, by
using scroll bars, the guest user can view all parts of the host screen.
By using NetOps feature for shrinking the host screen resolution, it
will often be possible to view a complete high resolution screen on a
PC running a lower resolution. If the guest is running a higher video
resolution than the host, the host might not take up the entire window on
the guest, the remaining part of the window will be black.
4.6.9 Zoom
----------
Instead of viewing the host screen in a window, it is possible to zoom
to a full screen view. In full screen view the host takes up the entire
guest screen, this gives the guest the most realistic view of the host.
The host screen can be zoomed by activating the Zoom key on the tool
bar, by choosing Zoom window from the Window menu, or by pressing
the hotkey defined for this action (default CTRL+Z).
Switch back from zoom mode by pressing the zoom hotkey (default
CTRL+Z).
If the host is running a higher resolution than the guest, the guest
will display scroll bars. If the guest is running a higher resolution
than the host, the remaining area on the guest screen will be black.
4.6.10 Window manipulation
--------------------------
When controlling multiple PCs simultaneously, NetOp provides a
button in the tool bar that will toggle between 3 modes.
One mode will cascade the windows, one will position the windows
vertically and one will position the windows horizontally.
It is also possible to directly select a mode. This is done from the
Window menu.
4.6.11 Hotkeys
--------------
NetOp provides special hotkeys used to execute specific NetOp Guest
tasks or used to substitute key combinations reserved by the OS/2 op-
erating system.
Initially most of these hotkeys are not active. Please refer to section
4.3.6 for instructions on how to define or redefine the hotkeys. Table
4-9 describes the hotkeys:
Table 4-9 Hotkey descriptions:
Zoom In/Out
Zoom the active host window to full screen or go back to normal
mode. This hotkey cannot be switched OFF, but it can be rede-
fined. The default value of this hotkey is CTRL+Z.
List Conn hosts
List all host PCs currently being controlled.
Next Window
Activate the window of the next host PC.
Ctrl+ESC
When CTRL+ESC is pressed on the guest, the key combination is
intercepted by the guest OS, the result is the guest task list. To
obtain the host task list define this hotkey (or use the Ctrl+Esc
button on the tool bar).
Alt+ESC
When ALT+ESC is pressed on the guest, the key combination is
intercepted by the guest OS. To execute the combination on the
host, define this hotkey.
Alt+Tab
When ALT+TAB is pressed on the guest, the key combination is
intercepted by the guest OS. To execute the combination on the
host, define this hotkey.
4.6.12 File Transfer
--------------------
NetOp includes an advanced file transfer tool which lets the user
transfer files between the guest and the host during a remote control
session.
To activate the file transfer tool, choose Transfer files to/from Host...
from the Options menu.
The various fields of this dialog box are described below:
Send files
Check this radio button to send files from the guest to the host.
This button is disabled if Receive files from guest is disabled in
the host security settings.
Receive files
Check this radio button to send files from the host to the guest.
This button is disabled if Send files to guest is disabled in the
host security settings.
Overwrite if file exists
If this check box is enabled existing files with the same name as
the transferred file will be overwritten. Use this option with care
since data might be lost. If this option is disabled files with
names which already exist will not be transferred.
Include subdirectories
Use this in combination with wildcards to transfer entire or par-
tial directory structures. Example: Entering c:\*.* in the Source
field and enabling Include subdirectories will transfer the entire
C-drive.
Source
Enter the file name(s) to transfer from, note that the usual OS/2
wildcards (?, *) are valid.
Destination
Enter a path or file name to transfer the files to. To specify a
path rather than a file name end the field with a backslash. Ex-
ample: Destination is non-existing directory C:\DATA, entering
c:\data in the destination field will create the file C:\DATA and
transfer the data to this file, entering c:\data\ in the destination
field will create the directory C:\DATA and transfer the files to
this directory.
The dialog box also contains a list of transferred files, and the prog-
ress of the file currently being transferred.
Press the Start Transfer button to start the file transfer, when a file
transfer is started the Start Transfer button changes to Cancel Transfer.
Press Close Window to close the dialog box. Please note that closing the dialog
box when a file transfer is in progress will not cancel the file transfer,
which will be continued in a background thread, choose Transfer files
to/from Host... from the Options menu again to bring back the file
transfer dialog.
Please note that the host might have disabled receiving, sending or
both (see section 5.4, "Security"), according to these settings the file
transfer menu item or one of the send/receive radio buttons might be
disabled.
4.6.13 Printer re-direction
---------------------------
NetOp for OS/2 provides a feature for re-directing print from the
OS/2 host to the OS/2 guest. When receiving a print from the host,
the guest program will print this to the default printer on the guest.
Please make sure that the default printer on the guest is compatible
with the printer driver used on the host.
In order to print, remote control the host, then print to a printer
where the output port is defined as a NetOp output port driver. See
section 5.7.
4.7 HELP SERVICE
----------------
NetOp contains an advanced Help service feature, which is designed to
ease the process of doing on-line support on a network.
It is possible for a NetOp guest to register as a help provider on the
network. Hosts can now request help from the registered help providers.
To register a guest as a Help provider choose Help service settings...
from the Options menu. In the resulting dialog it is possible to define
up to 3 Help services.
A Help service could be the name of a specific application this guest
wants to provide support for. Or it could be the name of the person
providing the support. Whenever a hosts activates the Request help
function it will be presented with a list which contains all help
services registered by any guest on the network.
After help services have been registered, the guest should activate
Show request for help... from the Options menu. This opens a
window which displays all requests from hosts to the services regis-
tered by the guest.
Each line represents one request. For each request is shown the host
ID, the time the request was made, and a problem description en-
tered by the host user when the request was made. The list is conti-
nously updated; requests are automatically removed if they have been
serviced by a guest, or cancelled by the requesting host user.
To answer a help request double click the line in the request window
(or select it with the arrow keys and press ENTER). This will start a
remote control session with the host which made the request.
Multiple guests can provide help service simultaneously. They can
even register the same help services. If for instance multiple guest
services register the service OS/2 support, this service will appear once
on a host's list of services. If the host request help from this service,
the request will appear in the request window on all the guests which
registered OS/2 support. When one of the guests answers the request,
it will dynamically be removed from the list on the other guests.
4.8 COMMAND LINE OPTIONS
------------------------
A wide range of the NetOp Guest's features can be controlled from
the command line. The syntax for starting the guest is:
NGUEST2 [-switch1 [-switch2 _ ] ] [group]
Options are set by using one or more command line switches. Com-
mand line switches should be preceded with the character -. The
switches accepted by the NetOp Guest are described in Table 4-11.
group is a group name, which is only used when communicating with
version 4.30 RemPCs. RemPCs can be defined as belonging to a
group, in this case only guests started with the same group name will
be able to control those RemPCs.
By using the -N switch it is possible to connect to any NetOp Host.
The -N switch should be followed by a host specification (described in
Table 4-12). If the host to be called from the command line already
exists in the guest's host table, the host specification is just the name:
NGUEST2 -N:NAME=PETER
If the host is not defined in the host table one or more settings can be
specified directly from the command line. For the settings which are
not defined on the command line default values are used. Example:
NGUEST2 -N:NAME=PETER;PROT=HN
This will start the guest, which will attempt a connection to a host
with the host ID PETER, using the NetBIOS protocol, other settings
will have the default value (e.g. compression low).
Table 4-11 Guest command line switches
OPTION DESCRIPTION
Hp+, Hp- Controls initialization of host (ver. 5) protocols.
Substitute p with a character to specify the protocol:
N=NetBIOS, I=IPX, T=TCP/IP, A=APPC,
S=Serial/modem, C=ISDN Capi. Use + to enable a proto-
col, - to disable.
Examples:
-HN+ : Initialize NetBIOS
-HA- : Do not initialize APPC
Rp+, Rp- Controls initialization of RemPC (ver. 4.30) protocols.
Substitute p with a character to specify the protocol:
N=NetBIOS, I=IPX. Use + to enable a protocol, - to dis-
able.
PD Disable all currently enabled protocols
IC Instant close. The NetOp Guest program will exit when
the last host window is closed.
IL:nnnnnnnn Add network nnnnnnnn to the IPX network list (see
section 7.3, "IPX" for a description of the IPX
network list)
L+, L- Controls automatic build of IPX network. L+: Enable
build, L-: Disable build.
N:host specification Connect to the host described with host specification.
A host specification has the following form:
field1=val1 [; field2=val2 _ ]
See Table 4-12 for a description of host specification
field and values.
Table 4-12 Host specification
FIELD VAL DESCRIPTION
NAME string Host PC name
KBD ADV Advanced keyboard routine
NOR Normal keyboard routine
COMP AUTO Automatic compression
NONE No compression
LOW Low compression
HIGH High compression
COLOR AUTO Automatic color selection
MAX_2 Max 2 colors
MAX-16 Max 16 colors
MAX_256 Max 256 colors
SCREEN_RES AUTO No reduction of resolution
SCREEN Reduce resolution to guest
1024_768 Reduce resolution to 1024_768
800_600 Reduce resolution to 800_600
640_480 Reduce resolution to 640_480
320_240 Reduce resolution to 320_240
PROT HN Communicate with host using NetBIOS
HI Communicate with host using IPX
HT Communicate with host using TCP/IP
HA Communicate with host using APPC
HC Communicate with host using ISDN Capi
HS Communicate with host using Serial/modem
RN Communicate with RemPC using NetBIOS
RI Communicate with RemPC using IPX
HA_NAME string Host APPC name or alias
HA_MODE string APPC mode
HC_PHONE string Host ISDN number
HC_CHANNELS 1 Use 1 B-channel
2 Use 2 B-channels
HC_LOCAL number Local number (EAZ)
HC_SHORT_HOLD number Enable short-hold mode (10 - 256)
FALSE Disable short-hold mode
HS_PHONE string Host phone number
HS_MODEM string Modem name. Modem must exist in the modem
database, otherwise null-modem is used.
Blanks should be substituted with _.
Example: HAYES_COMPATIBLE
HS_PORT string Port name. Example: COM1
HS_BAUD string Data speed for serial communication.
Example: 38400
HS_PULSE TRUE Use pulse dial for serial connection
FALSE Use tone dial for serial connection
Following settings only for communication with ver 4.30 RemPCs
RI_BRIDGE string IPX bridge address. Must be a 12 digit
hexadecimal number
RI_NET string IPX network number. Must be an 8 digit
hexadecimal number
RI_NODE string IPX node number. Must be a 12 digit
hexadecimal number
MAX number Max calls, number must be an integer in the
range -10 to 2000
Examples
Initialize the IPX protocol, and add 000BABE1 to the list of IPX net-
work number, where the guest should look for hosts:
NGUEST2 -HI+ -IL:000BABE1
Initialize the serial protocol, and call a host, using a modem, with the
phone number 112. Use the modem definition Hayes compatible:
NGUEST2 -HS+ -N:NAME=112;PROT=HS;HS_MODEM=HAYES_COMPATIBLE
Call the host named PETER (for which settings already are defined in
the default host table). Exit the NetOp Guest when the connection to
PETER is terminated:
NGUEST2 -N:NAME=PETER -IC
5. THE HOST
-----------
5.1 SUMMARY
-----------
This chapter describes how to use the NetOp Host software. This is
the NetOp module that prepares a PC to be remotely controlled.
Areas covered in the chapter include: How to start the host, how to
set up the host, security configuration, operation during remote con-
trol sessions.
For a description of how to install the host please refer to chapter 2,
"Installation".
5.2 STARTING THE HOST
---------------------
5.2.1 From the desktop
----------------------
If the host has been installed as an icon on the desktop, or in a desk-
top folder, it is started by double clicking the host icon.
5.2.2 From an OS/2 prompt
-------------------------
To start the host from a command prompt do the following:
1. Open an OS/2 command prompt.
2. Use the CD command to change to the NetOp directory.
3. Start the host by typing nhost2 ENTER.
It is also possible to supply the host with command line parameters,
see section 5.6, for a description of this.
5.2.3 Automatically at Startup
------------------------------
The host can be started automatically in two different ways:
1. Install the host in the OS/2 Startup folder. In the settings of the
NetOp host program object -L should be specified as command
line parameter.
2. Include the lines (provided that NetOp is installed in C:\NETOP,
otherwise substitute the appropriate directory):
CD \NETOP
START NHOST2 -L
CD \
in the file STARTUP.CMD, placed in the root of the boot drive
5.2.4 Initialization
--------------------
If the host is started without command line parameters, the host
setup dialog is displayed. The default settings in this dialog are the
settings specified the last time the host was run, these settings are
read from the file NHOST2.CFG.
After the setup dialog has been completed the host will minimize and
initialize. After this it is ready to accept incoming calls from a NetOp
Guest.
If the host is started with the -L command line parameter it initial-
ized directly after startup and minimizes. The host will use the same
settings as the last time it was run.
From the host's minimized state it is possible to follow its status in
two ways:
1. The icon title will display the status, e.g. NetOp Host -
Waiting for call or NetOp Host - Connected.
2. When connected to a host, an open eye will be displayed in the
icon.
Use the OS/2 settings notebook for the NetOp Host to specify that
the program should minimize to the desktop - by doing this the host
user will always know if he is being controlled.
To bring out the host window after initialization activate the OS/2
task list by pressing CTRL+ESC and double click the line "NetOp
Host" with the mouse.
5.3 SETTING UP THE HOST
-----------------------
If the host is started without command line parameters, the setup
dialog is displayed at startup.
The setup dialog can also be activated by choosing Setup... from the
host's configuration menu.
In the dialog box the communication protocol and host ID are
specified. NetOp includes support for serial communication (typically
modem or a null-modem cable), ISDN and various LAN and WAN
protocols (NetBIOS, IPX, TCP/IP and APPC). If in doubt about
which communication protocol to use, please ask the network admin-
istrator.
Select a protocol from the Select Protocol section of this dialog box.
For some of the protocols additional protocol specific settings need
to be specified, these settings are described in detail in section 7,
"Protocols".
For the NetBIOS and the IPX protocol it is possible to specify a host
ID, this is a character string with a maximum length of 32. If no ID is
specified, the MAC address will automatically be chosen.
Press OK to accept the host settings.
The settings are stored in the file NHOST2.CFG
Please note that when communication settings have been changed,
the host must be closed down and restarted before the changes take
effect.
TIP: If no ID is specified for NetBIOS or IPX, the MAC address will auto-
matically be chosen (Auto Host ID), a very powerful feature. By combining
the Call for help feature and the Auto Host ID, a remote control session
can be established without knowing the Host ID. Instead, the host user is
asked to press Request help, and then the guest can select the auto
host ID appearing in the Help service request window. The Auto Host
ID also opens up for possibilities such as loading the host program
from a server, as no unique ID needs to be entered for each PC.
Modem database
Choose modem database from the Configuration menu to access
NetOp's modem database. See section 4.3.4, "Modem database" for a
description of how to use the modem database.
Modem dialog
Choose Modem dialog... from the Configuration menu to display a win-
dow, which lists all the commands the host transmits to the modem,
and the modems responses. Useful for debugging purposes.
TIP: When loading, the program will immediately begin to initialize
the modem. Therfore it might not be possible to view the commands
sent to the modem. To overcome this, load the host from the com-
mand line using the parameter /L:30, this will delay the initialization
for 30 seconds, providing plenty of time to open the modem dialog.
5.4 SECURITY
------------
The NetOp host includes a number of security features. Use these to
prevent unauthorized access to the host PC, and to limit the number
of actions possible for the guest PC.
The security settings can all be accessed from the dialog box Security
Configuration, this dialog is activated by choosing Setup... from the
host's Configuration menu, activate the Security... button from the re-
sulting dialog box.
5.4.1 Maintenance Password
--------------------------
The host's security settings can be protected by a maintenance pass-
word. This password has to be entered each time the security configu-
ration dialog is activated. This ensures the host user against unau-
thorized changes to security settings (e.g. by a guest).
To define (or change) the maintenance password press the Mainte-
nance Password... button on the security configuration dialog box.
Toggle the Use maintenance password check box to enable or disable
the maintenance password. If the password is enabled enter the pass-
word in the New password field, re-enter the password in the Confirm
password field. Activate the OK button when done.
5.4.2 Guest Rights
------------------
The section of the Security Configuration which is labelled Allow Guest
to contains the settings which describe how much a guest is allowed to
do on this host. The various options are described below:
Use keyboard and mouse
If this option is disabled the guest will not be able to
remote control the host's keyboard and mouse, but
only view the screen. Sometimes referred to as View
only.
Chat
Specifies whether the guest is allowed to start a chat
(see 5.5.1, "Request Chat" for a description of chat).
Send files to host
Specifies whether the guest is allowed to transfer files
from the guest to the host.
Receive files from host
Specifies whether the guest is allowed to transfer files
from the host to the guest.
Blank screen
Enable this to allow the guest to blank the screen on
the host.
Lock keyboard and mouse
Specifies whether the guest is allowed to lock the host
keyboard and mouse.
Boot the PC
Specifies whether the guest is allowed to boot the host
PC.
5.4.3 Public name
-----------------
The NetOp guest has a build function, which finds hosts on the net-
work. However it only finds hosts with Public name.
If Public name is enabled a guest doing a build will pick up the host
name. If public name is disabled the host name will not appear on
the built list on the guest. This adds a layer of security, since the guest
must know the host ID in order to initiate a remote control session.
5.4.4 Password
--------------
The host can be protected by a password, which a guest must enter
correctly in order to control the host.
To use a password enable the Password check box in the security con-
figuration dialog. Enter the password in the field to the right of the
check box, the password will not be displayed when entered.
Password policy
It is possible to define a password policy on the host, this specifies
how many password attempts a guest has, and what will happen if the
limit is exceeded.
Press the Guest password policy... button to define a password policy. In
the resulting dialog choose the maximum number of wrong pass-
words a guest can enter, and what to do if the limit is exceeded: Han-
gup, Disable (do not take further calls from any guest), or boot host.
5.4.5 Confirm access
--------------------
If this option is enabled, the host will be presented with a dialog box,
every time a guest attempts a connection. From this dialog the host
user can accept or deny the remote control attempt.
Enabling confirm access makes sure the host is not accessed while
unattended.
Enable or disable confirm access by toggling the Confirm access check
box in the security configuration dialog box.
5.4.6 Inactivity time-out
-------------------------
If no data is being transferred between the guest and host, this setting
can force the host to disconnect after a pre-defined number of min-
utes.
Using this feature, one can for example prevent expensive telephone
charges in case an employee has left a guest connected to a host.
If the guest program stops working, e.g. due to power failure, the
host program might not detect this before the host screen changes.
Using the inactivity time-out, its possible to force the host to re-
initialize after a certain period of inactivity.
5.4.7 Call-back
---------------
This setting is only used if the host is using the serial/modem proto-
col.
If call-back is enabled, the host will answer incoming calls from a
guest and then hangup and call the guest back.
The call-back facility serves two purposes:
1. Security: By specifying a call-back number it can be ensured that
the host is only controlled from one specific telephone number.
2. Phone charges: Call-back can be used to reverse the phone
charges from guest to host.
There are three different settings for call-back, all found in the Call-
back section of the security configuration dialog box:
1. No call-back: No call-back will be performed.
2. Call back to: A call back is attempted to the specified number.
3. Roving call back: The guest is prompted for the number to call
back to, especially useful for reversing phone charges.
Furthermore it is possible to enter a number of seconds the host
should wait after the guest calls before the call-back is attempted. Use
this to make sure the guest is initialized and ready to be called back.
Enter the number of seconds to wait in the Wait before call-back field.
The Call-back timeout field is the number of seconds the host should
wait (assuming the guest is not reached) before the call-back times out
and is considered failed.
5.5 ON-LINE CHOICES
-------------------
This section describes the choices which are only available on the host
during a remote control session.
5.5.1 Request Chat
------------------
To request a chat session (see section 4.6.6, "Chat with Host") with
the guest, choose Request chat from the Configuration menu. The host
will send a beep to the guest and display a message in the title bar of
the host window on the guest.
The guest then has to initiate the chat, e.g. by pressing the chat but-
ton on the guest tool bar.
Please note that the guest cannot see the message when controlling
the host in zoomed full screen mode. In this case only the beep will
notify the guest.
5.5.2 Hangup
------------
The host can choose to disconnect from the guest at any time during
a remote control session. Choose Hangup from the Configuration
menu to disconnect the guest. A confirmation dialog will be dis-
played.
5.5.3 File Transfer
-------------------
When the guest is performing a file transfer (see section 4.6.12, "File
Transfer"), the host can see the status by choosing File Transfer... from
the Configuration menu.
From the resulting dialog box it is possible to see which files have
been transferred and the progress with the current file.
The file transfer can also be interrupted from this dialog box by
choosing Cancel. Click close to close the dialog box without interrupt-
ing the file transfer.
5.5.4 Call for Help
-------------------
The host user can activate the Request help... item in the Configu-
ration menu to initiate a Help request to any registered help provider
(see section 4.7, "Help Service").
Enter a description and choose a help service. The help services ap-
pearing in the list are the ones registered by the guests providing
help on the network. Press OK, the request is now registered.
Whenever a call for help is made the request appears on the screen of
the help providing guest(s). When a guest handles the request a re-
mote control session is automatically started between the help provid-
ing guest and the help requesting host.
A host can only have one pending help request. To cancel a pending
request choose Request help... again. This will inform the host
user about any pending request, which the user can then choose to
cancel.
5.6 COMMAND LINE OPTIONS
------------------------
A wide range of the NetOp Host's features can be controlled from the
command line. The syntax for starting the host is:
NHOST2 [-switch1 [-switch2 _ ] ]
Options are set by using one or more command line switches. Com-
mand line switches should be preceded with the character -. The
switches accepted by the NetOp Host are described in Table 5-2.
Table 5-2 Host command line switches:
L [:n ]
Load the host directly without prompting for setup informa-
tion. The settings used the last time the host was run will be
used.
Optionally a delay in seconds can be specified e.g. -L:10, this
will delay the initialization for the specified number of sec-
onds, use this feature if the host must wait for some communi-
cation device to be ready before initializing.
GA+ , GA-
Controls if the host sends a controlling guests mac / ip address
to a calling guest. GA+ sends, GA- does not send.
FRAMES:xxx
Number of frames to check per search. Default = 20
SLEEP:xxx
Time between each search. Default = 10 (milisecs.).
N:host specification
Use this parameter to override one or more of the settings
used the last time the host was started.
A host specification has the following form:
field1=val1 [; field2=val2 _ ]
See Table 5-3 for a description of host specification field and
values.
By using the -N switch it is possible to completely specify the host
settings from the command line. It is not necessary to enter all the
settings. For settings which are not entered the values from the last
time the host was run are used.
Table 5-3 Host specification
FIELD VAL DESCRIPTION
NAME string Host PC name
PROT HN Communicate with guest using NetBIOS
HI Communicate with guest using IPX
HT Communicate with guest using TCP/IP
HA Communicate with guest using APPC
HS Communicate with guest using Serial/modem
HC Communicate with guest using ISDN Capi
HC_CHANNELS string Number of B-channels, 1 or 2
HC_SHORT_HOLD TRUE Allow short-hold mode
FALSE Disable short-hold mode
HC_LOCAL string Local number (EAZ)
HA_MODE string APPC mode
HS_MODEM string Modem name. Modem must exist in the mo-
dem database, otherwise null-modem is used.
Blanks should be substituted with _. Example:
HAYES_COMPATIBLE
HS_PORT string Port name. Example: COM1
HS_BAUD string Data speed for serial communication.
Example: 38400
HS_PULSE TRUE Use pulse dial for serial connection
FALSE Use tone dial for serial connection
SEC_MAINT_PASS string Current maintenance password. If the host
has defined a maintenance password, this
field must match that password.
SEC_MAINT_NEW string Use this parameter to change the mainte-
nance password, leave blank to disable main-
tenance password
SEC_PASS string Sets the password the guest must enter to
access this host. Leave blank for no password.
SEC_PASS_MAX number Maximum password retries
SEC_PASS_POLICY BOOT Boot if too many wrong passwords
DISABLE Disable host if too many wrong passwords
HANGUP Hangup if too many wrong passwords.
SEC_PUBLIC_NAME TRUE Enable public name
FALSE Disable public name
SEC_CONFIRM TRUE Enable confirm access
FALSE Disable confirm access
SEC_KBD_MOU TRUE Allow guest to control keyboard/mouse
FALSE Guest not allowed to control keyboard/mouse
SEC_CHAT TRUE Allow chat
FALSE Do not allow chat
SEC_UPLOAD TRUE Allow guest to send files to host
FALSE Do not allow guest to send files to host
SEC_DOWNLOAD TRUE Allow guest to receive files from host
FALSE Do not allow guest to receive files from host
SEC_BLANK TRUE Allow blank of screen
FALSE Disable blank of screen
SEC_LOCK TRUE Allow guest to lock host keyboard/mouse
FALSE Do not allow guest to lock host keyboard/mouse
SEC_BOOT TRUE Allow guest to boot host
FALSE Do not allow guest to boot host
SEC_INACTIV_TIMO number In-activity time-out in minutes
SEC_CALL FALSE Disable call-back
ROVING Perform roving call-back
number Call back to number
SEC_CALL_WAIT number Seconds to wait before call-back
SEC_CALL_TIMO number Call-back time out
Examples
Initialize the host directly from the command line (use same settings
as last time):
NHOST2 -L
Initialize the host with the NetBIOS protocol. Use JOHN as host Id,
and PASS as password:
NHOST2 -L -N:NAME=JOHN;PROT=HN;SEC_PASS=PASS
5.7 PRINTER RE-DIRECTION
------------------------
5.7.1 Description
-----------------
The NetOp for OS/2 guest and the NetOp for OS/2 host includes a
feature for printer re-direction. Using this feature, it is possible to re-
direct print from the host to the guest.
Print from the desktop or Presentation Manager programs can be re-
directed. For example, drag a document to the printer symbol on the
desktop and this document can be printed on the guest printer in-
stead of the host printer.
5.7.2 Installing support for printer re-direction
-------------------------------------------------
In order to re-direct print from a host PC, the host PC must be pre-
pared by installing a special NetOp output port driver.
1. Select the printer on your desktop, select settings and output. Select
an output port, eg. LPT1. Select Install.
2. Place a floppy disk containing the NetOp driver NPRINT.PDR in drive A:.
Press Refresh and then Install.
3. Prepare a printer that as output port uses the NetOp output driver
/PIPE/NPRINT (select printer setting, then output, then
/PIPE/NPRINT).
Make sure that the printer driver used, is compatible with the printer
driver used on the guest PC. For example, it will not be possible to
re-direct from a postscript printer driver to a matrix printer driver.
Also, please make sure that the form defined for the printer driver on
the host and the guest are the same.
There is no special configuration needed on the guest PC, except
being aware that print from the host will be re-directed to the default
printer on the guest.
6. THE GATEWAY
--------------
6.1 SUMMARY
-----------
This chapter describes how to use the NetOp Gateway software. This
is the NetOp module that lets a PC function as a gateway for NetOp
traffic.
A NetOp Gateway will accept incoming calls from a guest via modem,
ISDN or APPC and route these calls to hosts via a network protocol
(NetBIOS, IPX or TCP/IP).
Areas covered in the chapter include: How to start the gateway, how
to set up the gateway, security configuration.
For a description of how to install the gateway, please refer to chapter
2, "Installation".
6.2 INTRODUCTION
----------------
The NetOp Gateway is used to let an external guest PC access any PC
on a network through one single gateway PC.
The gateway PC is prepared to route NetOp traffic, by running the
NetOp gateway module.
To externally access the PCs on the network via the gateway PC, the
guest PC has to pass through a separate gateway security layer. After
the guest has gained access to the network, the individual host secu-
rity settings still apply.
The gateway module can also act as a host, allowing for the gateway
PC itself to be remotely controlled, either from a network PC or from
an external PC.
6.3 STARTING THE GATEWAY
------------------------
6.3.1 From the desktop
----------------------
If the gateway has been installed as an icon on the desktop, or in a
desktop folder, it is started by double clicking on the gateway icon.
6.3.2 From an OS/2 Prompt
-------------------------
To start the gateway from a command prompt do the following
1. Open an OS/2 command prompt
2. Use the CD command to change to the NetOp directory
3. Start the gateway by typing ngw2 ENTER.
6.3.3 Automatically at startup
------------------------------
The gateway can be started automatically at when the computer boots
in two different ways:
1. Install the gateway in the OS/2 startup folder. In the settings of
the NetOp gateway program object -L should be specified as
command line parameter.
2. Include the lines (provided that NetOp is installed in C:\NETOP,
otherwise substitute the appropriate directory):
CD \NETOP
START NGW2 -L
CD \
in the file STARTUP.CMD, placed in the root of the boot drive
6.3.4 Initialization
--------------------
If the gateway is started without command line parameters, the setup
dialog is displayed. From this dialog box, the various configuration
dialogs can be reached. All the dialogs will as default values contain
what was specified the last time the host was run. These settings are
stored in the file NHOST2.CFG.
After the OK button in the setup dialog is pressed the gateway will
minimize, and be ready to route NetOp sessions from external guest
PCs to the networked host PCs.
If the gateway is started with the -L parameter the setup screen will
be bypassed and the host will initialize directly after startup. The
gateway will use the last settings as the last time it was run.
6.4 CONFIGURATION
-----------------
If the gateway is started without command line parameters, the setup
dialog is displayed at startup.
The setup dialog can also be activated by choosing Setup... from the
gateway's configuration menu once it is initialized. In this case the
gateway will have to be restarted for the changed to take effect.
There are three main choices:
Line setup.
Press this button to configure the communication and
security setting for the external line (APPC, ISDN or modem). See
section 6.4.1, "Line Setup".
Host setup.
The gateway can also act as a host. Press this button to
configure the host part of the gateway. See section 6.4.2, "Host
Setup".
Network setup.
Press this button to configure the communication
settings for the network (IPX, NetBIOS or TCP/IP). See section 6.4.3
"Network setup".
6.4.1 Line Setup
----------------
When the Line setup button in the Gateway setup dialog is activated
a dialog is displayed.
Net number
Normally there is no need to change this setting (only neces-
sary when multiple NetOp gateways are connected to one
network). See section 6.6 for a discussion of net numbers.
Select protocol
Choose which communication protocol the gateway should
accept incoming external calls on.
Line Security
Activate this button to configure security settings for the
line. See section 6.5, "Security" for a description of gateway
security.
Protocol properties
See section 7, "Protocols" for a description of protocol spe-
cific settings.
Press OK to accept the settings in the dialog (or Cancel to reject).
Once the line setup is completed, the information is stored in the file
NHOST2.CFG. The next time the gateway is loaded the settings will
be suggested as defaults.
6.4.2 Host Setup
----------------
When the Host setup button in the Gateway setup dialog is activated
a dialog is displayed.
A NetOp gateway is also a host, which can be controlled both from
network PCs and from external PCs. The host setup dialog box is
used to configure the host part of the gateway.
The Host ID is the string which is used to identify the gateway PC to
guest PCs. This field is similar to the Host ID field in the NetOp Host
module.
Activate the Host Security... button to configure security for the host
part of the gateway. Please refer to 5.4, "Security" for a description of
this.
6.4.3 Network setup
-------------------
When the Network setup button in the Gateway setup dialog is acti-
vated a dialog is displayed.
Net number
Normally there is no need to change this setting (only neces-
sary when multiple NetOp gateways are connected to one
network). See section 6.6 for a discussion of net numbers.
Select protocol
This specifies which protocol is used for communication
between the gateway and the network hosts. If in doubt,
please refer to the system administrator
Protocol properties
In this section protocol specific options are specified. The
contents of the section varies according to the selection in
the Select protocol section. Please refer to section 7,
"Protocols" for a discussion of protocol specific settings.
Press OK to accept the settings in the dialog (or Cancel to reject).
Once the network setup is completed, the information is stored in the
file NHOST2.CFG. The next time the gateway is loaded the settings
will be suggested as defaults.
6.5 SECURITY
------------
The NetOp gateway contains advanced security features to prevent
against unauthorized access.
The security configuration of the gateway is divided into Line security
and Host security.
Line security must be passed in order to remote control any host on
the network through the gateway. In addition the individual host se-
curity settings are still active and must be passed as well. Thus Line
security can be viewed upon as a firewall, which protects the entire
network from unauthorized access.
Host security governs security for the host part of the gateway, both
for external guests calling through APPC, ISDN or serial/modem to
remote control the gateway, and for network guests which want to
control the gateway PC.
6.5.1 Line security
-------------------
The line security is accessed by activating the Line security... button in
the line setup dialog box.
Password
From a dialog box the user can specify a password which must be
entered on the guest whenever a connection attempt to the gateway is
made.
Password policy
Activate this button to specify how many password attempts a guest
has, and what to do if the limit is exceeded: Hangup, disable (do not
accept any calls), or boot the gateway.
Call-back
When call-back is enabled the gateway will do the following whenever
an incoming call occurs:
1. The gateway prompts the guest for the password.
2. If the password is entered correctly, the gateway hangs up and
makes a call to the guest, either to a predefined number or by
prompting the guest for a number.
See section 5.4.7, "Call-back" for detailed discussion of call-back.
6.5.2 Host security
-------------------
The host security is accessed by activating the Host security... button in
the host setup dialog box.
Configuring host security is described in detail in section 5.4,
"Security". The only difference from the normal host security, is that
the gateway's host security does not contain call-back, since this is
handled under line security.
6.5.3 Maintenance password
--------------------------
The gateway security settings can be protected by a maintenance
password (similar to the host maintenance password described in sec-
tion 5.4.1, "Maintenance Password").
The maintenance password is defined in the Host security configura-
tion dialog.
The user is prompted for the maintenance password both when con-
figuring host and line security.
6.6 NET NUMBERS
---------------
The Line setup and the Network setup both contain a Net number field.
Normally these fields need not be changed!
It is only necessary to alter the net numbers in a situation where there
are multiple gateway PCs on a single network. In this situation the
following rules apply:
1. The net number in the Network setup dialog must be the same on
all the gateways attached to the network, it must be different from
every Line setup net number.
2. The net number in the Line setup dialog must be unique on every
gateway, it must be different from the net number in the Network
setup dialog.
3. No net number can have the value 0 or 1 which are reserved values.
Other than that, the net numbers may be arbitrarily chosen.
Example
A network has three gateways attached to it. On all three gateways,
the net number in the Network setup dialog box is set to 101. The net
number in the Line setup is set to 102 on the first gateway, 103 on the
second and 104 on the third.
6.7 ON-LINE CHOICES
-------------------
The gateway has the same on-line choices as the host. Please refer to
section 5.5, "On-line Choices" for a description of these. Please note
that these choices only are relevant when the gateway is being re-
motely controlled, not when there is only pass-through sessions to
other hosts.
6.8 COMMAND LINE PARAMETERS
---------------------------
The gateway accepts the same command line parameters as the host
program, please refer to section 5.6, "Command Line Options" for a
description of these. The command line parameters refer to the host
part of the gateway (for instance the host password can be set from
the command line, but not the line password).
7. PROTOCOLS
------------
7.1 SERIAL/MODEM
----------------
7.1.1 Description
-----------------
Use the serial/modem protocol to communicate using the RS-232c
interface. Typically with a modem over telephone lines or with a null-
modem cable.
7.1.2 Configuration
-------------------
No special configuration is needed as long as OS/2's standard serial
device driver is loaded. In OS/2 1.3 the serial device driver is not
loaded in the default setup. To do this add the device driver
COM0n.SYS (COM01.SYS for PCs with ISA bus, COM02.SYS for PCs
with MCA bus) to the CONFIG.SYS.
7.1.3 Protocol Specific Settings
--------------------------------
Modem
Choose a modem from the list. If your modem is not in the list
choose Hayes compatible (2400 bps or slower) or Hayes com-
patible fast (9600 or faster).
It is also possible to define new modems. See section 4.3.4,
"Modem database" for a description of this.
Dial
Choose Tone if this is supported by the phone system, otherwise
choose pulse.
Port
Typically COM1 or COM2. Use the Custom field to enter other
COM ports (e.g. COM4 or any other valid OS/2 serial device)
Baud rate
Should normally be Default which means that NetOp will use the
speed defined for the chosen modem in the modem database.
If connection is often lost try lowering the baud rate.
Phone number
Enter `*' to use the host ID as the phone number. Use this field
to enter the phone number if the host ID is e.g. the name of the
host user.
7.1.4 How to Define New Modems
------------------------------
The most important part of defining a modem for NetOp is the setup
strings (SETUP1 and SETUP2). NetOp does not distinguish between
these two strings. You can just consider them as two lines for your
setup string.
You should use the following general approach when constructing
the setup string:
1. Load the modem's factory settings (usually AT&F).
2. Specify that if the DTR signal is lowered the modem should dis-
connect and return to command mode (usually AT&D2).
3. Specify that the CD signal should track the state of the carrier
(usually AT&C1).
4. Specify that the modem should use local echo (usually ATE1).
5. If the modem is capable of RTS/CTS flow control, this should be
enabled using the appropriate AT command. Also enable
RTS/CTS flow control in the settings section of the modem dialog
box.
6. Specify that the DTE/DCE rate should be fixed at the DTE speed.
7. If your modem is equipped with error correction and/or data
compression, these should be enabled.
8. Instruct the modem to hangup after loss of carrier (usually by set-
ting the modem's S10 register. E.g. ATS10=20, causing the mo-
dem to hangup if carrier is lost for a duration of 2 seconds).
The Dial string should usually be ATD?D. This instructs NetOp to
use ATDT if tone dial is chosen by the user, and ATDP if pulse dial is
chosen.
The Hangup string is usually ATH0S0=0. H0 tells the modem to go
on hook, S0=0 tells the modem not to answer incoming calls.
The Send field is send to the modem after setup1 and setup2, but
only by the guest. Usually this field should be left empty.
The answer field should usually contain the string ATS0=<number
of rings>, e.g. ATS0=1, this instructs the modem to answer incoming
calls after <number of rings> rings.
Set Max Baud Rate to the maximum DTE supported by your modem.
Please note that you should be careful with high baud rates on slow
computers. You might get better performance by setting the baud
rate to 19200 rather than 57600 on a slow PC.
Please note that you can override the baud rate defined for the mo-
dem in protocol specific settings for serial/modem.
7.1.5 Host ID format
--------------------
The guest user can enter the phone number directly as the host ID
(e.g. in the combo box). To get a pause in a phone number (e.g. to
access an external line), most modems will accept an comma (`,'). Ex-
ample: To get an external line the guest user must dial 0 and then
wait for new ready signal, he want to dial the number 112, in this case
he would enter "0,112" as the host ID.
It is also possible to enter another host ID than the phone number
(e.g. the name of the host user), in this case use the protocol specific
field Phone number to enter the phone number (otherwise this field
should contain `*').
7.2 NETBIOS
-----------
7.2.1 Description
-----------------
NetBIOS is one the most popular protocols for LAN communication.
NetBIOS is typically used in LAN Server, LAN Manager, LANTastic,
and Windows NT environments.
7.2.2 Configuration
-------------------
NetBIOS is installed when the network client software is installed on
the PC. If there are any problems with accessing NetBIOS, please
contact a network administrator
7.2.3 Protocol Specific Settings
--------------------------------
To initialise support for remote control of OS/2 and Windows Hosts via
NetBIOS, NetBIOS is selected rom the Host section. To initialise support for
backwards compatibility with RemPCs ver. 4.3, select RemPC NetBIOS as well.
This backwards compatibility is also used for remote control of DOS PCs.
In the guest and host it is possible to define whether to use Primary
or Alternate adapter. This is defined in the NetBIOS setup, the setting should
normally be Primary.
When initializing NetBIOS, NetOp will first try to initialize NetBIOS under
extended services. If this fails, it will try to initialize NetBIOS under
requester services. If you experience problems initializing NetBIOS
communications you can force Netop to only try to initialize a specific
service, ACSNETB or NETAPI. This is done via the DTL2.INI file.
NetOp will as default define 2 datagram threads. Under certain circumstances,
using 2 datagram threads might cause problems for NetOp. It is possible to
force NetOp to only use one. This is done via the DTL2.INI file.
DTL2.INI file
-------------
;NetBIOS protocol settings
[NETBIOS]
;Specify NETAPI or ACSNETB
Mode=
;Number of Datagram threads, default = 2
Rcv_DG_Threads=
7.2.4 Host ID format
--------------------
When configuring the host a Host ID can be entered. The host ID
should be a string with a maximum length of 32 characters.
If no Host ID is entered NetOp will use the burnt-in network adapter
address (typically the MAC address). To call a host which uses the
burnt-in address as a host ID enter 0xnnnnnnnnnnnn. Where
nnnnnnnnnnnn is a 12 digit hexadecimal number (e.g.
0x080005AF341A).
7.2.5 NetOp resource needs
--------------------------
Guest Guest with Host
RemPCNB
Sessions n n 1
NCBs n+4 n+8 5
Names 2 5 2
n is the number specified in the Max host sessions field in the guest's
Communication settings... dialog.
7.3 IPX
-------
7.3.1 Description
-----------------
IPX (Internetwork Packet Exchange) is Novell's network protocol.
This protocol is typically used in Novell Netware environments.
7.3.2 Configuration
-------------------
IPX is installed when the network client software is installed on the
PC. If there are any problems with accessing IPX, please contact a
network administrator.
7.3.3 Protocol Specific Settings
--------------------------------
To initialise support for remote control of OS/2 and Windows Hosts via
IPX, IPX is selected rom the Host section. To initialise support for
backwards compatibility with RemPCs ver. 4.3, select RemPC IPX as well.
This backwards compatibility is also used for remote control of DOS PCs.
In the Communication settings... dialog, which is accessed from the Op-
tions menu in the NetOp guest, there are some IPX specific settings.
Normally the NetOp Guest will look for hosts on the same network as
itself. However some Novell networks consist of a number of subnet-
works, each identified with an 8 digit hexadecimal number. To reach
a host on another subnetwork than the guest, the host's network
number has to be defined in the guest's list of IPX networks.
There is a check button labelled Auto bridge support. When this option
is enabled the NetOp Guest will build an internal list of all known
IPX network numbers.
There is also a List button. This button lets the guest user manually
define a list of IPX network numbers.
To find the network number for a given PC, use Novell's NLIST util-
ity by issuing the following command at an OS/2 prompt:
nlist user=NetwareLoginName /a ENTER
Where NetwareLoginName should be substituted with the user's Net-
ware login name. The Address field of the resulting listing contains the
network number.
The network numbers in the NetOp guest's list must be 8 digits. if a
network number has less than 8 digits is should be padded with 0s.
Example: network number 1F23 should be entered as 00001F23 in
NetOp's network list.
Auto bridge support and the list feature are also available in the gateway
module and the in the host module. On the gateway, the purpose is to permit
access to other network segments. On the host, the purpose is to permit
Request Help access to Help providers located on other network segments.
If it is not possible to connect to a host PC, you can try to modify the size
of the data packages that NetOp sends. You do this by creating a file called
DTL2.INI and place this file in your NetOp directory. Below is an example of
how this file can look. The line MAX_PACKET_SIZE= determines the size of the
packet.
Sample of DTL2.INI file:
;IPX protocol settings
[IPX]
;Max packet size to use on IPX
MAX_PACKET_SIZE=512
7.3.4 Host ID format
--------------------
When configuring the host a Host ID can be entered. The host ID
should be a string with a maximum length of 32 characters.
If no Host ID is entered NetOp will use the burnt-in network adapter
address (typically the MAC address). To call a host which uses the
burnt-in address as a host ID enter 0xnnnnnnnnnnnn. Where
nnnnnnnnnnnn is a 12 digit hexadecimal number (e.g.
0x080005AF341A).
7.3.5 NetOp resource needs
--------------------------
NetOp uses IPX socket 8641 (hex) when connecting to hosts. For connnection to
RemPCIPX, NetOp uses socket 8186 and 8187 (hex). The sockets are allocated to
Danware by Novell.
7.4 TCP/IP
----------
7.4.1 Description
-----------------
TCP/IP is a networking protocol increasingly popular in LAN/WAN
environments. NetOp supports IBM's and FTP's implementation of
the TCP/IP protocol for OS/2.
7.4.2 Protocol Specific Settings
--------------------------------
If FTP's TCP/IP implementation is used it is necessary to enter the
local IP address on the guest and host. On the guest this is done in
the Communication settings dialog, on the host in the Host configuration
dialog.
Enter the IP address in dotted-decimal notation (e.g. 208.0.0.1).
If it is not possible to connect please verify that you can connect using the
PING program. If PING works, you can try to modify the size of the data
packages that NetOp sends. You do this by creating a file called DTL2.INI and
place this file in your NetOp directory. Below is an example of how this file
can look. The line MAX_PACKET_SIXE= determines the size of the packet.
Sample of DTL2.INI file:
;TCP/IP protocol settings
[TCPIP]
;Max packet size to use on TCP/IP
MAX_PACKET_SIZE=1024
7.4.3 Host ID format
--------------------
From the guest a host can be called by entering the IP address in
dotted-decimal notation (e.g. 208.0.0.1). If a name is entered, this
will be passed on to TCP/IP. If the name can be resolved to an IP ad-
dress where a host is loaded then the connection will be successful.
Thus a host ID could be e.g. `peter' or `peter.sales.danware.com'.
7.4.4 NetOp resource needs
--------------------------
NetOp uses one port. The default port used is 6502. To use another
port instead of 6502 (e.g. to avoid a conflict with another TCP/IP
application) include a line in TCP/IP SERVICES file on all guests and
hosts. Example: To use port 6503 instead of 6502 enter the following
line in the SERVICES file:
netop 6503/udp
netop and udp must be in the line. The port number can be
changed. However all NetOp PCs must use the same port number.
7.5 APPC
--------
7.5.1 Description
-----------------
APPC (Advanced Program to Program Communication) is a com-
munication protocol, which is typically used to communicate in IBM
WAN environments (SNA networks).
7.5.2 Protocol Specific Settings
--------------------------------
Mode refers to transmission mode, as defined in the Communication
Manager/2 setup. Normally this should be the IBM pre-defined mode
#INTER. Please refer to your system administrator for information
about modes if #INTER is not available.
7.5.3 Configuration
-------------------
APPC is installed and configured by using the Communication Man-
ager/2 setup utility.
In order to use NetOp over APPC two Transaction Programs (TPs)
must be defined in the CM/2 setup. The TPs must have the following
names:
DWDTL1
DWDTL2
In the setup of these TPs Service TP must be disabled, Operation Type
should be defined as `Queued operator preloaded'. Please note that
the names (DWDTL1, DWDTL2) must be in uppper case.
7.5.4 Host ID format
--------------------
When calling an APPC host, the guest should use either the fully
qualified LU name, or an LU alias as the host ID. Both of these are
defined in the APPC setup. For further information please refer to
your CM/2 documentation.
It is also possible to enter another host ID than the LU (e.g. the name
of the host user), in this case use the protocol specific field LU Name
or Alias to enter the host LU (otherwise this field should contain `*').
7.6 ISDN / CAPI
---------------
7.6.1 Description
-----------------
NetOp for OS/2 supports ISDN using Capi version 1.1, profil A (ie.
works with EuroISDN DSS1, GermanISDN 1TR6, French ISDN VN2,
Belgian ISDN CT1, ..) interface. NetOp for OS/2 will also work with
Capi version 2.0 which is backward compatible with Capi 1.1.
NetOp for OS/2 supports features such as short-hold mode, A-
number check and channel-bundling.
7.6.2 Configuration
-------------------
ISDN Capi must be loaded before you try to access it from the guest,
host or the gateway. If you cannot access ISDN Capi from NetOp,
please verify that a supported version is installed and loaded. Please
notice that the Capi dll should be a 16 bit version.
7.6.3 Protocol Specific Settings
--------------------------------
Table 7-3 contains a description of the properties settings specific to
the ISDN Capi protocol when configuring the host program.
Local Number
Enter the local number (EAZ) as defined in your Capi setup.
Short-hold mode
Select this to permit the use of short-hold mode. When no data
is transferred between the guest and host, the line will be dis-
connected. When activity starts on either the guest or the host,
the connection will be re-established.
Use of 2 B-channels
Select this to permit the guest to use 2 B-channels.
Enable Guest ISDN-Number check
If enabled, only those guests that has an ISDN number match-
ing a number in this list will be able to access this host.
Properties settings specific to the ISDN Capi protocol when configuring
the guest program:
Short-hold mode
Enable to use short-hold mode. Enter the number of seconds to
wait before disconnecting the line.
Local number
If short-hold mode is enabled please also enter local number
(EAZ) as defined in the Capi setup.
2 B-Channels
Select this if you want to use 2 B-channels.
7.6.4 Host ID format
--------------------
The guest user can enter the ISDN number directly as the host ID
(e.g. in the combo box).
It is also possible to enter another host ID than the ISDN number
(e.g. the name of the host user), in this case use the protocol specific
field Phone number to enter the ISDN number (otherwise this field
should contain `*').
8. TROUBLE-SHOOTING
-------------------
8.1 THE NATURE OF REMOTE CONTROL
--------------------------------
Remote control require a program to interact closely with the operat-
ing system in order to pick up screen information and deliver key-
board and mouse input. All has to be done so the PC, the operating
system and the program(s) running are affected as little as possible.
Danware strive to be able to remote control all PCs and all applica-
tions running operating systems supported by NetOp. However, we
cannot guarantee that NetOp will remote control all existing and fu-
ture PCs and applications.
Should you run into problems with a specific PC or application, for
example that you can only view, not control the keyboard, we will
appreciate hearing from you. We are very interested in investigating
such problems in order to come up with a solution either immediately
as a fix, or as part of a future release.
8.2 ANSWER TO COMMON PROBLEMS
-----------------------------
? Cannot connect to a host via IPX
! If the host is on another IPX network than the guest, the host's
network number should be defined in the guest's IPX network list.
Refer to section 7.3.3, "Protocol Specific Settings" for a descrip-
tion of how to do this.
? I get the error "DTL2.DLL already used. Guest to Host com-
munication not possible".
! You are probably trying to run the host and the guest simultane-
ously, only one of the programs should run on the same PC simul-
taneously
? The host window only displays "Unsupported video mode"
when controlling Windows (RemPC 4.3)
! When controlling 4.30 Windows RemPCs NetOp supports up to
800x600x16. If you are running a higher resolution, use the NetOp
for Windows host program instead.
? I cannot get a connection between my modems.
! For some modems the error correction and data compression are
not compatible. Try disabling these two features of the modems
(by changing your modem setup strings).
? I cannot control the keyboard on the OS/2 host PC
! If it is a PC running Warp, you can try to add the parameter /D to the
NHOST2.SYS device driver in the config.sys file on the host.
8.3 NETOP ERROR MESSAGES
------------------------
NetOp error messages include a brief description of the error and a
More... button. When reporting an error to a NetOp support person,
make sure to give all information contained in the error dialog and
also all information in the More... dialog.
Also have the following information ready:
1. Your NetOp serial number
2. OS/2 version information (for guest and host)
3. Relevant information about your communication hardware and
software (modems, network client software version, etc.)