9.2
Using the Registration Code
First, install the ATRLS using the
Installation
section above. You may use either the
Windows Control Panel or the command line program to apply your registration code to
the ATRLS software.
9.2.1 Windows Control Panel
Using the Start button, invoke the Windows Control Panel from the Settings/Control
Panel menu. Double click the “Ataman TCP R. L. Services” icon. Then, from the
“About” page, click on the “Register…” button and you will see:
Fill in the information from the “Letter of Registration” you received when you purchased
a product license. Click the “OK” button. Be sure the “Registration Name” is spelled as
shown in the Letter of Registration. The spelling must be exact since the Registration
Code is tied to the Registration Name. If a mistake in the spelling of the Registration
Name has occurred contact Ataman Software’s Technical Support and a new code will be
issued.
Be sure to save your registration information. You will need it when you reinstall the
software.
9.2.2 Command Line
Alternatively, you can use a command line program to do the registration. This is useful
if you want to automate the registration process using .CMD files. In the directory where
you installed the ATRLS, you will find a program called register.exe.
Retrieve the “Registration Code” and “Registration Name” from the “Letter of
Registration” you received when purchasing the product license. The Letter of
Registration arrived with your diskette. To use register.exe, start a command
prompt and issue the following command using the information from the Letter of
Registration.
register Registration_Code "Registration_Name"
7
The two quotes (
"
) above must be used if the name of the registered user is more than one
word. You should replace
Registration_Name
with the name listed beside the
“Registration Name:” entry in the registration letter and replace
Registration_Code
with the code listed beside the “Registration Code:” entry. (Typically
Registration_Name
will be either your name or your company’s name.)
10. Using the ATRLS
10.1 Configuring the ATRLS
To configure the ATRLS, invoke the “Ataman TCP R. L. Services” control panel, through
the Windows Start button from the Control Panel item in the Settings menu. The various
user and program settings are described below.
10.1.1 Users Page
To add a user, select the “Add User…” button. To edit a user, select the desired user
account name, and then press the “Edit User…” button. (Alternatively, you can double-
click the user account name you want to edit.) To delete a user, select the user account
you want deleted, then press the “Delete User…” button. You will be asked to confirm
the operation.
8
10.1.1.1
User Name
This is the user account name the remote client programs will use to allow remote users
to logon. This name is the name used by the outside world. The ATRLS treats user
account names that differ only in the case of letters as the same account.
10.1.1.2
NT User Name
This is the Windows user account that will execute for this remote user’s logon. This can
be an account either on the local machine, or in a Windows domain. This account name
is the same name as the “Username” listed in the User Manager program.
10.1.1.3
NT User Domain
This is the domain name associated with the NT User Name above. If the NT User Name
is not a domain account, but is local to the system you are configuring; you should place a
single period or dot “.” in this field.
10.1.1.4
Home Directory
This is the initial working directory given to the commands initiated by this user account.
This directory should be local to the system you are configuring. This directory will be
automatically set into the environment variable HOME when the user logs on.
9
10.1.1.5
Interactive Command Processor and Batch Command Processor
By default, the ATRLS pass the command from the rsh client to the cmd.exe command
processor that comes with Windows. If you have purchased an alternate command
processor that you would rather use, enter the command processor’s path and any
switches in this field. Because the command processor often needs different arguments
when used interactively, rather than in “batch” mode, we provide two forms of command
processor string. The Interactive Command Processor is invoked by telnetd and rlogind.
The Batch Command Processor is invoked by rshd and rexecd. When the Batch
Command Processor value is used, the environment variable COMMAND is set to the
command passed in from the remote rsh or rexec client program. In both instances, the
value of the Command Processor field is environment expanded.
For example, you could have rshd invoke cmd.exe by entering:
%COMSPEC% /C %COMMAND%
When a remote user uses an rsh client program to issue the dir command, on most
systems the resulting command will be:
C:\WINNT\SYSTEM32\CMD.EXE /C DIR
In the version 1 of the ATRLS, a script called REMOTE.CMD was automatically invoked
when a user logged-on. You can achieve the same functionality in version 2 by setting
these fields as follows:
Interactive Command Processor:
%COMSPEC% /K CALL %HOME%\REMOTE.CMD
Batch Command Processor:
%COMSPEC% /C CALL %HOME%\REMOTE.CMD&%COMMAND%
10.1.1.6
NT Password
This value is used only with rshd or rlogind if the user is allowed to logon without a
password. If you do not want the rshd or rlogind (without password) functionality, do not
set this field.
This is the password associated with the Windows user account specified above. This
field is necessary because Windows has no facility that allows a security context change
without the presence of a password. (In other words Windows does not have a capability
similar to the Unix setuid() system call.) This password must be changed any time
the Windows user account’s password is changed.
10.1.1.7
Host Equivalence List
This value is used only with rshd, or rlogind if the user is allowed to logon without a
password. If you do not want the rshd or rlogind (without password) functionality, do not
set this field.
This is a comma-separated list of host names or TCP/IP addresses from which this user
account name is allowed to execute commands. Limited wildcards are supported.
Specifically, names of the form “*.univ.edu” will allow all host names ending in
10