unable to connect remotely with powershell to a non domain pc

2020-02-13

Question

_{Thursday, February 13, 2020 4:59 AM}

Hello,
I have 2 win10 pcs both connected to the same switch/router combo (a netgear n-750).
They can ping each other, and i can use the windows "map a network drive" option from each pc to each pc.
But when i enter this at the power shell prompt, i get this error:

PS C:\ New-PSSession -ComputerName win10-pc1
New-PSSession : [win10-pc1] Connecting to remote server win10-pc1 failed with the following error message : WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer win10-pc1. Verify that the computer exists on the network and that the name provided is spelled correctly.
For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1

New-PSSession -ComputerName win10-pc1

+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
+ FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed

...
I have tried many things from many documents ive found online, but nothing seems to fix the problem i'm having.
I also have a win2016 server, and i can log into the server/domain from each of the 2 win10 pcs, and when either pc is logged into the domain, then the powershell remote options work almost normally.
Almost meaning that the powershell ISE will connect normally, but then if i run any command i will get a different error:

Remote host method get_WindowSize is not implemented.

But if i run the regular powershell window, all of the commands work normally.
the regular powershell I have does not have the same 'intellisence' that the ISE version does, and that makes it much harder to use.
The problems while logged into the domain are probably caused by different things (but i wanted to include that in case they are related), and my main goal (aside from understanding how powershell remoting works and can be configured) is to connect remotely to pcs that are not part of a domain.
I feel I am missing something very fundamental.
If anyone can help or point me in the right direction, I would be extremely grateful.
thank you
-Michael

All replies (9)

_{Friday, February 14, 2020 4:22 AM}

HI
I am researching your issue ,thanks for your waiting.

Best Regards
Andy YOU
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Saturday, February 15, 2020 4:08 AM}

that's great, thank you

_{Saturday, February 15, 2020 3:43 PM}

HI
thanks for your reply.

1.can you enter winver in command prompt on both win10 computers and look the os version and os version number ?[for example windows 10 enterprise 1809 (os build 17763.316)]
are only remote win10 joined AD domain or only local win10 joined AD domain?
are w2016 server joined AD the same domain as one of the win10 computer ?

2."WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer win10-pc1"
is there any enent log about your issue in
windows log\application
windows log\system
applications and services log\microsoft\winodws\windows remote managment\operational
Troubleshoot WinRM with PowerShell—Part 1
https://devblogs.microsoft.com/scripting/troubleshoot-winrm-with-powershellpart-1/

3."I also have a win2016 server, and i can log into the server/domain from each of the 2 win10 pcs, and when either pc is logged into the domain,"
do you mean you can remote access to win2016 server successfully by using below powershell command on both win10 client?
New-PSSession -ComputerName win2016

4."my main goal (aside from understanding how powershell remoting works and can be configured) is to connect remotely to pcs that are not part of a domain."
i think we can also post 3 problems in Windows PowerShell forum.
https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverpowershell

Best Regards
Andy YOU
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, February 19, 2020 4:27 AM}

HI
have you solved your issue?

Best Regards
Andy YOU
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Tuesday, February 25, 2020 2:43 AM}

hello Andy,

1000 pardons for my delay, Im also looking for a job, and I was very sidetracked on some opportunities, some of which were for naught and im still waiting on others.

no, this is not solved yet.

Thank you very much for your replies, i am going to get back to this tomorrow as I am totally wiped out and tired at the moment, but I cannot wait to pick this problem up again.

thank you very much again for your replies (I must stop letting any posts go unanswered for so long!)

-michael

_{Thursday, February 27, 2020 1:25 AM}

Hello Andy,

Thank you, too, for waiting / being asynchronous at times...

I gathered this extra info from these pcs.

note: I put the wrong pc name's stuff in my first post, but the same errors happen with the correct computer name.

To 'refresh' the pc names and the errors:

The full names of the 2 pcs I am using are win10-pc2 and home-pc4.

To make it easier to type, I usually refer to them as just pc2 and pc4, but their full names appear in errors and what not.

the win2016 server pc name is server2

:::::::::::::::::::::::::::::

regrading question 1, the pc's os versions:

pc2, winver says this: windows 10, version 1909, os build 18363.657

pc4, winver says this: windows 10, version 1903, os build 18362.657

:::::::::::::::::::::::::::::

regrading question 1, the domain questions:

I don’t understand exactly what your asking, but I think this is on the right path:

Both pc2 and pc4 are able to log into the win2016 domain, which is called d2.local.

When I open the system properties screen for both pcs, it says the full computer names are "win10-pc2.d2.local" and "home-pc4.d2.local".

But, for this problem/test, I am logging into each pc locally with local user accounts (not the domain user accounts that I use when I log into the domain), and currently the local user accounts have admin rights.

:::::::::::::::::::::::::::::

regarding question 2, is there anything in the event logs:

-I looked in these logs:

=====

applications and services log\microsoft\winodws\windows remote managment\operational

-every time I try to connect, I get the same sequence of 19 events

-I used this powershell statement to get this list (that is a dynamite article you put the link to in your reply!)

PS C:\ Get-WinEvent -LogName Microsoft-Windows-WinRM/Operational | Select-Object -first 19 | Format-list

TimeCreated : 2/26/2020 6:34:16 PM