Geek asks and answers

Why get-process -computername return a cannot connect to a remote machine error?

I can run the following command on a specific computer, and it can return a list of processes on several target computers, but it returns the error "Could not connect to the remote machine" on the same machine.

get-process -ComputerName 192.168.1.101

  • None of the target machines have an installed installation.
  • The computer running the powershell script on kernel has 2.0 installed.
  • I have administrator privileges on all machines.
  • Target computers that can remotely return a list of processes are the 2003 Standard Edition Server Service Pack 1 (SP1).
  • The final machine that does not return the process list remotely is the 2003 R2 Standard Edition SP2 server.

What would prevent me from getting a list of processes from a remote machine using powershell?

+2
source share
2 answers

It turns out that on the machine that was returning the error, the remote registry service was not started. As soon as I started this service, the error "Could not connect to the remote machine" disappeared. This blog post helped me find a solution http://sebastienlachance.com/post/ProcessGetProcesses-common-errors.aspx

+5
source

I think it uses WMI, so if the service is down, this will do it. Can you execute Get-WMIObject requests on these PCs at all?

0
source

More articles:


All Articles