Extreme Networks Sentriant AG Software User's Manual page 370

Hide thumbs Also See for Sentriant AG:
Table of Contents

Advertisement

Endpoint Testing Conditions
Table 17: Conditions Affecting Endpoint Testing
Short name
Testing (NAC agent)
Testing (ActiveX plug-
in)
Installing ActiveX plug-
in
ActiveX plug-in
installation failed
Validating installation
Installation failed
NAC agent not active
Connection failed -
endpoint busy or file
and print sharing
disabled
Connection Failed
(unsigned SMB)
Connection failed—no
logon server
Connection failed—
endpoint/domain trust
failure
Connection failed—
timed out
Connection failed—
session setup
370
Description
Sentriant AG shows this status briefly while the endpoint is being tested by the NAC
agent.
Sentriant AG shows this status briefly while the endpoint is being tested by the ActiveX
plug-in.
Sentriant AG shows this status briefly while the ActiveX plug-in is being installed.
Sentriant AG shows this status when installation of the ActiveX plug-in failed. The
installation probably failed due to browser settings (see "Important browser settings" in
the Sentriant AG Installation Guide). The end-user has the option to retry or cancel
which presents the user with the next testing method specified on the End-user access
screen.
Sentriant AG shows this status while Sentriant AG is validating that the NAC agent is
working.
Sentriant AG shows this status when the NAC agent cannot be installed. This is likely
due to permission problems on the endpoint.
Sentriant AG shows this status when an endpoint that was previously running the NAC
agent is no longer running the agent. This is likely due to a firewall being turned on.
During the connection to the endpoint, the endpoint is not able to complete the
requested testing by Sentriant AG. This condition can occur when then endpoint is
busy running other processes or programs, or it might be in an overloaded condition.
Retesting the endpoint again at a later time generally resolves this problem.
Defragmenting the hard disk can also help this situation on slower endpoints.
Testing of the endpoint failed due to an unsigned SMB.
During the connection process, the endpoint was not able to validate the user ID and
password credentials supplied by Sentriant AG because the endpoint does not have
network access to any authentication servers. This can be due to a routing issue which
is not allowing the endpoint to reach the necessary servers on the network. Also, if
Sentriant AG is inline with the domain controller, you might need to open up the
appropriate ports (135 through 138, 445, 389, 1029) in the Sentriant AG accessible
endpoints configuration for your domain controller IP address. Once the endpoint can
reach the necessary servers, retest the endpoint.
The supplied credentials failed to authenticate because a previous trust relationship
established between the endpoint and the Windows directory is broken in some way.
Resolve this problem by adding the endpoint again as a member of the appropriate
Windows domain, then retest the endpoint.
Sentriant AG timed out while trying to connect to or retrieve information from the
endpoint. This could be due to a slow or saturated network, or the endpoint might have
been shutdown or rebooted while it was being tested by Sentriant AG. If the endpoint
is still on the network, retest it with Sentriant AG.
Sentriant AG shows this status when the RPC client had problems communicating with
the endpoint.
Sentriant AG Software Users Guide, Version 5.3

Advertisement

Table of Contents
loading

This manual is also suitable for:

Sentriant ag 5.3

Table of Contents