Article ID: 3660, created on Feb 8, 2008, last review on May 11, 2014

  • Applies to:
  • Helm 3

Resolution

Problem/Summary
Helm fails the system diagnostic with the following issues:

Registry Access Failed Helm was unable to connect to the registry of 'SERVERNAME'. Please ensure that the Remote Registry Service is running on this server and that the communication IP for this server (MACHINE IP) is correct.

File System Access Failed Helm was unable to connect to the file system of 'SERVERNAME'. Please ensure that File and Printer Sharing is enabled on your server's network interface and that the communication IP for this server (MACHINE IP) is correct.

Helm Admin Access Failed Helm was unable to find the NT user account that will be used by Helm to connect to server 'SERVERNAME'. Please ensure that the NT account specified in the Helm Configuration Tool is present on this server and that the password is correctly set.

Solution

1.) Ensure the Remote Registry service is running (under Administrative Tools -> Services).

2.) Ensure that File and Print Sharing is enabled (go to your LAN connection properties and make sure the box is ticked).

3.) Ensure the Helm Admin passwords are synched (go to Computer Management -> Users -> HELM_ADMIN -> Set password and ensure this is the same password that you enter under the Helm Configuration Tool -> System Identity tab).

NOTE FOR NAT BASED USERS:

If you have disabled TCP and UDP port 445 on the NIC using TCP/IP packet filtering, then you will still get the above errors. If you enable these ports, everything will work correctly.

110556ad4b9f1c73a3682661cd1dca89 152090ff5e9a05ea7e1cf0c248449638 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF