HP 800 User Manual page 176

Endpoint Activity
Test Status States
4-12
Awaiting ip transition – NAC 800 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 NAC 800. 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 – NAC 800 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. Alterna-
tively, 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 NAC 800 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 neces-
sary servers on the network. Also, if NAC 800 is inline with the domain
controller, you might need to open up the appropriate ports (135
through 138, 445, 389, 1029) in the NAC 800 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 relation-
ship 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 – NAC 800 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 NAC 800. If the
endpoint is still on the network, retest it with NAC 800.
■ Connection failed - session setup – NAC 800 shows this status when
the RPC client had problems communicating with the endpoint.