Introduction
In this article, we will discuss how to resolve the PsExec access error (23 H2 and 24 H2) in Windows 10 and Windows 11. PsExec is a powerful tool from Microsoft that allows administrators to execute commands and applications on remote systems. However, some users encounter issues when trying to use PsExec, particularly when accessing network paths. In this guide, we will cover the causes of the error and provide steps to resolve it.
Understanding the Error: "Could not access COMPUTER-NAME: network path not found"
When attempting to use PsExec to access a network path on a remote system, some users may encounter the error message "Could not access COMPUTER-NAME: network path not found" (error codes 23 H2 and 24 H2). This error can occur due to several reasons, including:
- Incorrect network path syntax
- Network connectivity issues
- Insufficient permissions on the remote system
- Firewall or antivirus software blocking the connection
Checking Network Connectivity
Before attempting to resolve the PsExec access error, it's essential to check the network connectivity between the local and remote systems. You can do this by:
- Pinging the remote system using the IP address or hostname.
- Checking the firewall settings on both the local and remote systems.
- Ensuring that the required ports are open.
Checking Permissions
If the network connectivity is established, the next step is to check the permissions on the remote system. You can do this by:
- Logging in to the remote system using an administrator account.
- Checking the NTFS permissions on the network share.
- Ensuring that the user account used to run PsExec has the necessary permissions to access the network share.
Modifying PsExec Options
If the network connectivity and permissions are in order, you may need to modify the PsExec options to resolve the access error. You can do this by:
- Using the -s option to run the remote command as a different user.
- Using the -accepteula option to accept the End User License Agreement.
- Using the -h option to specify the fully qualified domain name of the remote system.
Summary
In this article, we discussed how to resolve the PsExec access error (23 H2 and 24 H2) in Windows 10 and Windows 11. We covered the causes of the error and provided steps to check network connectivity, permissions, and modify PsExec options. By following these steps, you should be able to successfully access network paths using PsExec.