What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Access denied on Windows XP: Connection could not be established (80070005: Access is denied - Hos

Votes:

0

Your Vote:

Up

Down

I have a small set up 4 XP computers, 1 Windows 7, and one server 2003. The only issue with adding WMI sensors is on the Windows XP boxes. I have enabled DCOM, verified the WMI registry entries, local securoty policy is allowing network access.

Could there be anything I am missing in PRTG?

This is a workgroup I tried the computer name:user:password and localhost:username:password in the prtg settings.

Thanks!

access denied wmi

Created on Jul 1, 2011 3:06:05 PM by  geojones2010 (50) 1 1



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hello,

Thanks for the reply! I had to disable "force guest". I used wirechark to see the error code and googled it. I found an article on a blog and changed the registry value:

my computer\ HKLM\system\currentcontrolset\control\lsa

That did the trick. What is strange to note is that this became an issue after imaging 3 machines (I use sysprep).

Best!

Created on Jul 5, 2011 6:10:49 PM by  geojones2010 (50) 1 1



3 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

the user you are "using" for the WMI Monitoring (which is entered in PRTG) is it a Local Admin on the target host? Or at least member of the "Distributed COM Users"-Group?

best regards.

Created on Jul 4, 2011 11:18:48 AM by  Torsten Lindner [Paessler Support]



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hello,

Thanks for the reply! I had to disable "force guest". I used wirechark to see the error code and googled it. I found an article on a blog and changed the registry value:

my computer\ HKLM\system\currentcontrolset\control\lsa

That did the trick. What is strange to note is that this became an issue after imaging 3 machines (I use sysprep).

Best!

Created on Jul 5, 2011 6:10:49 PM by  geojones2010 (50) 1 1



Votes:

0

Your Vote:

Up

Down

Thank you very much for your solution!

Created on Jul 5, 2011 7:30:44 PM by  Torsten Lindner [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.