[chef] Re: RE: Re: Can't knife winrm to Windows box?

[Galen Emery < >]

On Wed, Nov 12, 2014 at 4:18 PM, Fouts, Chris < " target="_blank"> > wrote:

-----Original Message-----
From: Daniel DeLeo [mailto: "> ] On Behalf Of Daniel DeLeo
Sent: Wednesday, November 12, 2014 7:12 PM
To: ">
Subject: [chef] Re: Can't knife winrm to Windows box?



On Wednesday, November 12, 2014 at 4:09 PM, Fouts, Chris wrote:

> I’ve done everything described here. In my case it’s a Windows Server 2012 R2 box.
> https://docs.getchef.com/plugin_knife_windows.html
>
> knife winrm ………….. gives
>
> ~]# knife winrm "mynode.domain.com
> (http://mynode.domain.com)" "dir" -m -x Administrator -P myPW -p 5986
> ERROR: Network Error: Connection refused - connect(2)
> (https://mynode.domain.com:5986) Check your knife configuration and
> network settings
>
> Any clues? Any more debugging steps I can take?
>
> Thanks,
> Chris

Connection refused means that either nothing is listening on that port on that host, or there is a firewall that makes it look like nothing is listening on that port on that host.

--
Daniel DeLeo


I did this

~]# nmap -p 5985 mynode.domain.com

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2014-11-12 19:15 EST
Interesting ports on <ip address removed>:
PORT     STATE SERVICE
5985/tcp open  unknown

Nmap finished: 1 IP address (1 host up) scanned in 0.205 seconds

You're testing 5985, but in your knife winrm example, you have 5986.  Are you trying for a secure or insecure connection?

--

Galen Emery