Use the Endpoints tab to specify
protocols to be used by workstations connecting to the Server for
remote procedure calls.
The protocol Named-Pipe (ncacn_np) and endpoint
\PIPE\RTSERVER are entered by default. This is usually the most efficient
method for workstations in the domain to connect to the Server. To
add access for a workstation outside the domain, you must add the
additional protocol.
You can include all protocols and endpoints
available to the Server by clicking the down arrow in Protocol and
selecting Supported Protocols (All) from the
list. Endpoints are created for every available protocol. When configured
this way, workstations must query an RPC Locator for the endpoints
when connecting to the Server. This query introduces a small delay
when the server is first selected and may compromise security.
Note: When Supported
Protocols (All) is selected, Endpoint displays
an asterisk (*) and Network Address displays
the computer name.
Grid Details
- Protocol
- Click the down arrow to select from a list of available
protocols.
- Endpoint
- Specify the endpoint, or address, that corresponds
to the specified protocol. (The format and content depend on the specified
protocol.)
- Network Address
- Displays the network address of the Server. (The
format and content depend on the specified protocol.)
- Authentication
- In
selecting a level of security, the needs of your site must be weighed
against potential performance compromises.
- The higher the protection level, the greater the
overhead required.
- The more often verification is requested, the more
time required to complete a process.
Select the appropriate level of authentication.
- None
- No authentication is required.
- During Connect (first call only)
- Authenticate when the user connects to the Server
on the first call. This security level ensures only that the connection
is valid and is from the proper user. No further authentication is
made and transferred data is not verified. This level of security
requires the least overhead and, of the available options, offers
the least security.
- Every Call
- Authenticate the user each time data is exchanged,
regardless of number of packets.
- Each Packet
- Confirm that each packet of transferred data is
received from the authenticated user. This level of security requires
more overhead and offers more protection than the Connect Level.
- Each Packet (Verify not changed)
- Confirm that each packet of transferred data is
received from the authenticated user and verify that it has not been
modified. This level of security requires more overhead and offers
more protection than the Packet Level.
- Each Packet (Verify not changed and Encrypt)
- Confirm
that each packet of transferred data is received from the authenticated
user, verify that it has not been modified, and encrypt the argument
value of each remote procedure call. This level of security requires
the most overhead and, of the available options, offers the most protection.
Update Product Configuration Files
Each workstation to connect to the Server
must use a Product Configuration File that includes Server endpoint
information. The Product Configuration File used by a workstation
is specified in Personal Options.
To
update Product Configuration Files with new information entered on
the Endpoints tab, click Update
Product Configuration File(s). Use the Choose Product
Configuration File dialog to list Product Configuration Files to update.
Note: If a Product Configuration
File to be updated is unavailable from the Choose Product Configuration
File dialog, the file must be updated manually on the corresponding
workstation.
Enter the name this server will be known
to clients
Enter
a name for the Server. The name you enter is added to the list of
available Servers displayed in action request editors that can use
a Server for remote processing.
Grid Details
- Product Configuration File
- Specify the complete path to each Product Configuration
File to be updated. To select from your system directories, click
the grid cell and click the browse button.
Each time
you enter a Product Configuration File, you are prompted for the corresponding
password. The password is set in Product Options.
- Password
- When you enter the password for a Product Configuration
File the first time, the password is saved for future updates to the
Product Configuration File. For security reasons, the password displays
as a series of asterisks (****).
- Edit
- Click Edit to display the
Product Options Editor for the corresponding Product Configuration
File.
- Update
- Select the check box to include the corresponding
Product Configuration File to be updated.
Update
Click Update to
update each selected Product Configuration File with the new endpoint
information.