Extreme Networks AG200 User Manual page 140

Endpoint Activity
Installing test service—Sentriant AG shows this status briefly while the agent is being installed.
●
Install canceled—Sentriant AG shows this status when the end-user has cancelled the installation of
●
the agent.
Testing (installed test)—Sentriant AG shows this status briefly while the endpoint is being tested by
●
the agent-based method.
Testing (one-time test)—Sentriant AG shows this status briefly while the endpoint is being tested by
●
the ActiveX method.
Installing one-time plug-in—Sentriant AG shows this status briefly while the ActiveX plug-in is
●
being installed.
One-time plug-in installation failed—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.
Validating install—Sentriant AG shows this status while Sentriant AG is validating that the agent is
●
working.
Install failed—Sentriant AG shows this status when the agent cannot be installed. This is likely due
●
to permission problems on the endpoint.
Agent not active—Sentriant AG shows this status when an endpoint that was previously running
●
the agent is no longer running the agent. This is likely due to a firewall being turned on.
Awaiting ip transition—Sentriant AG shows this status during a transition from a quarantined IP
●
address and a non-quarantined IP address and vice versa.
Connection failed - endpoint busy or file and print sharing disabled—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.
Connection failed - unsigned SMB—Sentriant AG is not able to connect to the endpoint as it only
●
allows signed connections to Windows SMB services. This generally occurs on endpoints running
Windows 2003 Server. To resolve this problem, configure the endpoint to allow unsigned SMB
connections and then retest the endpoint. Alternatively, the NAC Agent or ActiveX browser plug-in
can be used to test the endpoint.
Connection failed - no logon server—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 server(s), retest the endpoint.
Connection failed - endpoint/domain trust failure—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.
Connection failed - timed out—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.
Connection failed - session setup—Sentriant AG shows this status when the RPC client had
●
problems communicating with the endpoint.
140
Sentriant AG Users' Guide, Version 5.0