[chef] Re: Re: Re: winrm

[Nikhil Shah < >]

Daniel, that could be a possibility. I migrated from chef hosted to chef open source, I'll touch base with you tomorrow -  

Thanks,

Nikhil Shah

On Sep 18, 2013, at 6:16 PM, Daniel DeLeo < "> > wrote:

On Wednesday, September 18, 2013 at 2:03 PM, Paul Morton - BIA wrote:

Nikhil - This typically means that you have the wrong username or password specified. 401 is un-authorized.

On Sep 18, 2013, at 2:03 PM, Nikhil Shah < "> > wrote:

Anyone seen this error message? I had it working (of course with the hosted solution); however, this is the first windows server I'm launching hosting my open source server in house:

ERROR: Failed to authenticate to ["192.168.XX.XX"] as administrator

Response: Bad HTTP response returned from server (401).

DEBUG: Adding 192.168.XX.XX

DEBUG: :session => :init

DEBUG: :relay_to_servers => cmd.exe /C %TEMP%\bootstrap-5449-1379538020.bat

DEBUG: :relayed => 192.168.XX.XX

DEBUG: 192.168.XX.XX => :run_command

ERROR: Failed to authenticate to ["192.168.XX.XX"] as administrator

Response: Bad HTTP response returned from server (401).

Nikhil Shah / System Administrator

To clarify, your authentication credentials are being rejected by the Chef server. So either you have a bad client key or node name.

To test things out with knife, you can try something like `knife node list -s CHEF_SERVER_URL -u CLIENT_NAME -k PATH_TO_CLIENT_KEY`

-- 

Daniel DeLeo