You probably hit the reverse dns error.
Windows WinRM ensure it is called properly by checking the dns entries and the hots in the request header.
Check that your dns entries (host and PTR) are correct, PTR record must point to the machine name, not to an alias.
You should also call the distant host by its name and not by IP address.
Hope this helps.
Le 2014-05-21 11:01, a écrit :
Hi, I need to run chef-client in windows machine from one windows machine using winrm/winrs. I had a code chef cookbook like windows_batch "backup" do cwd node['winrm_path'] code <<-EOH winrs -r:ip_address chef-client EOH end the above code(cookbook) will execute in windows machine from there it will run chef-client in another windows machine using winrs but errors occured. I enabled the winrm in both windows machines errors like : STDERR: Winrs error:The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config. or else Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. any one help me how to resolve this?? Thanks, Ganesan.A
Archive powered by MHonArc 2.6.16.