Enter-PSSession to remote server fails with “cannot find the computer”

三世轮回 提交于 2019-11-30 17:14:49

After talking to our domain admin I think I found the cause of the problem.
The server is in a resource domain which only has a one way trust to the main OU.
This explains why I can do PS remoting from the server to the clients but not vice versa.
I found that I can use the IP address with the -Credential option in my case though which isn't nice but an acceptable workaround.

In my case DNS was was pointing to the right IP yet there wase a typo in the hostname so basicaly the parameter -Computername and the actual hostname didn't match.

This is most likely caused by your netbios name being different from the server's hostname. Try to connect with the netbios name instead.

  • Determine the correct name by running the following command in powershell:

"$env:COMPUTERNAME.$env:USERDNSDOMAIN"

run winrm quickconfig from a powershell session on the remote machine

Check Domain Replication and see if the computer object is where its supposed to be. This is something I had to deal with for computer objects that were not replicated from one domain controller to another.

There is a self-signed certificate under local computer / RDP ... make sure there is one there for WinRM service to use.

See if you can find out if there is any firewall that might be blocking the WinRM ports.

Hope it helps.

I know its very late but i am putting my fix to the few sites that experienced the same issue. for me it was a duplicate computer name in the root domain. found it by running setspn -f -q */servername. this popped up the server name in multiple domains. deleting the invalid machine from the root AD and root dns, and i was up and running.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!