United Technologies TruVision SVR Guía de usuario descargar pdf (Pagina 14)

TruVision SVR Network Configurations

14 TruVision SVR System User Guide

• UDP Port (5000)

ICMP Settings:

• Allow incoming echo requests

Windows Authentication Model

The process used by Windows to verify a client’s identity is called authentication. In order to properly

set up a system or troubleshoot an existing installation, the first step is to determine the identity of the

client attempting to connect to the server.

Here are some general guidelines:

• Interactive processes always run with the identity of the user that launched them, or they can be

launched with credentials of a different user through the “runas” command.

• Services typically run under the SYSTEM account (or another account specified through

Windows Services).

When a client connects to a remote server, the client’s identity is sent to that machine, and that system

authenticates the client. This process can have several outcomes depending on which user account is

used by the client:

• If both machines are in a domain and the domain user is used, then the server will use the domain

controller to authenticate the incoming client connection.

• If the client used the local machine account and the same local account with the same password

exists on the server, then that account will be used.

Note: If the same local account exists on the server, but the password is different, the client’s

connection attempt will immediately return failure. It will not default to the method

described next.

• If the client used the local machine account and an account with that name is unknown to the

server, an incoming connection will be assigned the ANONYMOUS user on the remote machine.

Note: There is a security policy which allows ANONYMOUS users to be part of the

EVERYONE group, but by default the EVERYONE group only includes users whose

identity was established in some way (i.e., not anonymous).

Local vs. Remote Permissions

Extended Windows security model, introduced in Windows XP SP2 and Windows 2003 Server SP1,

split permissions listed in the previous section into two separate parts: local and remote. This allows

system administrators more granular control over object security.

As the client-server connection is analyzed, the location of the components will determine which

permissions (launch, activation, and access) will be used. If both components are running on the same

machine, local permissions will be used. Otherwise, Windows will use remote permissions.

1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 43 44

Sin comentarios

United Technologies TruVision SVR Guía de usuario Pagina 14