Winrm


#1

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
nshah@theorchard.com

The Orchard® / www.theorchard.com

t (+1) 212.308.5648 / f (+1) 212.201.9203
23 E. 4th St., 3rd Fl / New York, NY 10003

The Daily Rind™ / www.dailyrindblog.com
Facebook / @orchtweets

Privileged And Confidential Communication.
This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and © are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.


#2

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 nshah@theorchard.com 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
nshah@theorchard.com

The Orchard® / www.theorchard.com

t (+1) 212.308.5648 / f (+1) 212.201.9203
23 E. 4th St., 3rd Fl / New York, NY 10003

The Daily Rind™ / www.dailyrindblog.com
Facebook / @orchtweets

Privileged And Confidential Communication.
This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and © are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.


#3

thats very odd, b/c i copied and pasted into windows login and it works.

On Wed, Sep 18, 2013 at 5:03 PM, Paul Morton - BIA
pmorton@biaprotect.comwrote:

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 nshah@theorchard.com 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
nshah@theorchard.com

The Orchard® / www.theorchard.com

t (+1) 212.308.5648 / f (+1) 212.201.9203
23 E. 4th St., 3rd Fl / New York, NY 10003

The Daily Rind™ / www.dailyrindblog.com
Facebook / @orchtweets

Privileged And Confidential Communication.
This electronic transmission, and any documents attached hereto, (a) are
protected by the Electronic Communications Privacy Act (18 USC §§
2510-2521), (b) may contain confidential and/or legally privileged
information, and © are for the sole use of the intended recipient named
above. If you have received this electronic message in error, please notify
the sender and delete the electronic message. Any disclosure, copying,
distribution, or use of the contents of the information received in error
is strictly prohibited.

  • Nikhil Shah */ System Administrator

nshah@theorchard.com

The Orchard® / www.theorchard.com

t (+1) 212.308.5648 / f (+1) 212.201.9203
23 E. 4th St., 3rd Fl / New York, NY 10003

The Daily Rind™ / www.dailyrindblog.com http://www.dailyrindblog.com/

Facebook http://www.facebook.com/theorchard /
@orchtweetshttp://www.twitter.com/orchtweets

Privileged And Confidential Communication.

This electronic transmission, and any documents attached hereto, (a) are
protected by the Electronic Communications Privacy Act (18 USC §§
2510-2521), (b) may contain confidential and/or legally privileged
information, and © are for the sole use of the intended recipient named
above. If you have received this electronic message in error, please notify
the sender and delete the electronic message. Any disclosure, copying,
distribution, or use of the contents of the information received in error
is strictly prohibited


#4

Could this be from misconfigured WinRM? I followed the instructions just as I did with previous servers. The only difference is now I am hosting the chef server vs. having it hosted.
Nikhil Shah / System Administrator
nshah@theorchard.com

The Orchard® / www.theorchard.com

t (+1) 212.308.5648 / f (+1) 212.201.9203
23 E. 4th St., 3rd Fl / New York, NY 10003

The Daily Rind™ / www.dailyrindblog.com
Facebook / @orchtweets

Privileged And Confidential Communication.
This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and © are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

On Sep 18, 2013, at 5:04 PM, Nikhil Shah nshah@theorchard.com wrote:

thats very odd, b/c i copied and pasted into windows login and it works.

On Wed, Sep 18, 2013 at 5:03 PM, Paul Morton - BIA pmorton@biaprotect.com 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 nshah@theorchard.com 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
nshah@theorchard.com

The Orchard® / www.theorchard.com

t (+1) 212.308.5648 / f (+1) 212.201.9203
23 E. 4th St., 3rd Fl / New York, NY 10003

The Daily Rind™ / www.dailyrindblog.com
Facebook / @orchtweets

Privileged And Confidential Communication.
This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and © are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.


Nikhil Shah / System Administrator

nshah@theorchard.com

The Orchard® / www.theorchard.com

t (+1) 212.308.5648 / f (+1) 212.201.9203
23 E. 4th St., 3rd Fl / New York, NY 10003

The Daily Rind™ / www.dailyrindblog.com

Facebook / @orchtweets

Privileged And Confidential Communication.

This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and © are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited


#5

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 <nshah@theorchard.com (mailto:nshah@theorchard.com)> 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


#6

On Sep 18, 2013, at 4:25 PM, Nikhil Shah nshah@theorchard.com wrote:

Could this be from misconfigured WinRM? I followed the instructions just as I did with previous servers. The only difference is now I am hosting the chef server vs. having it hosted.

I’ve seen weird problems with WinRM. For example, see KNIFE-22 [1], KNIFE-298 [2], and KNIFE-337 [3].

[1] https://tickets.opscode.com/browse/KNIFE-22
[2] https://tickets.opscode.com/browse/KNIFE-298
[3] https://tickets.opscode.com/browse/KNIFE-337


Brad Knowles brad@shub-internet.org
LinkedIn Profile: http://tinyurl.com/y8kpxu


#7

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 dan@kallistec.com 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 nshah@theorchard.com 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


#8

Daniel,

I think you got it. I believe when I ported over it messed with the permission of the client key. I was able to deploy a new server, ill try the ones I have been having issues with.
Nikhil Shah / System Administrator
nshah@theorchard.com

The Orchard® / www.theorchard.com

t (+1) 212.308.5648 / f (+1) 212.201.9203
23 E. 4th St., 3rd Fl / New York, NY 10003

The Daily Rind™ / www.dailyrindblog.com
Facebook / @orchtweets

Privileged And Confidential Communication.
This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and © are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

On Sep 18, 2013, at 6:16 PM, Daniel DeLeo dan@kallistec.com 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 nshah@theorchard.com 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