Remoting error

PowerShell Help
1

by gusac at 2013-03-02 21:31:05

Hi,
I just started with Powershell (thanks to Jason Helmick) and finding difficulty with invoke-command and remote PSSessions. I get the following error:
New-PSSession : [adcfmidc6] Connecting to remote server adcfmidc6 failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.


This is what I have verified so far:-
- Port 5985 is open
- WinRM service is running
- winrm quickconfig
- enable psremoting
- Execution policy set to Unrestricted
- Firewall is disabled, I can telnet to 5985 and TCPPing on port 5985
- Both the systems have Powershell v 3.0

The other cmdlet which have -computername parameter, work fine. The issue is only with the remoting.

Thank you!
by DonJ at 2013-03-02 21:40:07
What version ($PSVersionTable) is on the client and on the remote machine?
by gusac at 2013-03-02 22:00:01
Source(Win2008R2):
Name Value
---- -----
PSVersion 3.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.17929
BuildVersion 6.2.9200.16398
PSCompatibleVersions {1.0, 2.0, 3.0}
PSRemotingProtocolVersion 2.2


Destination (Win2012):
Name Value
---- -----
PSVersion 3.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.18033
BuildVersion 6.2.9200.16434
PSCompatibleVersions {1.0, 2.0, 3.0}
PSRemotingProtocolVersion 2.2


and this issue is with all the systems, So I’m suspecting sme configuration/restriction in the environment but not sure what.
by Aleksandar at 2013-03-11 21:09:03
Have you looked at "Large Kerberos tokens cause WinRM requests to fail" KB (http://support.microsoft.com/kb/970875)? It applies to WinRM 1.1, but I’ve heard some people having the same issue with the latest versions of WinRM as well (WinRM 3.0, in your case).
Try to change these two Registry keys, as it is described in a Resolution section, on one of your test computers and see if that helps:

HKLM:SYSTEM\CurrentControlSet\Services\HTTP\Parameters\MaxRequestBytes
HKLM:SYSTEM\CurrentControlSet\Services\HTTP\Parameters\MaxFieldLength