March 28, 2024, 05:13:22 PM

Author Topic: (Error: 5) during Registry Read  (Read 10004 times)

helsby

  • Member
  • *
  • Posts: 3
(Error: 5) during Registry Read
« on: January 06, 2006, 06:47:15 PM »
The scan status reads \"Access is denied. (Error 5) during Registry Read and the only thing returned is the mac address, ip address and the mac owner
However I can connect to c$ and also to the registry remotely.

Any ideas?

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2702
  • Dayton, Ohio, USA
(Error: 5) during Registry Read
« Reply #1 on: January 06, 2006, 08:23:44 PM »
Hi there.  Actually a \"Registy Read\" in NEWT means it tries to open the following remote registry path:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall

Is this remote machine Windows XP?  If so, the default installation of XP chooses the \"Guest only\" sharing and security model.

Please try changing the model to \"Classic\" and let us know if that helps.

A screenshot detailing how to change the option is shown here:
http://www.komododigital.com/winsecurity.htm

A reboot may be required.

jmoreno

  • Member
  • *
  • Posts: 1
(Error: 5) during Registry Read
« Reply #2 on: March 16, 2007, 01:55:09 PM »
I have the same problem.
I have about 130 machines in my network and this problem appears when i upgrade my windows 2000 prof. system to windows xp prof. SP2.

I saw my configuration in \"Local security settings\" and it is correct, in Classic mode.

However, i can not modify this option...



This computer is in domain, but the user is administrator of the domain, and in this computer.

Any other idea?

Thank you very much.

Juan Moreno.

bdhuser

  • Member
  • *
  • Posts: 3
(Error: 5) during Registry Read
« Reply #3 on: March 16, 2007, 03:21:56 PM »
Jmoreno-

My guess is you need to modify the setting in Group Policy (being in a domain).

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2702
  • Dayton, Ohio, USA
(Error: 5) during Registry Read
« Reply #4 on: March 16, 2007, 05:19:17 PM »
We have seen this issue in the past and it seems to be a bug incurred during the upgrade process.

Please see the following Microsoft Knowledge Base article to correct this:

\"This behavior may occur if the remote computer was upgraded from Microsoft Windows 2000 to Windows XP Professional.\"

http://support.microsoft.com/kb/892192