Cannot Connect to Remote Registry

[gmail2]

This problem seems to kind of intermittent - possibly something to do with the image that we've deployed. Basically, I cannot connect to any remote registry - even though the remote registry service is running on the local PC. It will add the computer in but as soon as I try to expand the hives I get "Error while opening key".

Also, I cannot connect to remove Event Viewers - again, it gets added into the MMC but I get permission denied when I try to open it. On some of our member servers, I also get this error, and on others it works fine. I'm running all this as domain admin, so are there some user rights I need to be looking out for? We do have quiet alot of user rights assigned through group policy.

Anybody got any ideas?

Irish Poetry - Karen O'Connor
Get your Irish Poetry Published
Garten und Landschaftsbau

 

[linney]

You receive an "Access denied" or "The network path was not found" error message when you try to remotely manage a computer that is running Windows XP Service Pack 2

http://support.microsoft.com/default.aspx?kbid=840634&product=windowsxpsp2#kb1

 

[gmail2]

Sorry, should have mentioned ... these PC's are SP1, not SP2. Any other ideas?

Irish Poetry - Karen O'Connor
Get your Irish Poetry Published
Garten und Landschaftsbau

 

[linney]

How to Manage Remote Access to the Registry

http://support.microsoft.com/default.aspx?scid=kb;EN-US;314837#appliesto

Free Tools Save Hours

http://www.langa.com/newsletters/2004/2004-05-31.htm#9

 

[mlconley]

You may need to authenticate to the remote computer via resource sharing before you can access it's registry.

I always log into my local machine rather than the domain and I won't automatically authenticate to other computers because my login is not a local admin account on other computers. Therefore, I haven't automatic access to that computer's registry.

 

[mlconley]

Also, VNC and other remote control programs have value, and I use and love them, but if you have security on the network, a standard user cannot write to the registry, this means that the standard user has to log out so I can log in as admin and edit the registry - or I can do my work without interupting them. This also works for all remote computer management.

You might also consider PSTOOLS from sysinternals because you can do some neat things like remotely shutting down large groups of computers and remotely running defrag, adding registry keys, software updates and so on.