Novell ZENworks Network Access Control 5.0, Руководство пользователя

Страница: 145 / 534

Endpoint Activity 145
no
vd
ocx
(e
n)
24
Ma
rch 20
09
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) — Testing of the endpoint failed due to an unsigned
SMB.
Š Connection failed — no logon server — During the connection process, the endpoint was not
able to validate the user ID and password credentials supplied by Novell ZENworks Network
Access Control 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 Novell ZENworks Network Access Control is inline
with the domain controller, you might need to open up the appropriate ports (135 through 138,
445, 389, 1029) in the Novell ZENworks Network Access Control accessible endpoints
configuration for your domain controller IP address. Once the endpoint can reach the necessary
servers, 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 — Novell ZENworks Network Access Control 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 Novell ZENworks Network Access Control. If the endpoint is still on the
network, retest it with Novell ZENworks Network Access Control.
Š
Connection failed — session setup — Novell ZENworks Network Access Control shows this
status when the RPC client had problems communicating with the endpoint.
Š Failed testing — insufficient test privileges — The credentials Novell ZENworks Network
Access Control used to test the endpoint do not have sufficient privileges to read the registry or
enumerate the services. An easy way to debug this is to run
regedit
and connect to the
remote endpoint using the same admin credentials supplied to Novell ZENworks Network
Access Control. You should be allowed to browse the HKLM\Software and HKLM\System
keys on the endpoint. Retest the end point after increasing the credential permission levels or
using a different set of credentials with the necessary permissions.
Š Connection failed — no route to host — The endpoint is unreachable on the network by
Novell ZENworks Network Access Control. This can be due to either a network routing issue
or because the endpoint has powered off or is in the process of rebooting. Retest the endpoint
once the routing issues have been resolved or the endpoint is back on the network.
Š
Failed testing — patching endpoint — The endpoint failed testing and patching is in
progress.
Š Patching endpoint failed — The endpoint is unable to be patched.
Š
Patching endpoint complete — Patching of endpoint is successful.
Š Endpoint disconnected before could be tested — Novell ZENworks Network Access
Control shows this status when the endpoint disconnects from the network before testing could
be completed.