August 12, 2016 at 1:10 pm #50138
I am taking PSSESSION using CredSSP Authentication(Already configured CredSSP Client and Server),But getting the below Error :
$Session = New-PSSession -ComputerName "Test" -Authentication CredSSP -Credential $Cred
New-PSSession : [Test]Connecting to remote server[Test] failed with the following error message : The request is not supported.
CategoryInfo : OpenError : (System.Management....RemoteRunspace:RemoteRunspace) [New-PSSession].PSRemotingTransportException
FullyQualifiedErrorId : 50,PSSessionOpenFailed
Kindly help me to fix this!!
August 12, 2016 at 1:13 pm #50140
How are these machines related? Are they in a domain together? Not in a domain? Is the destination computer's name exactly as listed in DNS and/or Active Directory?
August 12, 2016 at 1:22 pm #50142
Also, what PowerShell versions are you running on the client and server?
August 12, 2016 at 1:40 pm #50150
So, "Secrets of PowerShell Remoting" gets into some of these details, but...
Why not just allow the default Kerberos protocol to be used? However, note that you must connect using the target's canonical AD name, in order for the mutual authentication to function. You can't use IP address unless you take different steps, because the computer can't be "found" in AD by IP.
But CredSSP has a number of requirements; see the "Second Hop" section in https://devopscollective.gitbooks.io/secrets-of-powershell-remoting/content/manuscript/accessing-remote-computers.html. And, double check the CredSSP configuration – the target must be in "Server" mode, the origination must be in "Client" mode, and must specify the server as a trusted delegate.
May 15, 2018 at 6:22 am #100566
Was this sorted for you? I am getting the same issue and not able to solve this. This used to work for me before. Suddenly this has broken and I am getting the error you got.
May 15, 2018 at 7:35 am #100579
I ran into the same problem, and spent quite some time trying to find the answer. I was trying to create a CredSSP session from one Windows 10 machine to another. In the past this always worked perfectly for me, but now, a normal PSSession worked, but a CredSSP session threw the Request not supported error.
The clue came when I tried to RDP into the Windows 10 machine. In this case, an error dialog was shown indicating that it could be because of an update of 'Oracle CredSSP encryption' (free translation, I got it in Spanish). And a link to https://go.microsoft.com/fwlink/?linkid=866660 was provided.
The cause of the problem was connecting from Windows 10 1803 to Windows 10 1709. The solution was simple:
– either upgrade the Windows 10 server machine to 1803
– or create a policy (or registry key) as per https://support.microsoft.com/en-us/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018, allowing for 'vulnerable' connections.
I didn't have time for upgrading, so my quick and dirty choice was executing:
$RegKeyPath = 'Registry::HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters\' $RegKeyName = 'AllowEncryptionOracle' New-ItemProperty $RegKeyPath -Name $RegKeyName -Value '2' -PropertyType 'DWORD' -Force
Hope this helps
May 31, 2018 at 5:18 am #101475
Thank you Harmen and Jon. I would not have been able to figure this without your help. The update was the issue. With your help, I was able to sort it out 🙂
You must be logged in to reply to this topic.