remoteware windows 3.x client user⁍꥔㈡猺팃듃=쨘 · pdf fileavailable in all countries...

RemoteWareWindows 3.x Client

U s e r ’ s G u i d e

V e r s i o n 4 . 1 S e r v i c e P a c k 1 A

RemoteWare Windows 3.x Client User’s GuideVersion 4.1 Service Pack 1A

This document was prepared to assist licensed users of RemoteWare by XcelleNet, Inc.; its contents may not be used for any other purpose without prior written permission. The material contained herein is supplied without representation or warranty of any kind and is based on typical use. Any unusual use may produce unpredictable results. XCELLENET ASSUMES NO RESPONSIBILITY AND SHALL HAVE NO LIABILITY OF ANY KIND ARISING FROM THE SUPPLY OR USE OF THIS DOCUMENT OR THE MATERIAL CONTAINED HEREIN. Companies, names, information, and data used in examples herein are fictitious unless otherwise noted. The information in this document is furnished for informational use only and is subject to change without notice.

References in this manual to XcelleNet products, programs, or services do not imply that XcelleNet intends to make these available in all countries in which XcelleNet operates.

Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 52.227-19.

© 1997-2003 XcelleNet, Inc. All Rights Reserved.

All rights reserved, including the right to reproduce this document or any portion thereof in any form.

Printed in the United States of America.

RemoteWare is a trademark of XcelleNet, Inc.

Other product and company names mentioned herein may be the brand names, trade names, trademarks or registered trade-marks of their respective orders.

Contents

USING THIS GUIDE

About this guide ................................................................................................................. vUse Adobe Acrobat to view guide online .......................................................................... vUsing RemoteWare online Help ...................................................................................... vi

What’s in this guide .......................................................................................................... vii

CHAPTER 1: INSTALLING THE CLIENT SOFTWARE

Client Requirements........................................................................................................ 10

Installing the RemoteWare Client................................................................................... 10

Configuring the template Client ..................................................................................... 13

Configuring the communication settings ........................................................................ 16

Using asynchronous (ASYNC) settings ....................................................................... 16

Using the Auto Detect option ..................................................................................... 17

Using NetBIOS settings .............................................................................................. 18

Using SPX settings ....................................................................................................... 19

Using TCP/IP settings ................................................................................................. 20

Completing setup ............................................................................................................. 21

CHAPTER 2: USING THE CLIENT

Understanding the fundamentals .................................................................................... 24

Starting Client Communications ..................................................................................... 25

Understanding the features of the Client Communications window ............................ 26

Using the main window ............................................................................................... 26

Using the menus and buttons...................................................................................... 26

Using the status bar ..................................................................................................... 28

Connecting with the Server ............................................................................................. 30

Connecting using another Dialing Directory entry.................................................... 30

Using the Dialing Directory ............................................................................................ 31

Connecting using the Directory .................................................................................. 31

Setting a default entry.................................................................................................. 32

Creating new entries.................................................................................................... 32

Modifying a Directory Entry ....................................................................................... 33

Defining Dial Scripts ................................................................................................... 44

iv R e m o t e Wa re W i nd o ws 3 . x C l i e n t U se r ’s G u id e

Modifying Client Setup.................................................................................................... 52

Changing the password................................................................................................ 52

Using Schedules ............................................................................................................... 53

Deactivating the schedule ........................................................................................... 54

Using the Communications Log...................................................................................... 55

Viewing Alerts .................................................................................................................. 58

Resource Error ............................................................................................................ 58

ESD Arrived ................................................................................................................ 58

AA Disabled ................................................................................................................. 59

ESD Disabled .............................................................................................................. 59

Reinitializing the modem................................................................................................. 60

Unloading the Client........................................................................................................ 60

Selecting Client preferences............................................................................................ 60

Using the Modem Monitor .............................................................................................. 61

Using the Modem Monitor status lights ..................................................................... 61

Using the Modem Monitor user interface.................................................................. 62

Exiting Client Communications ...................................................................................... 64

Using WinAuto Auto Communications........................................................................... 64

Placing Auto Communications on the desktop........................................................... 64

Command Line options ............................................................................................... 65

Starting Auto Communications ................................................................................... 66

Exiting Auto Communications .................................................................................... 67

APPENDIX A: UNDERSTANDING THE CLIENT DIRECTORY STRUCTURE

Installation details ............................................................................................................ 70

Files and directory changes ............................................................................................. 70

The WINESD directory .............................................................................................. 71

INDEX........................................................................................................................................ 73

Chapter X: Chapter Title <-- Apply “chapter hidden” style

Using This GuideThis guide introduces you to RemoteWare Windows 3.x Client, one of the client-side components of RemoteWare, a remote systems management tool specifically designed to distribute software to and perform inventory scans for remote and fixed-site users. It contains fundamental information necessary to use the software, including a conceptual overview and highly interactive walkthroughs.

About this guide

We recommend you print this guide so it is readily available as you perform your tasks. If you prefer to use this guide online, you may find it helpful to zoom to 150% for enhanced readability.

Printing this manual

From Acrobat Reader, you can print the entire guide or a range of pages.

To print the guide:

1 On the File menu, click Print.

2 Select the printer and number of copies, and click OK.

Use Adobe Acrobat to view guide online

Use Adobe Acrobat Reader’s hyperlinks and Find features to easily access information in this guide.

Hyperlinks

Hyperlinks take you directly to a topic or page. Hyperlinks are included for the following:

• Table of Contents and Index

• Topics at the beginning of each chapter

• Cross references

To use hyperlinks:

1 Click the Hand tool on the Acrobat Reader toolbar. The pointer changes to a

hand.

2 Place the hand symbol over the topic/page number you want to view and click. Acrobat Reader takes you to the page you selected.

vi R e m o t e Wa re W i nd o ws 3 . x C l i e n t U se r ’s G u id e

Find feature

You can use Find to search for text in any document you have open.

To search for text:

1 On the toolbar, click Find.

2 Enter the term(s) you want to find in the Find What field. Click Cancel to close.

3 To narrow your search:

• Match Whole Word Only to search for the exact term only.

• Match Case to do a case-sensitive search.

• Find Backwards to move backwards instead of forwards through the document.

4 Click Find to begin your search.

To continue to search for other instances of a term, select Edit and Find Again. In the Find dialog box, the original term displays in the Find What field. Click Find Again. Repeat this process until you have found the section you want to view.

Using RemoteWare online Help

RemoteWare online Help provides explanations of features and steps for how to complete tasks.

To access RemoteWare online Help:

On the application’s Help menu, click Topics (or Help Topics), or press F1.

Us i ng Th i s G u i d e v i i

What’s in this guide

This guide includes the following chapters.

Table 1. Chapters

Chapter Title Description

Chapter 1 Installing the Client software Describes the steps for installing and configuring the RemoteWare Client on your computer.

Chapter 2 Using the Client Describes the various Client applications, their features, functions, and windows, and explains how to use these application to communicate with a RemoteWare Server.

Appendix A Understanding the Client Directory Structure

Provides file system information for directories on the Client computer.

viii R e mo t eWar e W in d o ws 3 .x C l i e n t U s e r ’s G u i de

C H A P T E R

1


1 Installing the Client software

The RemoteWare Client includes an installation program for transferring the Client

software and configuring usage and connection settings.

This chapter includes:

• System and software requirements necessary to install and use RemoteWare Client

• Install the Windows 3.x Client on a computer

• Configure a template Client

• Configure settings used by the Client to communicate with RemoteWare Server

10 R em o t e Wa r e W i n do w s 3 . x C l i en t U se r ’s G u i de

� Client Requirements

To install and use the RemoteWare Windows 3.x Client, you need the following:

• A 386 or higher PC with Microsoft system requirements for running Windows 3.x.

• A hard drive with a minimum of 8 MB free space and one 3.5" disk drive.

• A minimum of 16 MB memory (RAM).

� See the section “Configuring the communication settings” for a discussion about connection types and their setup.

• Microsoft Windows 3.x.

• One or more of the following communications types: Asynchronous, NetBIOS, IPX/SPX, TCP/IP.

• One available serial port (COM1 - COM4).

• One or more disks containing the Client installation kit. These disks are provided by your Server Administrator.

� Installing the RemoteWare Client

The Server Administrator uses the RemoteWare Server to define the components of the network and creates installation disks for each Client on the system. Your Server Administrator then provides you with the Client installation disk for your computer.

To install the Client software, use the Setup program on the first disk of the Client installation kit. Note that the optional steps in this section refer to template Client installations, and may not be relevant to your installation.

To install the software:

1 Insert the first disk of the Client installation kit in the floppy drive.

2 Launch setup.exe from the disk.

• From the Windows Program Manager, choose File then�Run.

• Type a:\setup.exe in the Command Line field, or use the Browse button to locate the setup program.

• Click OK to start the setup program.

C H A PT ER 1 / I n s t a l l i n g t h e C l i en t s o f tw a r e 11

3 Select the drive letter for the Client files and click Continue.

4 You will see a dialog box asking you to decide whether to add the Client software to the Windows Startup group. Click one of the following buttons:

• Yes. Places the WinXnode communications program in the Startup group. This program runs whenever Windows starts and allows the Server to access the Client. Choosing Yes does not automatically display the Client user interface.

• No. The Client user must manually launch the WinXnode communications program or the Client Communications user interface.

5 You will see a dialog box asking you to choose whether to automatically or manually update the autoexec.bat file. Click one of the following buttons:

• Yes. Setup adds the commands necessary to copy software updates from the updates directory to the \nodesys Client directory each time the computer reboots.

• No. Make no changes to the file. To apply Client software updates manually, you should add these lines to the autoexec.bat file or perform equivalent actions:REM ========== RemoteWare Client Commands BEGIN ==========

x:

CD \nodesys

� Change the x: in this example to the drive letter for the Client software.

IF EXIST \nodesys\updates\*.exe COPY \nodesys\updates\*.exe \nodesys

>NUL

IF EXIST \nodesys\updates\*.dll COPY \nodesys\updates\*.dll \nodesys

>NUL

IF EXIST \nodesys\updates\*.exe DEL \nodesys\updates\*.exe >NUL

IF EXIST \nodesys\updates\*.dll DEL \nodesys\updates\*.dll >NUL

REM =========== RemoteWare Client Commands END ===========

Note: The RemoteWare Client should be installed on a local drive. XcelleNet does not support running the Client from a network drive.


If the Client uses DOS 6.2, you must disable the “Confirm when copying files” function. Doing so allows Client file transfers to proceed. Add this line to the autoexec.bat file: set copycmd=/y

Windows 3.x computers also require the \nodesys directory in the path statement.

Setup has completed installing the Client on the computer. Continue to the next sections to configure the communication resources and set up the template Client (if applicable).


� Configuring the template Client

The Server Administrator may have provided you with a set of installation disks containing a template Client. A template Client allows your Administrator to easily configure large quantities of Clients and allows you to adjust specific settings during installation. The template Client becomes a regular Client once installation is complete.

Many of the windows in this section appear only if the Server Administrator has configured this feature. If you do not encounter one of the windows shown below, please skip to the next section, “Configuring the Communications Settings.”

1 After the welcome window, you will see a general information window:

Complete the following fields:

• Location or Description. Type up to 22 characters. The description tells the Server Administrator the location or function of this Client.

• Client Password. Enter up to 10 characters for a password.

• Client Name. (This option may not be present.) Type your Client name as given to you by the Server Administrator. An incorrect Client name will cause the Client registration to fail.

Click Next to continue.


2 Enter your registration information. The Server uses this information to authenticate your Client.

• Server Serial Number. Enter the number provided by your Server administrator.

• Registration Key. Enter the registration key provided by your Server administrator.


3 Provide the technical contact information for this Client. Only the Contact Name and Phone # are required; other fields are optional. This information may be used by the Server Administrator for reference; it is not used by the Server.

Note: This window or some of its options may not appear, depending upon your setup.


Provide the following information:

• Contact. Provide a name or department that can assist with the Client.

• Phone #. Enter a voice phone for the contact listed above.

• Address. Use these two text boxes to enter an address. This may be the address where the Client resides, or may be the address for the contact or Client user.

• City, State. Enter the city name and state (or other geographical designation).

• Zip. Enter the postal code for the mailing address.


The template Client information is complete. The Client transmits these values to the Server later in the installation process. The registration session is described in “Completing setup” later in this chapter.

Note: A template Client is not registered at the Server until a successful communications session occurs and the Server Administrator verifies the new Client. An unregistered Client cannot perform any data or file transfer functions other than the registration function.


� Configuring the communication settings

The RemoteWare Setup Wizard displays one or more windows to assist you in configuring communication and setup parameters. The Client’s resource definitions govern the number and ordering of the windows.

Using asynchronous (ASYNC) settings

If your Client is configured to use the asynchronous protocol, verify and adjust the following settings:

Complete the following information

• Server Phone. Displays the number your Client uses to contact the Server. It may be blank if the Server Administrator intends to always place outbound calls to the Client. Verify this number, and add any calling prefixes, area or country codes necessary to contact the Server.

� For a Direct Connect asynchronous connection, the Max Data Rate setting for the Server’s asynchronous resource must match the Data Rate of the Asynchronous resource defined for the Client.

• Modem Type. Displays the brand or label for modems that have been predefined at the Server. If the visible choice is not correct, scan the list for a better choice. Contact your Server Administrator if you cannot determine which choice is appropriate.

• Port. Lists the hardware serial port for the modem. Choices may be from COM1 to COM4. If you are not certain of this value, see the “Auto Detect option” later in this section.

• Data Rate. Displays the modem’s transfer speed in bits per second (bps). Change the value from 1200 to 57600 bps if it is not correct. If you are not certain of the correct data rate, see the “Auto Detect option” later in this section.


• Client Phone. The Server uses this number to contact the Client. It may be blank if the Server Administrator always intends for the Client to place an inbound call to the Server, as in the case of a mobile Client. Otherwise, verify that the number is correct, and include the area or country codes if the Server is not a local call.

Using the Auto Detect option

Setup includes a feature to assess what serial ports are available on the Client and whether a modem is connected and available. Auto Detect then determines the modem’s maximum data rate, and presents you with a list of results. Choose from the results to set the Port and Data Rate values.

Click Auto Detect to invoke this process.

Once you have verified that the modem is powered on and connected to the serial port,

click Continue.

Auto Detect searches for communication ports, and then for modems on the ports.

Each available port appears as a separate line with the following information:

• Direct Connect. Auto Detect found a serial port, but was not able to detect any modems. This port could be used as a direct connect Client, where the Client


connects to the Server via a null modem serial cable. However, this is impractical unless the Client is in close proximity to the Server.

• Modem at nnnnn bps. The serial port possesses an active modem capable of the data rate displayed.

Select a choice and click OK to set the Port and Data Rate. Click Cancel to end Auto Detect and leave the settings as they were.

When you are finished adjusting the async settings for your Client, click Next to continue.

Using NetBIOS settings

If your Client is configured to use the NetBIOS network protocol, verify and adjust the NetBIOS address:

Server NetBIOS Address. Displays the NetBIOS address that the Client uses to contact the Server. This value is one of the Server Names.

Note that the Client NetBIOS address is always the name of the Client.


Note: If all your choices indicate direct connect and a modem is connected to the system, verify the following and rerun Auto Detect: the modem is on or plugged in, it is connected to the serial (not parallel) port, the cable is functioning properly, appropriate software drivers are available for internal or PC Card modems, and other programs are not currently allocating or accessing the modem or serial port. You can use a standard terminal program (such as Windows Terminal) to troubleshoot several of the items above.

Note: Setup automatically adjusts a data rate that exceeds the maximum data rate for the current modem type.


Using SPX settings

If your Client is configured to use the SPX network protocol, verify and adjust the following SPX settings:

• Server SPX Address. The Client uses this value to connect with the Server during an inbound call. The Server Administrator provides this SPX address to the Server computer. The field may be blank if the Server Administrator always plans to initiate an outbound call from the Server to the Client.

• Client SPX Address. This value is the SPX address the Server uses to contact the Client during an outbound call.


Note: The message Resource Not Installed appears in the Client SPX Address field if this computer does not have SPX network software available or active.


Using TCP/IP settings

If your Client is set up to use the TCP/IP network protocol, verify and adjust the following values if necessary:

• Server TCP/IP Address. Defines the address used by the Client to contact the Server. This field may be blank if the Server always initiates an outbound connection to the Client.

• Client TCP/IP Address. Defines the TCP/IP address the Server uses to contact the Client during an outbound session.


Note: The message Resource Not Installed appears in the Client TCP/IP Address field if this computer does not have TCP/IP network software available or active.


� Completing setup

The Client software is installed and is ready for communication sessions with the RemoteWare Server. Non-template Client installations are complete at this point.

If you have a template Client, you have the option to perform the registration connection, or you may defer the connection until a later time.

To register the template Client:

1 Click Yes when Setup asks if you want to establish a connection with the RemoteWare Server.

2 Choose which resource, phone number, or network address to use and click Connect. The registration process attempts to connect to the Server.


Setup displays a message if registration is successful. The Client can now communicate with the Server as a regular Client, and installation is complete.

If the registration is unsuccessful, you can retry the session now or wait until later. You do not need to rerun installation to register at a later time; you can launch registration from the Client Registration icon in the RemoteWare program group.

C H A P T E R

2


2 Using the Client

The RemoteWare Client contains a suite of applications that allow the computer to

exchange files, messages, and information with a central RemoteWare Server. This

chapter includes:

• RemoteWare Client fundamentals

• Start Client communications

• RemoteWare Client features and controls

• Set up communications with or without the user interface

• Use Client user interface to set up, monitor, and control communications

• Use WinAuto Auto Communications application for simplified or preconfigured operation


� Understanding the fundamentals

Although the Client is a computer with the ability to exchange information with a RemoteWare Server using a variety of asynchronous or network resources, it also refers to a set of applications that make this possible. Table 1 lists the main Client applications.

Table 2. Client applications

Program nameCommon name

Description

NodeComm.EXEClient Communications

This application is the user interface you can use to set up, control, or monitor communications with the Server. Client Communications depends on WinXNode (described below) for access to communication resources. NodeComm does not need to be active for communication to occur with the Server.

WinXNode.EXECommunications engine

Enables the Client to communicate with the Server. This application has no user interface. The program may be set up to activate when Windows starts. WinXNode is automatically loaded when the Client Communications application starts.

NodeReg.EXEClient Registration

Unregistered template Clients have this application in the RemoteWare program group. It allows the Client to register without re-running the Setup installation program. This application is no longer needed after a successful template Client registration.

WinAuto.EXEAuto Communications

This application allows the Client to initiate an unattended inbound session with the Server using predefined settings. WinAuto is useful for Clients that must operate with little or no operator intervention, or for systems that want to start the connection from a batch file, command line, or other application.

RWNWMMUI.EXEModem Monitor UI

Use the Modem Monitor user interface to view the Client commands and modem responses. Use this interface to troubleshoot an asynchronous connection. Modem Monitor is available as a standalone application or from the Command / Modem Monitor menu in Client Communications.

RWNWMMST.EXEModem MonitorStatus Lights

The status lights display the current modem condition. This is useful when troubleshooting, or when you cannot directly determine the modem’s operating status (for example with an internal modem).

C H A PTE R 2 / U s in g t he C l i en t 25

� Starting Client Communications

You can start Client Communications by double-clicking its icon, or you can run the Client automatically each time you start the computer. The following table lists the various methods for starting the Client.

After the Client user interface appears, it starts the WinXNode program. WinXNode is a program that runs independent of Client Communications and manages communications with the Server.

The Client Communications application provides communication capabilities under all Windows environments. It allows you to initiate a connection to the Server, schedule a communications session, view the Communications Log, edit the Client’s setup, and more.

In addition, the Dialing Directory lets you save up to forty additional phone numbers, network addresses, or special connection procedures. You can select one of the entries as your default connection.

Table 3. Starting the Client

To Do this

Start the Client from its icon Double-click the Client Communications icon in the RemoteWare program group.

Start the Client each time Windows starts

For a user interface, place a copy of the Client Communications icon (the NodeComm.exe program) in the Startup folder. For no user interface, place a copy of WinXnode (the WinXnode.exe program) in the Startup folder.

Start the Client from the command line

Windows cannot be currently running when you use this option. Type win nodecomm at the DOS command line. The \nodesys directory must be in your path for this command to work.


� Understanding the features of the Client

Communications window

This section provides an overview of the major components in the Client Communications window, such as menus, buttons, and the status bar.

Using the main window

Starting Client Communications displays a window containing the menus, buttons, and current Client status.

Using the menus and buttons

The menu bar contains every Client function and command. The buttons at the top of the window are available for quick access to commonly used commands. You can also access every button function from the menus. Move the mouse over a button to obtain a short description in the lower-left corner of the window.

The menu bar topics and buttons are always available from the mouse or keyboard. To access them from the keyboard, press the [Alt] key and the underlined letter for that menu topic.

Table 3 lists the button and menu commands and gives a brief description of each.

Table 4. Client Communications menu commands and toolbar buttons

Menu Command Button Description

File Setup Displays the connection parameters currently being used by the Client. Client password may also be changed from this command.


Schedule Starts the Schedule Connection window, which allows the Client to start, modify, or stop and inbound call to the Server at a specific time each day.

View Log Displays the communications Log.

Dialing Directory Shows the current Dialing Directory, and allows the Client to add, modify, or delete entries, settings, tasks, and dial scripts.

Exit Closes the Client Communications window. Also stops the WinXNode application if the Client started the program and the Client is not currently connected to the Server.

Command Connect Initiates an inbound connection to the Server. This command toggles with the Cancel command.

Cancel Aborts a connection in progress. This command toggles with the Connect command.

Reinitialize Transmits the reinitialization commands to the modem or network device. Not available when a connection is in progress.

View Alerts Displays more information about any errors or events. The alerts also appear as icons in the right bottom section of the status bar. See Table XXXX for a list of alert icons and their functions.

Unload Client Removes the WinXNode program from memory. Client Communications cannot transmit or receive until this program is successfully running.

Load Client Starts the WinXNode program. Client Communications requires this program to successfully communicate.

Table 4. Client Communications menu commands and toolbar buttons (continued)



Using the status bar

The status bar at the bottom of the Client Communications window provides information about your current resources and status.

The status bar is split into four sections, each containing specific information:

• Default Directory. The top left section displays the connection method used when the Client connects.

• Help overview. The bottom left section continuously provides a brief description of each item as you move the cursor over a button or menu item.

Options Set Client preferences by toggling these choices:Save Last Position. Places the window in the same place as it was when the application last ended.Use default size. Opens the window in the standard size. Can also be used to reset the dimensions when the windows is already open.Float to top. The Client Communications window is always the topmost window.

Modem monitor Only available for asynchronous resources. Starts the Modem Monitor UI and Status Lights. Allows you to view the commands sent to the modem and modem responses. Use this command to troubleshoot the Client software and hardware.

Help Help Index Displays the list of Help topics for the Client Communications.

Using Help Displays general information about using Windows Help.

About Client Communications

Displays the About box, which lists the application name, version, manufacturer, and copyrights.

Table 4. Client Communications menu commands and toolbar buttons (continued)



• Current resource. The top right section shows which communications resource is currently loaded.

• Alert icons. The bottom right section displays the alert icons to indicate an event significant to the Client environment. Click one or more of the icons, described in the following table, to obtain specific information on the alert.

Table 5. Alerts

Alert icon Alert name Description

Resource Error

The Client has detected a problem with the current resource. The Transport Error window explains what has happened.

ESD Arrived New files exist in the updates directory. See Appendix A for more information.

AA Disabled The modem’s Auto Answer feature has been turned off by the Client user. The Server cannot place outbound calls to the Client until Auto Answer is enabled. This feature may be disabled for inbound only Clients, or when the Client might inadvertently answer an incoming voice call on the same phone line.

ESD Disabled

The Client cannot receive updated applications because the Client has disabled Electronic Software Distribution. This option is useful when the Client user may not have time for a lengthy download.


� Connecting with the Server

To call the Server from the Client, select Connect on the Command menu or click the Connect button. This action starts an inbound connection to the Server using the default Dialing Directory entry. A bar between the representation of the Client and the Server shows that a connection is being attempted.

To cancel the dialing, select Cancel Connection on the Command menu or click the Cancel button.

Once a connection is made, the window displays the activity between the Server and the Client above and below the bar. File transfers display a progress indicator to show how much data has been exchanged and the direction of the file transfer.

Connecting using another Dialing Directory entry

The Connect command uses the default setting in the Dialing Directory listing. You may want to temporarily use another entry for this connection without changing the default setting.

To connect using another setting, right mouse-click the Connect button. The Connect menu appears.

From the Connect menu, select the resource description you wish to use. The Client initializes the resource and initiates the connection.


� Using the Dialing Directory

The Client Dialing Directory allows you to customize the connection options available to connect to the Server. You can edit phone numbers and network addresses, set protocol parameters, define which tasks to complete, and disable ESD and Auto Answer

To display the Dialing Directory, on the File menu select Dialing Directory or click the Directory button. The Dialing Directory window displays the Default Entry, followed by a list box containing available resources and settings.

Descriptions followed by an asterisk “*” are those defined by the Server Administrator. Administrator-defined entries cannot be deleted or modified, but they can be copied and then modified.

Connecting using the Directory

To initiate an inbound connection using one of the entries in the directory, highlight the desired entry and click the Connect button.

From the main window, you can also right mouse-click the Connect button and choose the entry to use to start a connection with that entry. See “Connect using another dialing directory entry” in the previous section for details.


Setting a default entry

The Client uses the default entry settings whenever the Connect command is executed. To set a default from the Dialing Directory window, highlight the entry to use as the default and select Set Default on the Command menu.

You can also set a default entry from the main communications window by right mouse-clicking the Directory button. The Set Default menu allows you to select which default entry to use for a connection.

Creating new entries

To create a new Dialing Directory entry:

1 Choose an existing description that most closely matches the entry you want to create. If you are not certain which entry this is, then choose an entry that uses the same communications transport (such as an SPX entry for a new SPX definition).

2 On the File menu, select Copy. A new entry with identical settings appears in the Modify Dialing Directory Entry window. The only difference is the description field.

3 Adjust the settings in the Modify Dialing Directory Entry window. See the following sections for information on this window, its property pages, and their settings.

4 When you are finished, click OK to create and save the new entry, or click Cancel to discard the entry and return to the Dialing Directory.


Modifying a Directory Entry

Use the Modify Dialing Directory Entry window to change an item to meet your connection needs. You can change any entry that is not an Administrator-defined entry (designated with an asterisk “*” after the description name).

The property pages common to all resources are discussed in the sections that follow.

Using the General property page

The General property page is the first property page in the Modify Dialing Directory Entry window. Use this property page to change the entry’s name, connecting Server, resource type, phone or address, and connection parameters. All the options on this property page are available to every resource type.

Modify one or more of these options to fit your needs:

• Description. Enter up to 50 characters describing the resource. The Client places entries in alphabetical order based on the description.

• System. Displays the Server name and serial number. If your Server Administrator has set up the Client to connect with more than one Server, then there will be a list of Servers in the drop-down menu. Choose which Server this resource contacts when starting a connection.

• Resource. Lists the available resources for this Client. Some resources may be listed more than once depending on how the Server Administrator defined the Client.

Note: A resource type must appear in this field in order for the Client to use it. For example, it is not possible for a Client to use or create an SPX entry if the Administrator has not defined at least one SPX resource and assigned it to the Client.


• Phone Number, NetBIOS address, SPX address, or TCP/IP address. This field changes labels depending on the Resource value. Enter a phone number or network address for the resource. The Client does not verify the validity of this field; invalid fields for the resource will cause the connection to fail.

• Settings. On the General property page, click this button to display the Resource Settings window and change the low level settings for the resource.

Use the Resource Settings window to modify these low level communications parameters:

• Packet Size. The number of bytes sent in one packet. A packet may contain from 128 to 8192 bytes. Lower numbers are for systems that cannot handle large amounts of data, or for conditions where it is difficult to send a large packet without line interference. Higher numbers maximize throughput and result in a shorter session time. Available values may vary; see the note below.

• Window Size. Specifies the maximum number of packets transmitted before the Server waits for an acknowledgment. This value should often be set to the maximum unless some equipment between the Client and Server requires a specific window size.

• Retransmit Timeout. Indicates the number of seconds to wait before retransmitting unacknowledged data. Should be set to higher values on links with high delay times, such as slow networks or satellite links.

Note: Due to performance considerations, we recommend that you do not use the NetBIOS resource during Remote Control sessions or when connecting to Windows 3.1 Clients.

Note: Changing these settings without an understanding of their results or your network configuration may cause your connections to fail or decrease appreciably in performance. Consult with your Server Administrator for assistance with these parameters.

Note: The Packet Size and Window Size fields work together to define the total number of unacknowledged bytes at any point in time. Multiplying these two values cannot exceed 8192 bytes; therefore, some values may not be available in one field until the other field value is reduced. For example, when Packet Size is set to 4096, Window Size values from 3 to 8 are not available.


• Session Timeout. The Session Timeout value determines how long a connected session continues without a successfully acknowledged packet.

• Enable Data Compression. When enabled, the Server automatically compresses data to maximize the data throughput. This feature is not necessary if your modem provides data compression or for network based resources.

• Prefix/Suffix button. To view or define character strings that can be used in a phone number or dial string, click this button on the General property page of the Modify Dialing Directory Entry window. You will then see the Prefixes/Suffixes window of defined values.

Codes and their corresponding strings appear in the list box. To use a code, type it in the Phone Number or Network address field in the General property page of the Modify Dialing Directory Entry window (explained in the previous section).

Other controls on the Prefixes/Suffixes window include:

• Add. Opens the Edit Prefixes/Suffixes window, where you can add a new prefix or suffix entry.

Enter the Description and String, then click OK to place the entry in alphabetical order in the Prefixes/Suffixes window.

• Delete. Highlight an entry and click Delete. You will see a warning dialog box, prompting you to confirm the deletion. Click OK to proceed.

• Edit. Highlight an entry to edit, then click Edit. The Edit Prefixes/Suffixes window appears with the current values. Change the values if needed and click OK.

Using the Tasks property page

From the Tasks property page in the Modify Dialing Directory Entry window, you can select which tasks to execute or disable ESD. The Tasks property page is only available when the Server Administrator enables this feature for the Client. All choices on this page are available to all resource types.


• Selected Tasks for Inbound Connection. This list box displays the tasks you can enable or disable when the Client initiates a connection.

Highlight the tasks you wish to perform, or deselect an entry to prevent it from executing. Do not disable an entry if you are uncertain of its function. Contact your Server Administrator for more information on that task.

• Click Defaults to reset the list box to default settings. The Client highlights and deselects items based on the status of the item as defined by the Server Administrator.

• Disable Electronic Software Distribution. When enabled, the Client does not receive any files that are part of the software distribution tasks. Use this option to prevent a potentially lengthy file download from taking place or to allow transfers to occur during off-peak hours.

• Show tasks during connection. Check this option to display the task name currently being executed in the main window. The task name appears in between file transfers.

Note: Some tasks that are not in the list may execute during an inbound session. These tasks cannot be disabled because they have been defined as required by the Server Administrator. In addition, outbound connections from the Server process all tasks, regardless of their settings in this list box.


Using the Async Setting property page

In the Modify Dialing Directory Entry window, asynchronous resources display an additional Async Settings property page. This page contains settings for modems and phone systems.

Use these options to modify modem and dial script parameters:

• Modem. Displays the name for settings that operate with this modem. The settings are initially provided by RemoteWare; you or your Server Administrator can create, set, or modify modem definitions. Click the down arrow for a list of supported modems. If you do not see your modem in the list, contact your Server Administrator or create your own definition by clicking the Modems button.

• Modems button. Click to open the Modem Definition window, where you can view and modify modem commands and expected return codes. See the section “Working with Modem Definitions” later in this chapter for an explanation of this window.

• Dial Script. Displays the dial script currently used for this entry. A dial script consists of commands used to place calls or to complete a logon sequence on a network provider or communications service. Dial scripts may be assigned to the Client by the Server Administrator, or you may create specific dial scripts by clicking the Dial Scripts button. See “Defining Dial Scripts” later in this chapter for more information.

• Dial Scripts button. Click to open the Dial Script Setup window, which lists defined dial scripts and allows the Client user to create, edit, or delete dial scripts.


To change or define a dial script, see the “Defining Dial Scripts” section later in this chapter.

� For a Direct Connect asynchronous connection, the Max Data Rate setting for the Server’s asynchronous resource must match the Data Rate of the Asynchronous resource defined for the Client.

• Data Rate. Defines the data transfer rate for the modem chosen. Normally, this value equals the maximum data rate for the modem. Modems that support CTS/RTS (hardware) flow control can specify higher data rates to take advantage of the modem’s ability to reliably control the data speed based on line conditions. Data rates may be from 1200 to 57600 bits per second.

• Port. Indicates which hardware serial port to use on this Client for this modem. Choices may be from COM1 to COM4.

• Auto Detect button. Click to instruct the Client to search the computer for all serial ports and attached modems. Once the search is complete, the Client presents a list of ports and a description of the attached serial devices in the Available Ports window.

Ports labeled as “direct connect” do not have a detectable modem, either because a modem is not attached to the port, the modem is not powered on, another application is using the port, or the Windows Ports settings (from the control panel) are incorrect.

• Disable Auto Answer. Check this option to prevent the modem from answering the line. Disabling the Auto Answer function is helpful when the modem shares a


line with a voice phone or fax device, or when the Client always initiates inbound connections to the Server.

Working with modem definitions

Create, modify, and delete modem definitions from the Modem Definition window. You can edit only modem definitions that were created on the Client. To access the Modem Definition window from the main window:

1 On the File menu, select Dialing Directory or click the Directory button. The Dialing Directory window appears.

2 Highlight any asynchronous item and click Edit. If possible, choose an item that most resembles the definition you are about to create.

3 You will see the Modify Dialing Directory Entry window, which is explained earlier in this chapter.


4 Click the Async Settings tab to view the Async Settings property page.

5 Click the Modems button. The Modem Definition window appears.

Creating a new modem definition

1 From the Modem Commands property page in the Modem Definition window, use the Select a Modem drop-down list to choose a modem that most closely matches the definition you wish to create.

2 Click New.


3 Enter a name in the Modem name text box.

4 Define or change any of the options on the Modem Commands or Miscellaneous property pages. (See “Modem Commands property page” and “Miscellaneous property page” later in this section for more information on these options.)

5 Click Save when you have finished defining the modem. The modem name you defined appears in the Modem field on the Async Settings property page of the Modify Dialing Directory Entry window.

Renaming or modifying a modem definition

1 From the Modem Commands property page in the Modem Definition window, use the Select a Modem drop-down list to choose a modem to rename. The choice must be a modem that was defined at the Client; otherwise all the fields are dimmed. (To create a modem definition at the Client, see “Creating a new modem definition” in the previous section.)

2 Type the new name in the Modem name text box. You can also change any options as necessary. See the sections “Modem Commands property page” and “Miscellaneous property page” later in this chapter for more information on these options.

3 Click OK. The Client renames the modem definition and places it in the modem list.

Deleting a modem definition

1 From the Modem Commands property page in the Modem Definition window, use the Select a Modem drop-down list to select the modem to delete. You can only delete modems defined by the Client.

2 Click Delete. Select Yes at the confirmation window to permanently remove the entry.

Using the Modem Definition property page

The Modem Definition window includes two property pages: Modem Commands and Miscellaneous. These property pages and their options are listed in the following sections.

Modem Commands property pageThe Client communicates with the modem using text codes defined on the Modem Commands property page in the Modem Definition window. RemoteWare and your Server Administrator have defined many of the modems you may encounter. Determine if your Server Administrator has a modem definition before defining a new modem.


Depending on the modem and its features, some options on this page may need to be altered to set the correct combination of features on the modem.

Options on this property page include:

• Select a modem. Lists the currently selected modem and displays its settings. Click the down arrow to display the list of defined modems.

• Modem Name. Displays the current name for the modem. Use when defining a new modem definition or modifying an existing definition.

• Initialization. Use up to 60 characters to set up operating conditions for dialing and listening. This string is commonly used to set timeout values, disable flow control, enable compression, and so on. An exclamation mark “!” must always be used at the end of a line to specify a carriage return.

• Auto Answer. Specifies conditions for letting the modem answer incoming calls. Standard formats are usually provided by the modem manufacturer, and include enabling the auto answer function, setting the number of rings before a connection, and other answering options. An exclamation mark “!” must always be used at the end of a line to specify a carriage return.

• No Answer. Specifies conditions to not answer incoming calls. The Client sends this string to the modem after a connection has ended. An exclamation mark “!” must always be used at the end of a line to specify a carriage return.

• Dial. Use up to 9 characters to define the AT command used to dial the number. This string is prepended to the phone number, and generally instructs the modem to use pulse (ATDP) or tone (ATDT) dialing.


• Escape. Define up to 9 characters that are used to place the modem into the command mode. This string is usually sent to prepare the serial device for additional commands (such as the Initialization or Hang Up).

• Hang Up. Up to 9 characters can be used to instruct the modem to terminate the connection. An exclamation mark “!” must always be used at the end of a line to specify a carriage return.

Miscellaneous property pageResult codes and timing parameters exist and may be set from the Miscellaneous property page in the Modem Definition window. Changes may be necessary for new modem definitions, or if your current definition does not respond properly to the modem.

The options on this property page are:

• Select a modem. Use this drop-down list to select an existing modem definition from the list. Choosing a definition displays its corresponding parameters in the rest of the fields. The Client dims the options for modem definitions created by the Server because they cannot be changed.

• Current Result Code. Displays the numerical result code returned from the modem and its meaning. Result codes are a modem’s response to Client commands. During a connection, the Client expects to receive numeric result codes from the modem. This exchange is visible from the Modem Monitor, which is discussed later in this chapter. A modem might use a different number to stand for a result. Use this drop-down list and the New Result Code text box to assign a new result definition to a number so that the Client interprets the number correctly during a connection.

To change the number for a result code, select the entry you wish to change from the drop-down list. Type the new value in the New Result Code text box.

• New Result Code. Displays the result code that matches the Current Result Code option. Use this text box when you wish to change the number for the current result code.

• Max Data. Select the bits per second (from 1200 to 57600) that defines the upper data transfer limit for the modem.

• Modem Delay. Specifies how long in milliseconds the Client pauses before sending the next command to the modem. With older modems, you might need to increase this value to allow more time for the modem to process commands.

• Modem Timeout. Determines how long the program waits for the presence of a carrier signal during a connection attempt. The modem stops the attempt if a

Note: Three digit result codes are not supported.


carrier signal from the remote modem is not recognized during this number of seconds. Increase this value higher if your modem frequently fails to recognize the remote modem’s carrier signal in time to set up a connection. This value should match the S7 register set in the Initialization string. The S7 register tells the modem how long to wait for carrier detect.

• Modem Flow Control. Click this check box to enable hardware flow control between the Client and the modem. Hardware flow control allows the Client to transmit at the highest possible data speed, automatically adjusting for conditions such as line quality, busy destinations, and modem limitations.

Defining Dial Scripts

A dial script consists of commands used to place calls or complete a logon sequence on a network provider or communications service. The dial scripts may be constructed by the Server Administrator or Client user. Client users may only modify dial scripts created on the Client.

From the Async Settings property page of the Modify Dialing Directory Entry window, click the Dial Scripts button to open the Dial Script Setup window. This window lists defined dial scripts and provides access to the Dial Script Editor.

The Dial Script Setup window lists each defined dial script on a separate line. For each entry, the window displays the date and time the entry was created or last modified, and may also display the compile date and time. Entries missing a Last compiled date and time (indicated by an asterisk “*”) cannot be used until they are compiled.


Creating a new dial script

1 From the Dial Script Setup window, click New. You will see the New Dial Script window.

2 In the text box, type up to eight characters for the new script name and click OK. This opens the Dial Script Editor.

3 Start typing the dial script commands. Use the commands in Tables 5 and 6 as a guide.

4 When you are finished entering the dial script, do one of the following:

• To save the dial script without compiling, click Save. This dial script will not be available to the Client until it is compiled at a later date. Use this option when you have not completed the dial script, when it needs further work to compile successfully, or when you do not want it used on the Client at this time. Once it is saved, click Close to exit the window.

• To verify the dial script syntax, click Compile. A message appears at the bottom of the window if the compile is successful. Successfully compiled dial scripts may be used by the Client to initiate connections to the Server. Once the compile is successful, you should click Close to exit the Dial Script Editor.

• If you want to discard the work you have done, click Close.


5 The Client returns to the Dial Script Setup window. Click OK to finish working with dial scripts. Any dial scripts you define and compile appear in the Dial Script drop-down list on the Async Settings property page of the Modify Dialing Directory Entry window.

Table 6. Dial Script commands

CommandExample

Description

; or REM; This is a commentREM Call next; send name.

Text that follows a semicolon or REM is not executed. Use these commands to add comments to a script or deactivate script commands. REM or “;” must be the first item on the line. A comment cannot follow a command on the same line.

DIAL "{string}"

DIAL "ATDT9,5551212,,2001!"

Transmits a string and waits for a return code. The string can consist of AT modem commands, which may include the special characters see Table 6), the <phone #> variable, and an exclamation mark “!” at the end of the command as a carriage return. Use DIAL instead of TRANSMIT when you want the Client to process result codes (for example, “13” for “CONNECT 9600”) returned from the modem.

DLLCALL {command} ["string"]DLLCALL 101 "NOWAIT"

DLLCALL executes an external routine supplied by the Administrator. A programmer creates DialScriptExternalCommand() and compiles it into the RWWDSEXT.DLL module. Command is an integer identifying a specific action in the function, and string optionally passes an argument to the function.

PAUSE {seconds}PAUSE 60

Insert a delay from 0 to 65,535 seconds.

MODEMINIT ["{string}"]MODEMINIT MODEMINIT "AT&F1S0=0!"the assigned modem. The Client uses the modem assigned to the current

Transmits a string and waits for an “OK” return code from the modem. Specifying no string transmits the default Initialization value for the assigned modem. The Client uses the modem assigned to the current connection configuration. The string can consist of AT modem commands, which may include special characters (see Table 6), the <phone #> variable, and an exclamation mark “!” at the end of the command as a carriage return.

TRANSMIT "{string}"TRANSMIT "ready"

Transmits a string and continues without waiting for a reply. TRANSMIT is usually used to send login information to another system. The string can consist of any text, which may include special characters (see Table 6), the <phone #> variable, and an exclamation mark “!” at the end of the command as a carriage return.


WAITFOR {seconds} "{string}"WAITFOR 400 "log in:"

Delays execution from 0 to 65,535 seconds, or until the modem returns the value in string. String is case sensitive. WAITFOR returns a TIMEOUT if no match occurs before the time expires. WAITFOR ignores parity when comparing strings.

{ } = Required argument[ ] = Optional argument

Table 7. Dial Script special characters and variables

Character or variable Example Description

, (comma) DIAL "ATDT9,11031,,,55 0032"

Inserts a pause in a dial string. Use one or more commas to instruct the modem to wait while the communications network is occupied. The delay time depends on the number of commas and the serial device. With modems, the S8 register typically defines the delay time for one comma.

! (exclamation mark) MODEMINIT "AT&F1!"DIAL "ATDT 5551212!"

Inserts a carriage return. This is often required to start processing a command on serial devices or networks. The “!” may be used anywhere in the string, but the MODEMINIT and DIAL commands require “!” at the end of the string.

" " (quotation marks) TRANSMIT "Hello" Strings must begin and end with quotation marks. To specify a quotation mark in a string, use the literal character “\"“.

/ (backslash) TRANSMIT "\! \\ \ff \!"

Uses the literal character or a hexadecimal value that immediately follows the backslash. Some common literal characters are “\,” for comma, “\"“ for quotation marks, “\!” for exclamation mark, and “\\” for backslash. Use two hexadecimal characters to transmit that value; “\ff” sends FF hex or 255 decimal.

Table 6. Dial Script commands (continued)

CommandExample

Description


Copying a dial script

1 From the Dial Script Setup window, highlight the dial script you want to copy.

2 Click Copy. You will see the Copy Dial Script dialog box.

3 Type up to eight characters for the new dial script name and click OK.

4 The Dial Script Editor allows you to make any modifications to the dial script. Changes must be compiled to be available to the Client, even if the dial script has been compiled in the past.


5 Do one of the following:


• To save the dial script without compiling, click Save. This dial script will not be available to the Client until it is compiled. Then click Close to exit the window.

• To verify the dial script changes, click Compile. A message appears at the bottom of the window if the compile is successful. Use compiled dial scripts to initiate connections to the Server. If the compile is successful, click Close to exit the Dial Script Editor.

6 The Client inserts the new dial script into the Dial Script Setup list box. Click OK if you are finished working with dial scripts. New compiled dial scripts appear in the Dial Script drop-down list on the Async Settings property page of the Modify Dialing Directory Entry window.

Modifying a dial script

1 From the Dial Script Setup window, highlight the dial script you want to change.

2 Click Edit to display the Dial Script Editor window.

50 R em o t e War e W i n do w s 3 . x C l i en t U se r ’s G u i de

3 Make any changes to the dial script in the Dial Script Editor.

4 When the changes are complete, do one of the following:


• To save the dial script changes without compiling, click Save. This dial script will not be available to the Client until it is compiled, even if it was compiled at an earlier date. Then click Close to exit the window.

• To verify the dial script changes, click Compile. A message appears at the bottom of the window if the compile is successful. When successful, this compiled dial script may be used by the Client. If the compile is successful, click Close to exit the Dial Script Editor.

5 If the Save or Compile functions were used, then the Client updates the dial script. Click OK from the Dial Script Setup window if you are finished working with dial scripts.


Deleting a dial script

1 From the Dial Script Setup window, highlight the dial script that you want to delete, and click Delete.

2 You will see a warning dialog, asking you if you want to delete the dial script.

Click Yes to confirm the operation.

3 Dial Script Setup removes the dial script from the list box. Click OK if you are finished working with Dial Scripts.


� Modifying Client Setup

A Client’s password is one level of security that permits a connection with a specific Server. The password and other connection information are available from the Current Client Setup window.

On the File menu, select Setup or click the Setup button to view this window.

Changing the password

The Server uses the Client password to recognize a valid Client of the system. Do not change this password without being directed to do so by your Server Administrator. Change the Client’s password only if the same change occurs at the Server. The wrong password will prevent the Client from connecting.

To change the Client password:

1 On the File menu, select Setup or click the Setup button. You will see the Current Client Setup window.

2 The Current Client Setup window displays the current password. Type the new password in the Password text box. The password may be from 1 to 10 characters.

3 Click OK to accept the new password.


� Using Schedules

Use the Client scheduler to set a daily time for the Client to contact the Server. Once active, the Client may initiate an inbound connection to the Server at a fixed time each day. Only one schedule can be defined at a time.

The schedule is useful for unattended Client operation. For example, to schedule an unattended connection to begin at midnight, set the connection time for 00:00 and leave the Client computer on for the night.

To set a time for a connection to start:

1 On the File menu, select Schedule or click the Schedule button. You will see the Schedule Connection window.

2 Check the Enable Scheduled Connection check box to activate the scheduler.

3 The Connection Time button displays the current starting time for the scheduler. Click the Connection Time button to change the time.

Note: The schedule cannot be modified if the Server Administrator has set it from the Server. The connection occurs at the scheduled time unless the Client software is not running or it cannot access the connection hardware.

Note: If every control on the Schedule Connection window is disabled, then the Server has set the Client’s schedule. It is not possible for a Client to modify a schedule set at the Server. Contact your Server Administrator to adjust the schedule.


4 You will see the Set Connection Time window, which allows you to change the 24-hour time. Remember to properly represent afternoon times, such as 14:36 for 2:36 PM.

5 Click OK to exit the Set Connection Time window.

6 Check the Enable Retries check box to permit the Client to retry the connection should the first attempt fail. When enabled, the Client attempts to contact the Server a maximum of three (3) times, 5 minutes apart, before logging the attempt as unsuccessful.

7 Click OK to exit the Schedule Connection window.

The communications session runs automatically, according to the set schedule, as long as Client Communications is running. The schedule is not saved when you exit Client Communications.

Deactivating the schedule

There are two different scenarios and procedures for deactivating the schedule:

Schedule set by the Client. Click the Schedule button or select Schedule on the File menu. If the controls in the Schedule Connection window are active, then clear the Enable Scheduled Connection check box. The schedule is disabled.

Schedule set by the Server. If the Schedule Connection window will not allow you to clear the Enable Scheduled Connection check box, then your schedule has been activated from the Server. The Server Administrator can disable the schedule from the Server, thereby returning control to the Client. The Client user can also exit Client Communications to temporarily delay the schedule. If the schedule time arrives and Client Communications or WinXNode are running, the Client attempts to place an inbound connection to the Server.

C H AP TE R 2 / U s i n g t he C l i en t 5 5

� Using the Communications Log

Each time the Client attempts to communicate with the RemoteWare Server, the Communications Log records this information:

• Start Time. Lists the date and time when the connection was initiated or accepted from the Server.

• Duration. Displays the minutes and seconds elapsed from the Start Time to disconnection.

• Origin. Indicates whether the Client or Server initiated the connection.

• Status. Displays the outcome of the connection. Possible status values are listed in the following table.

Table 8. Client connection statuses

Status Description

Aborted The Client or Server requested an unexpected interruption in the connection.

Busy Signal The Client could not contact the Server because the resource at the Server end was occupied. Try again later or contact the Server Administrator if the issue persists.

Client disabled The Server has disabled the Client. A connection to this Server is not allowed until the Server Administrator enables the Client.

Client undefined

There is no Client by this name on the Server. The Client may have been deleted. Contact your Server Administrator.

Connect cancelled

A request to stop the connection was issued by the Server or the Client during the connection phase (before the connection was complete).

Invalid Password

The password or security token at the Server and the Client do not match. Contact your Server Administrator to reset security or verify the password for this Client.

Lost Connection An unexpected interruption in the connection occurred through no action by the Client or the Server. Retry the connection; if situation repeats contact your Server Administrator.

Modem error The modem did not return a successful result code in response to a command. Check the modem cabling, restart the modem, and reinitialize the modem.

No answer The Server did not respond when the Client initiated a connection. Verify that the number or address is correct.


No carrier The Server’s modem answered the line, but no carrier signal was detected. Verify that the phone number is correct, the necessary prefixes or suffixes are supplied, and the Server modem is functional. Manually place the call to determine if the Server is answering and providing a carrier signal.

No dialtone The Client’s modem does not detect a dial tone when it uses the phone line. Verify that the phone line is plugged into the correct modem socket, that a phone receiver can detect the dial tone, and that no other tones (such as a message or call waiting beep) occur when the line is picked up.

No status The Client could not assign a status to this connection.

Resource error The Client received or detected an unexpected condition while using a network resource. Verify the correct network address, network access software, and correct network access protocols (such as dial scripts).

Scheduler off The Server is operational but cannot process the tasks in a session because the Scheduler application is currently disabled. Try again later or contact the Server Administrator.

Server down The Server cannot accept the connection because it is not currently running. Try again later or contact the Server Administrator.

Server suspended

The Server cannot accept connections because the Server Administrator has temporarily interrupted its operation. Try again later or contact the Server Administrator.

Successful The connection experienced no errors.

Time out A connection was stopped by the Client because the Server did not respond in a reasonable amount of time.

Undefined An error occurred that did not match any of the defined status types.

Table 8. Client connection statuses

Status Description


To view the Communications Log, on the File menu, select View Log or click the View Log button.

Double-click an entry or highlight the entry and click the Detail button to reveal detailed information on the connection attempt. The Communications Log Detail window contains session and resource information that explains the status and may assist with troubleshooting a Client.

Use the Previous and Next buttons to view details about the other entries in the log. Click OK to return to the main Log window.

When you are finished viewing the Communications Log, click Close from the Communications Log window.


� Viewing Alerts

Icons in the lower right corner of the screen indicate significant events that involve the Client. These alert icons let the user know whether Auto Answer is enabled, whether ESD is enabled, if ESD files have been received, or if a transport error has occurred. To display more information about an alert, click the alert icon or select View Alerts on the Commands menu.

Resource Error

The Client displays the Resource error alert icon when it believes that the current resource is no longer suitable for reliable communications. This may occur because of a modem or network interruption, power disruption, incorrect settings or network address, or contention for the resource from another application.

The Transport Error window displays information about the resource, any information returned from the resource, and an interpretation of the error by the Client.

ESD Arrived

The ESD Arrived alert icon appears when files are detected in the \nodesys\updates directory.

Electronic Software Distribution is a Server feature that transfers the latest files from the Server to the Clients. The Server only sends the files when the Client does not possess the latest version. In addition, the Server automatically resends files that may have been inadvertently altered, moved, or deleted. This feature is valuable when the latest data is required or portions of the Client are deleted accidentally.

The ESD Files window lists the executables and DLLs in the \nodesys\updates directory. This is the default directory for RemoteWare Client software. These files are


automatically installed if your autoexec.bat file was modified during installation. If it was not, you may want to move these files into the \nodesys directory when the Client software is not running.

AA Disabled

The Auto Answer alert icon indicates that this Client cannot accept an incoming call. To accept incoming calls, clear the Disable Auto Answer check box in the Modify Dialing Directory Entry - Async Settings page. This option is covered in the “Async Settings property page” section earlier in this chapter.

Auto Answer is a modem function that picks up the line when the modem detects a ring signal. This feature is required for Clients accepting outbound calls from Servers. However, Auto Answer may be inconvenient when the phone line is shared with voice callers, fax machines, and other computers.

ESD Disabled

The ESD Disabled alert icon appears when the Client user has disabled ESD.

ESD, as described in the “ESD Arrived” section, allows files to be automatically updated across all Clients. It is possible to disable this function by clicking the Disable Electronic Software Distribution check box on the Modify Dialing Directory Entry - Tasks property page. (For more information, see “Tasks property page” in the “Modifying a Directory Entry” section earlier in this chapter.) Disable ESD to control when files are updated. This may be helpful to limit the amount of time needed for a connection, or to permit the Client to receive ESD at off-peak hours. It is also helpful when you want to only receive certain tasks without the risk of a lengthy file transfer.


� Reinitializing the modem

Selecting Reinitialize on the Command menu sends the Auto Answer or the No Answer command string to the modem. Use this option if you have problems communicating with the modem at the Client, or when the Resource Error alert icon appears while using an asynchronous resource.

� Unloading the Client

If Client Communications loaded the WinXNode program at startup, then Client Communications stops WinXNode when you exit the application. If WinXNode was running before you started Client Communications, it will remain resident in memory after you exit the program. To unload WinXNode without closing Client Communications, on the Command menu select Unload Client.

To reload the WinXNode program, on the Command menu select Load Client.

� Selecting Client preferences

The Client offers three options to control the Client’s window behavior. The settings you choose are saved and used each time you exit and re-enter Client Communications.

• Save last position. When enabled, the Client Communications main window appears in the same location when the program ended.

• Use default size. Adjusts the window size to standard dimensions each time Client Communications starts. The window size may be adjusted while the application is running.

• Float to top. Places the Client Communications window on top of all other windows.


� Using the Modem Monitor

Modem Monitor is a diagnostic utility for Clients using asynchronous resources. It allows a Client user to see the current modem status, and to view the command level information between the Client and the modem.

The programs described in the following table launch when you choose Modem Monitor on the Command menu.

Using the Modem Monitor status lights

The status lights display some of the important modem states. Knowing the status of these indicators is most important when the Client is establishing a connection. The progression from one set of indicators to another can signal a problem with the modem or its settings.

The indicators appear red when active and black when they are off. The indicators from

left to right are listed in the following table.

Table 9. Modem Monitor applications

Program nameCommand name

Description

RWNWMMUI.EXEModem Monitor UI

The Modem Monitor user interface lists Client commands and modem responses. Use the transcript of this activity to troubleshoot an asynchronous connection. Modem Monitor is available as a standalone application or from the Modem Monitor command on the Command menu in Client Communications.

RWNWMMST.EXEModem MonitorStatus Lights

The status lights display the current modem condition. This is useful when troubleshooting, or when you cannot directly determine the modem’s operating status (for example, with an internal modem).

Note: Modem Monitor Status Lights may not exactly match modem hardware lights because of timing delays.


Using the Modem Monitor user interface

The Client and its modem send commands to inform and alert each other on the status of the connection, or for behaviors that are necessary for an orderly shutdown of a connection. The Modem Monitor UI displays the transcript from the Client and the modem, allowing the Client user or technician to locate the specific connection stage that may be a problem.

Table 10. Modem status indicators

Indicator Meaning Description

CTS Clear to send Lights when the modem is ready to accept data from the Client.

DSR Data set ready Lights when the Client is ready to send data to the modem.

RI Ring indicator Briefly flashes when the modem has detected an inbound call on the phone line.

DCD Data carrier detect Lights when the audio signal from the Server modem has been received and understood.

RX Received data Indicates that the modem is receiving data from the Server modem.

TX Transmit data Lights when the Client modem is sending data to the Server modem.


The following table list the menu options available with the Modem Monitor.

Table 11.

Menu Command Description

File Clear screen Erases any existing entries from the Modem Monitor window.

Log to “\nodesys\modemmon.log”

Copies any Client or modem command to the Log file. Toggles with the Stop Logging menu option.

Stop Logging Stops appending entries to the log file.

Exit Stops Modem Monitor and closes the window. Does not affect the Modem Monitor Status Lights application.

Options Monitor Transport State Toggle this option to display explanatory messages. These messages are not part of the Client/modem command sequence. These messages appear in black in the Modem Monitor.

Monitor Input Data Toggles to display the return codes sent by the modem. These codes should appear as numeric data. Input data appears in blue in the Modem Monitor.

Monitor Output Data Toggles to display the commands sent by the Client to the modem. The output data appears as red in the Modem Monitor.


� Exiting Client Communications

When you have finished using Client Communications, select Exit on the File menu or click the Exit button.

� Using WinAuto Auto Communications

Administrators can use the WinAuto.exe Auto Communications application in the place of Client Communications if you want the Client user to be able only to monitor communications and schedule a connection to the Server. Auto Communications is a subset of the Client Communications application that only allows the user to monitor communications or schedule an inbound connection. Auto Communications does not contain facilities for viewing or modifying the Log, Client settings, or communication settings.

Auto Communications automatically exits after a successful session has occurred, if the maximum number of retries has been reached, or if the Server places an outbound call to the Client.

Placing Auto Communications on the desktop

To add the Auto Communications application to a program group:

1 Open the program group.

2 From the Program Manager menu, select File and then New.

3 Click the Program Item button, and then click OK.

Note: If you try to exit Client Communications and a schedule is active, the Client displays the message “Warning, schedule is active.” The Client skips the schedule if you exit, but the schedule is set to try again at the next scheduled time.


4 In the Program Item Properties window, enter this information for each option listed:

Leave any other options unchanged with their default values.

Command Line options

Auto Communications can be configured with custom settings from the command line. Table 11 lists the options, an example of each, and their functions.I

If you do not specify any options on the command line, the Auto Communications Options window appears when you start the application.

For this option Enter this value Comments

Description Auto Communications This name is suggested; your label may be any valid Windows description.

Command Line x:\nodesys\winaout.exe Options

Replace x: with the actual drive letter. See the following section for a list of options.

Working Directory x:\nodesys Replace x: with the actual drive letter.

Table 12. Auto Communications command line options

Option Example Description

-d retries minutes winauto.exe -d 5 10 Places a call to the Server using a specified number of retries within a given time frame.

-n winauto.exe -n The example allows up to 5 retries 10 minutes apart. Disables the escape key. The application does not allow the user to exit until the session is successful or the number of retries have been exhausted.

-r minutes winauto.exe -r 30 Reschedules a call to the Server within a specified time after a session has occurred. This example calls the Server, then schedules another call in 30 minutes.

-w minutes winauto.exe -w 15 Specifies a period of time to wait for a successful inbound call from the Server. This example instructs the Client to wait for 15 minutes for a successful session, then exit.

Note: You cannot use the -d, -w, or -r options together.

Note: Start WinAuto for the first time without command line options. This allows the user or installer to specify default settings for the program.


Starting Auto Communications

To start Auto Communications, double-click the Auto Communications icon in the RemoteWare program group. Auto Communications automatically loads the communications engine (if it is not already active) and displays the Auto Communications Options window.

Use the Auto Communications Options window to specify how to handle a connection with the Server. The choices are to place an inbound call to the Server, to call the Server after a session, or to wait for the Server to contact the Client.

The following options are available in this window:

• Using Dialing Directory Entry. For the Dial-Out and Reschedule choices, select the connection method the Client uses when initiating an inbound connection to the Server. Auto Communications uses the Dialing Directory default entry if none is supplied.

Select one of the three following connection methods:

• Dial-Out. Immediately start an inbound call using the settings from the Using Dialing Directory Entry field. These fields are related to the Dial-Out option:

Retry n times t minutes apart. Select the number of permissible retries and the retry interval. The Client uses this information if the connection is unsuccessful. Specify 0 to 999 retries that are from 0 to 999 minutes apart. A value of zero (0) minutes apart instructs the Client to initiate a connection immediately after an unsuccessful attempt. (The default setting is 3 retries 5 minutes apart.)


Use Alternate Entry. Click the check box to allow the Client to use a different Dialing Directory entry if previous attempts to reach the Server are unsuccessful. Select a different Dialing Directory entry than the item at the top of the window, and change the On retry # field if necessary.

On retry #. Determines when the Client begins to use the communication settings in the Use Alternate Entry option. Select from 0 to 999 retries; the default setting is the second retry. Selecting zero (0) bypasses the primary resource and uses this resource for the first connection.

• Reschedule. Similar to Dial-Out, but reschedules another inbound connection. The next connection occurs 0 to 999 minutes after the last session; the default setting is 5 minutes. Depending on the time interval, this option is useful for periodic Server queries when the Client is out of the Server’s reach.

• Wait. Set up the Client to wait for an outbound call from the Server for a set number of minutes. The Auto Communications application will wait for a successful session from 1 to 999 minutes. The default setting is 5 minutes. A value of zero (0) minutes instructs the application to wait indefinitely. Auto Communications will not exit until a successful session has been completed.

• Save Options. Select to use the settings defined in this window each time Auto Communications begins. The current settings become default values when the application is next started.

Once you have set the options, click OK to start Auto Communications. If you click Cancel, the settings will not be saved and Auto Communications does not start.

Exiting Auto Communications

Click Exit to stop Auto Communications before it terminates normally.

A P P E N D I X

A

A Understanding the Client Directory Structure

This appendix discusses the following file system information:

• What happens during installation

• Changes to existing Windows files and directories

70 R e m o t e Wa re W i nd o ws 3 . x C l i e n t U se r ’s G u id e

� Installation details

An installation of the RemoteWare Client begins with a set of files generated by a RemoteWare Server. The group of files are called an installation kit (or makekit). Although makekits generally reside on one or more floppy disks, they may also be created on a hard disk or network volume. Only one makekit can be created on a hard drive or network volume, but the files and directories can be moved to another location for storage.

The SETUP.EXE application installs the makekit from any floppy disk, hard drive, or network volume. Files in the makekit must be installed to the root directory of a hard disk accessible to the Client. Exactly one Client may be installed on a disk partition.

The SETUP.EXE application performs the following tasks:

• Decompresses the setup files and places them in the ~msstfqf temporary directory.

• Obtains the destination directory and creates the \NODESYS and \RWNODE directories

• Copies the files provided in the \FILES directory to the \NODESYS directory.

• Provides the option to start the communications engine at startup.

• For 16-bit Windows computers, provides the option to automatically update files during bootup.

• For template Clients, obtains necessary configuration and security information.

• Provides the option to view and change connection numbers or addresses.

• Removes temporary files from the hard disk.

� Files and directory changes

A RemoteWare Client installation and subsequent operation performs these tasks:

• Creates the \NODESYS directory and all its files and subdirectories.

• Creates the \RWNODE directory and sets up the Client information.

• For Windows 3.x computers, optionally modifies the AUTOEXEC.BAT file to contain commands to automatically copy and then delete files from the \NODESYS\UPDATES directory to the \NODESYS directory. This occurs during bootup to avoid modifying a file that may be in use. If the modification occurs to the AUTOEXEC.BAT, then SETUP copies the original to AUTOEXEC.BAK.

• Creates the RemoteWare program group and icons for the RemoteWare Client applications.

• Optionally adds the WinXnode icon to the Startup program group.

A P P EN DI X A / U n de r s t a n d i n g t h e C l i e n t D i r e c t o r y S t r u c t u r e 71

The WINESD directory

One of the directories created on the Client is \winesd. This directory is where the Server sends files that need to be placed in the Client’s Windows directory. The Client Communications application checks the Windows directory each time it is launched. Any out of date file in the Windows directory is updated with the file in the \winesd directory. Files in the \winesd directory are never deleted by the Client when the update is completed; you must do this manually.

Index

A

AA Disabled alerts 59

Aborted status 55

About Client Communications command 28

alert icons

in the status bar 29

list of 29

alerts

AA Disabled 59

ESD Arrived 58

ESD Disabled 59

list of 29

Resource Error 58

viewing 58

async communications

dial scripts for 37

performing diagnostics 61

setting properties for 37

settings for 16

authenticating the Client 14

auto answer

disabled 38

enabling 42

Auto Communications

exiting 67

options for 66

placing on desktop 64

starting 66

using command line options with 65

working with 64

Auto Detect option 17, 38

autoexec.bak file 70

autoexec.bat file 11, 70

B

Busy Signal status 55

buttons, in Client Communications 26

C

Cancel command 27

Clear screen command 63

Client Communications 25

diagnostics 61

exiting 64

main window 26

menus and buttons 26

selecting preferences for 60

starting 25

status bar 28

statuses 55

unloading 60

Client directory structure 70

Client disabled status 55

Client name, supplying 13

Client password 13, 52

Client phone number, entering 17

Client setup, modifying 52

Client undefined status 55

Command Line options, using to configure Auto

Communications 65

command line, starting the Client from 25

Command menu 27

communication settings

async 16

configuring 16

NetBIOS 18

SPX 19

TCP/IP 20

Communications Log

viewing details 57

working with 55

compiling dial scripts 49, 50

compressing data 35

configuring template Clients 13

Confirm when copying files option, disabling 12

Connect cancelled status 55

Connect command 27

connecting

to the Server 30

using Dialing Directory entry 30

connections


scheduling 53

to the Server 30

via a Dialing Directory entry 30

contact information, supplying 14

CTS modem status indicator 62

current resource, identifying 29

D

-d retries minutes command line option 65

data compression 35

data rate

adjusting 18

selecting 43

setting 16, 38

DCD modem status indicator 62

deactivating schedules 54

default directory, identifying 28

default entry, setting in Dialing Directory 32

deleting

dial scripts 51

modem definitions 41

prefixes and suffixes from dial strings 35

DIAL command 46

Dial Script Editor 45

dial scripts

compiling 45, 49, 50

creating 45

defining 44

deleting 51

for async communications 37

list of commands 46

modifying 49

special characters and variables 47

dial strings, prefixes and suffixes 35

Dialing Directory 25

creating new entries in 32

General property page 33

modifying entries 33

setting a default entry 32

Tasks property page 35

using to connect 31

Dialing Directory command 27

Dialing Directory entry

using to connect 30, 66

directory changes made by Setup.exe 70

disabling ESD (electronic software distribution) 35,

36

DLLCALL command 46

DOS 6.2 12

DSR modem status indicator 62

E

enabling data compression 35

entries

creating in Dialing Directory 32

modifying Dialing Directory 33

ESD Arrived alert 58

ESD Disabled alert 59

ESD, disabling 35, 36

Exit command 27, 63

exiting

Auto Communications 67


F

File menu 26, 63

file transfers, progress indicators 30

G

General property page 33

H

Help Index command 28

Help menu 28

I

icons, for alerts 29

inbound connections, selecting tasks for 36

installation kit 10

installation, completing setup 21

installing

RemoteWare Client software 10

template Clients 13

Invalid Password status 55

I n de x 75

K

kit, installation 10

L

Load Client command 27

Log to command 63

logs, Communications 55

Lost Connection status 55

M

maximum data rate, selecting 43

menus, in Client Communications 26

modem definitions

creating 40

deleting 41

renaming and modifying 41

working with 39

modem delay, setting 43

Modem error status 55

modem flow control, setting 44

Modem Monitor 61

menu commands 63

status indicators 62

using status lights 61

using the user interface 62

working with 61

Modem monitor command 28

Modem Monitor UI application 61

Modem Monitor, applications in 61

modem timeout, setting 43

modem type, specifying 16

MODEMINIT command 46

modems

detecting automatically 17

reinitializing 60

selecting 42, 43

specifying data rate 18

modifying

Client setup 52

dial scripts 49

Directory entries 33

Monitor Input Data command 63

Monitor Output Data command 63

Monitor Transport State command 63

N

-n command line option 65

name, of Client 13

NetBIOS communications

Server address 18

settings for 18

No answer status 55

No carrier status 56

No dialtone status 56

No status status 56

NodeComm.exe 24

NodeReg.exe 24

NODESYS directory 70

O

Options command 28

Options menu 63

P

packet size, specifying 34

passwords

changing 52

supplying 13

PAUSE command 46

ports

selecting 38

specifying 16

preferences, selecting 60

prefixes and suffixes, for dialing strings 35

R

-r minutes command line option 65

registering template Clients 15, 21

registration information, supplying 14

registration key, entering 14

registration, connecting in order to 21

Reinitialize command 27

reinitializing a modem 60

REM command 46

requirements, system 10


Resource Error alerts 58

Resource Error status 56

resources

async 37

list of available 33

selecting 30

result codes 43

retransmit timeout, specifying 34

retry times, setting 66

RI modem status indicator 62

RWNODE directory 70

RWNWMMST.EXE 24

RWNWMMST.EXE application 61

RWNWMMUI.EXE 24

RWNWMMUI.EXE applicatio 61

RX modem status indicator 62

S

Schedule command 27

Scheduler off status 56

schedules

deactivating 54

setting connections times 53

working with 53

Server down status 56

Server NetBIOS Address 18

Server phone number 16

Server serial number, supplying 14

Server suspended status 56

Server, connecting to 30

session timeout, specifying 35

Setup command 26

setup, completing 21

setup.exe 10

SETUP.EXE application 70

software, installing 10

special characters, for dial scripts 47

SPX communications 19

starting

auto communications 66


Client from the command line 25

Client from the icon 25

Startup group, placing Client programs in 11

status bar, in Client Communications 28

Status Lights

application 61

using 61

statuses of Client Communications 55

Stop Logging command 63

Successful status 56

suffixes, adding to dial strings 35

system requirements 10

T

tasks

for inbound connections 36

selecting to perform 35

Tasks property page 35

TCP/IP communications

Client and Server addresses 20

settings for 20

template Client

configuring 13

installing 10

registering 15, 21

Time out status 56

toolbar buttons, in Client Communications 26

TRANSMIT command 46

TX modem status indicator 62

U

Undefined status 56

Unload Client command 27

unloading Client Communications 60

unregistered Clients 15

Using Help command 28

V

variables, for dial scripts 47

View Alerts command 27

View Log command 27

viewing alerts 58

W

-w minutes command line option 65

I n de x 77

WAITFOR command 47

WinAuto Auto Communications 64

WinAuto.EXE 24

window size

adjusting 60

specifying 34

windows, Client Communications 26

WINESD directory 71

WinXNode program 25

unloading 60

WinXNode.EXE 24

remoteware windows 3.x client user⁍꥔㈡猺팃듃=쨘 · pdf fileavailable in all countries...

Documents