Error: 'Unable to Connect to Agent' when running a Windows report. (NETIQKB31986)

  • Document ID:7731986
  • Creation Date:02-Feb-2007
  • Modified Date:29-Apr-2008
    • Micro Focus Products:
      Secure Configuration Manager

Resolution

fact
VigilEnt Security Manager 3.x

fact
VigilEnt Security Agent for Windows 3.x

fact
VigilEnt Security Agent for Windows 2.x

symptom
Error: 'Unable to Connect to Agent' when running a Windows report.

cause

The target machine in VigilEnt Security Manager (VSM) may be a member of a workgroup, a resource domain, or a standalone machine.  To determine if the machine is part of a workgroup or standalone machine, right-click Network Neighborhood (on the target machine) from the desktop and select Properties.

If the machine is not a member of the same domain where VSM is running, and the VigilEnt Security Agent for Windows is configured to perform domain-membership checking, reports and actions against the Agent will fail.



fix

To avoid receiving this error, disable domain-membership checking on the Agent by performing the following steps:

  1. Navigate to Start | Run, and type regedit.  The Registry Editor window will open.
  2. Naviage to HKEY_LOCAL_MACHINE\SOFTWARE\PENTASAFE\VSANT.
  3. Right-click on HKEY_LOCAL_MACHINE\SOFTWARE\PENTASAFE\VSANT select New from the menu, and then select DWORDValue.
  4. Change the name of the DWORD value to: DomainCheck, and Leave the value set to 0.
  5. Close the Registry Editor to save changes.
  6. Stop and restart the VigilEnt Security Agent for Windows service for the settings to take effect.

 



note
<B>WARNING:</B> Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. NetIQ cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. <P>Make sure that you backup your Registry prior to making any changes.

note
Note: The agent will work on a workgroup machine for same-machine auditing, but will not be able to do proxy auditing of another machine. This is because proxy auditing only works for systems that are members of domains (cross-domain auditing is also possible if the right trust-relationships have been established).

Additional Information

Formerly known as NETIQKB31986