Try connecting to this computer using any standard Windows administrative tool (such as Computer Management, or latest service pack for windows server 2008 r2 64 bit Services make sure that you usb cable types for printers are able to start/stop a services, enter Device Manager, Event Viewer sections.
Computer Management node and click, connect to another computer.
See, dCOM Configuration page for more information on how to configure dcom.Try setting the value to Timeout 5 seconds.If you the machine you are connecting to does not allow access with your credentials, is not a member of your forest, or is not joined to a domain; then there is one easy way to get all of your tools working.You may need to change the Authentication used when deploying to this computer.Configuration - Resolving "Access is Denied (5 Message when Connecting via DeviceLock Management Console.Use this method only if operating systems on both local and remote computer support Computer Management (for example both machines have Windows 2000 installed).3 out of 4 found this helpful.(Note: This setting is not available in XP or 2003).In these cases open up c and verify that the Log On As value.Verify PDQ Inventory or PDQ Deploy service is not running as LocalSystem.Comments, the error indicates that the account used for the connection does not have enough privileges on the target computer.Select Computer dialog and click,.
Access denied, incorrect privileges on the remote computer.
With [email protected] undelete installed and registered on a remote computer, and correct access to the remote computer and dcom is configured properly, all [email protected] undelete functions will run the same way as if it was a local machine.Possible Causes, this security error is usually caused by the user account not being an administrator of the target machine.If you use the command line tool for drive mapping, you can also create an authenticated RPC session between your machines which will be used in any access attempt you make after this.Error Messages, error, description, the RPC Server is not Available.Was this article helpful?Mistyped remote computer name, or software is not installed properly.If the target is a Windows 7 or Windows 2008 R2 and the Windows Firewall is turned off (and needs to stay off) then the user credentials that run the Background Service must have Administrative rights on the target machines.Modify Service Manager TCP Connection, if the problem persists after restarting the background service you may need to modify the Service Manager TCP Connection settings in Preferences Performance.Make sure that the account used for connection does have local administrative privileges on the target computer.Then you can connect to remote computer via local services or component management tools.
If you are not able to do it then check the following common reasons for this problem: - Simple File Sharing option is enabled (for Windows XP) on the remote machine - Windows (or any third-party) firewall blocking connection attempts - RPC and Remote Registry.