RMA: 301 - Cannot connect to remote registry

Glen · Post by **Glen** » Mon Oct 02, 2006 3:00 pm

Hi Alex and co.
I've just installed an RMA agent on a clients server that is NATed through to the server which the RMA manager runs on. RMA connection works and I'm able to create various tests...Except CPU Utilization. The reply says "RMA: 301 - Cannot connect to remote registry" I entered the UNC path with all appropriate details..

Server is a terminal server running Windows 2003. I checked the services and remote registry is running.

Can someone help?

Thanks

G

KS-Soft Europe · Post by **KS-Soft Europe** » Mon Oct 02, 2006 3:14 pm

CPU Usage test needs administrator's privileges.
If RMA started as service, you should specify user account with administrator's rights using standard Services applet.

Regards,
Max

Glen · Post by **Glen** » Mon Oct 02, 2006 4:34 pm

Are there any other reasons why it wouldn't work? As the account which I use is an admin account.

We changed the administrator username for security reasons (yeah i know the SID still stays the same) but could this have a possible impact?

I'm also getting 'access is denied' for setting up some of the UNC tests, which makes me think the two are related to the username...

KS-Soft · Post by **KS-Soft** » Mon Oct 02, 2006 5:10 pm

Are there any other reasons why it wouldn't work?

There are a lot of possible reasons. Please make sure
1) RPC service is started on the systems
2) Remote Registry Service started on target system (Ok, this was checked)
3) PerfOS.DLL is enabled on target system
4) There are no firewalls between 2 systems (probably its not a problem in your case)
5) admin account has KEY_READ access to the following registry key on target system HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows_NT\CurrentVersion\Perflib

Regarding item #3: Microsoft provides "Extensible Counter List" utility: http://www.microsoft.com/downloads/deta ... laylang=en
This utility displays list of DLLs that are used to support Performance Counters, using the utility you may disable/enable specific DLLs.

We changed the administrator username for security reasons (yeah i know the SID still stays the same) but could this have a possible impact?

Do you mean test worked fine before you have changed password?

Regards
Alex

Glen · Post by **Glen** » Sun Oct 08, 2006 8:04 pm

Hi,
Thanks for that. I have checked all those settings. None of which seem to be out of order...
I'm still no closer to getting this resolved.

It works perfectly on the same agent but a different computer that I'm running the CPU test from...I don't understand that

Glen

KS-Soft Europe · Post by **KS-Soft Europe** » Mon Oct 09, 2006 12:40 am

Glen wrote:We changed the administrator username for security reasons (yeah i know the SID still stays the same) but could this have a possible impact?

So, did you change the admin account? I think you should retype admin account's name and password for RMA service in Services applet. It might help.

Regards,
Max

Glen · Post by **Glen** » Tue Oct 10, 2006 2:50 pm

Yes I did,
Also created another domain administrator account and tested that from a different server with the same test successfully.

KS-Soft · Post by **KS-Soft** » Tue Oct 10, 2006 7:46 pm

Sorry, I don't know other reasons why Windows can reject request

Try to ask Microsoft.
Also, can you try to install RMA on that server (that does not accept request)? Most likely it will work if you start agent under local system account and setup CPU Usage test to check "local system" (local for the RMA of course)...

Regards
Alex

Glen · Post by **Glen** » Sun Oct 15, 2006 5:55 pm

Hi Alex,
We put an agent locally on the server and it worked. The problem was because the server was running win2k web edition which gave all sorts of issues due to RPC lockdowns.

Thank you for your help

KS-Soft · Post by **KS-Soft** » Mon Oct 16, 2006 10:27 am

You are welcome