Hi guys. I am trying to access the remote computer on the same domain to make some configurations. Basically, what I need is just to update some drivers.

I have configured GPO to enable remote access. But I am still can not connect to any computer on the same network.

If I am doing this via Computer Manager → Connect to other computer and I am getting this error Unable to access the computer. Make sure that this computer is on the network, has remote administration enabled and is running the Plug and Play and Remote registry services.

I have checked everything. Remote administration is enabled, Plug and Play and Remote registry services are running.

Also if I am trying Enter Pssession using PowerShell I am getting this.

Enter-Pssession : Connecting to remote server failed with the following error message : The WinRM client
cannot process the request. Default authentication may be used with an IP address under the following conditions: the tr
ansport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided. Use winrm.cmd to
configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated.

I am frustrated guys do you have any thoughts what could be wrong?

10 Spice ups

Edit: you did mention it was on the same network*

My first thought would be firewall? Do you have a software firewall enabled?

1 Spice up

The error message is giving you most of what you need. This isn’t just about the TrustedHosts list, it’s saying that in order to use an IP address with the default authentication scheme, you have to ALSO be using HTTPS (which isn’t configured by default) and provide explicit credentials.

The default authentication mechanism is Kerberos, and it wants to see real host names as they appear in AD. Not IP addresses, not DNS CNAME nicknames. Some folks will enable Basic authentication, which is less picky - but you should also set up HTTPS since you’d otherwise pass credentials in cleartext. Enable-PSRemoting only sets up HTTP.

Adding names to your hosts file won’t work. This isn’t an issue of name resolution; it’s about how the mutual authentication between computers is carried out.

Additionally, if the two computers involved in this connection aren’t in the same AD domain, the default authentication mechanism won’t work. Read “help about_remote_troubleshooting” for information on configuring non-domain and cross-domain authentication.

From the docs at about_Remote_Troubleshooting | Microsoft Learn

well you told us everything except what OS your computers are using.
and how are you doing to remote to them.

Yes they are on the same network.

Ok maybe this works connecting via PS. But I am not able to connect via DESKTOP MANAGER neither. Just the MSTSC works. So, I don`t think this is has something with the protocols. For me looks like a GPO is not set properly.

That’s a deny error.
Are you running the MMC with administrator creds for the remote machine?

Yes I do. I think something is not properly set up with GPO. But can not figure out what is the issue.

You must login to the computer locally to utilize Device Manager. That functionality was removed.

as an alternative you could try:

Yes seams that is the issue.

But that device manager tools is not working on remote machine neither.

What error do you get when you opening device manager console on the remote machine?