Share via

RPC server unavailable - Taskkill on a remote computer.

Anonymous
2024-04-10T01:18:28+00:00

Hi,
I'm trying to find a way to create a .bat file that kills processes on remotely connected machines.
I have 31 computers connected through a 100G mellanox switch, networked in a 10.10.10.X range with a 255.255.255.0 subnet.
Using CMD, I run a command: Taskkill /s "hostname" /IM "Process" but a get a return "RCP Server is not available".

Troubleshooting steps I've tried to solve this issue:

  • Restarted remote procedure call in services
  • Disabled all Firewall settings on every workstation
  • confirmed that remote registry and TCP/IP NetBIOS Helper are running
  • verified correct time and time zone settings
  • No DNS settings are configured.

Also worth looking into - There is a function if you go to Services>Action>connect to another computer, you should be able to access the services on a computer on the local network.
I get an error when trying to access a computer with an IP adres:

Windows was unable to open service control manager database on 10.10.10.X (the IP of the workstation) ERROR 5: Access is denied

Would anyone be able to help me out with this one?

Many thanks!

Windows for business Windows Client for IT Pros User experience Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-04-14T23:55:25+00:00

    Hello,

    May I have the output result of the command **Portqry.exe -n <ServerIP> -e 135**?

    Are there any obvious related errors under the System log and Applications and Services Logs? For example, event ID 1014. This event indicates that the RPC service failed to register with the endpoint mapper.

    On the local machine, run the command **wmic /node:<remote\_server> os get caption** and see if it returns the same error. If yes, then the problem is with the WMI connection. If no, then the problem is with the WMI query or script.

    Verify correct DNS settings on both machines. Make sure that they can resolve each other's hostnames and IP addresses correctly. You can use the commands nslookup <hostname> and ping <hostname> to test DNS resolution.

    Verify that the following services are running and set to auto start after restart on both machines:

    • Remote Procedure Call (RPC)
    • Remote Procedure Call (RPC) Locator
    • TCP/IP NetBIOS Helper
    • Remote Registry
    • Windows Management Instrumentation"

    Regards,

    Karlie

    0 comments