CODEWITHSUNDEEP
powershell-3.0powershell-remoting
user333869
user333869

Reputation: 577

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

My desktop is win7 and I am trying to connect to a server 2012.
Both hosts are on the same domain.

If I do:

Enter-PSSession -ComputerName *ServerName***

I get the following failure message from winrm

Enter-PSSession : Connecting to remote server xxx failed with the following error message : WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer xxx. Verify that the computer exists on the network and that the name provided is spelled correctly.*

It doesn't matter if I use just the server name or if I enter it fully qualified.

Both systems show $PSVersionTable.PSVersion 4 0 -1 -1

I have tried the various troubleshooting hints that I found i.e.
run Enable-PSRemoting -Force and also set TrustedHosts = * on both sides.
I also disabled the firewall service on both sides.
When I try to Enter-PSSession from the server to my desktop it works as desired.
But from my desktop to the server I always get the error message that the computer cannot be found.

Upvotes: 25

Views: 75068

Answers (5)

Adi Feldgajer
Adi Feldgajer

Reputation: 21

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. I 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.

Upvotes: 2

Ian Collins
Ian Collins

Reputation: 71

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"

Upvotes: 7

yaro137
yaro137

Reputation: 19

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.

Upvotes: 1

user333869
user333869

Reputation: 577

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.

Upvotes: 11

Douglas Tripple
Douglas Tripple

Reputation: 13

run winrm quickconfig from a powershell session on the remote machine

Upvotes: 1

Related Questions