You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working on upgrading our chef provisioning vsphere up to latest and am running into an issue where this library is erroring trying to get max_envelop_size_kb from the server. Can't seem to find anyone with the same issue, so maybe we just have something setup incorrectly. Any help would be appreciated.
Based on the stack trace, it looks like the failure is occuring in the rubyntlm library trying to parse the ntlm message type in the auth headers of the response. So this error would likely occur on any WinRM call and it just so happens that the envelope check is the first one.
I have never seen this particular error before but it suggests that something may be intercepting the WinRM traffic and injecting a different response so that the auth headers do not contain valid NTLM messages. A proxy would be a good place to start looking for suspects here.
Working on upgrading our chef provisioning vsphere up to latest and am running into an issue where this library is erroring trying to get max_envelop_size_kb from the server. Can't seem to find anyone with the same issue, so maybe we just have something setup incorrectly. Any help would be appreciated.
https://github.com/WinRb/WinRM/blob/master/lib/winrm/shells/power_shell.rb#L152
Server:
Window 2016 with Desktop Experience VM
I can telnet to port 5985. Firewall is off.
Error Output:
WinRM Config:
The text was updated successfully, but these errors were encountered: