The reg key is located here: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurePipeServers winreg
Ensure that the Administrators group has, at the very least, Read Access. Furthermore, Windows Server 2003 and Windows XP both share a setting where the LOCAL SERVICE account needs to have Read Access to the winreg key. This is due to the fact that Microsoft changed some behavior here and no longer use the LOCAL SYSTEM to log onto the Remote Registry Service. If LOCAL SERVICE is removed from having access to the winreg key, then HFNetChkPro cannot perform a scan.
· The customer can also test remote registry access from the console.
o Open regedit on the console machine
o Click File and the Connect Network Registry
o Type in the name or IP of the target machine that is getting the error 501.
o Supply the credentials you are using to scan this machine
o If connected, navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurePipeServers winreg
o Can you navigate to this key?
Hi, thanks for the quick response. I checked the registry key above on the Windows 7 computer. LOCAL SERVICE has read access to the winreg key. The Administrators group has Full Control and Read Access to winreg. I used an account with administrative credentials to attempt the Connect Network Registry above and could not connect to the machine from the console. Any help is appreciated.
Is the target machine a domain member? Is the Netlogon service started? If you have a GPO enforced, you may want to take a closer look at any restrictions in place.
I too am having this issue on three windows 7 machines. The rest of my machines are fine. You should know that we are NOT in a domain environment and I have admin rights on the 3 machines in question. I have also checked that remote registry service is running and file sharing is turned on. I can test the existence of them and they are found. I just cannot connect. I've tried the net use command, unsuccessfully.
You will need to be able to gain administrative access to the remote target's registry in order to successfully scan the machine using Protect. You will also need to be able to remotely access the target machine's root drive share (i.e. IPC$ or C$). You may need to review the UAC settings on the targets in question (UAC will affect remote restrictions). Please review the topic 'Scanning Prerequisites' within our Administration Guide (also availabe via the 'Help>Index' menu for a detailed overview.
If you are still unable to resolve the issue, we would urge you to contact Support directly, via any of the contact methods outlined here: