Sorry wrong port on previous post…
[root@server ~]# nmap -p 5986 mynode.domain.com
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2014-11-12 19:18 EST
Interesting ports on :
PORT STATE SERVICE
5986/tcp filtered unknown
Nmap finished: 1 IP address (1 host up) scanned in 0.358 seconds
From: Daniel DeLeo [mailto:email@example.com] On Behalf Of Daniel DeLeo
Sent: Wednesday, November 12, 2014 7:12 PM
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.
knife winrm …………… gives
[root@bserver ~]# 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
Any clues? Any more debugging steps I can take?
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.