Just as @nic_chef has suggested - Is port 5985 open & listening? I am assuming you have already run basic trouble shooting like
ping <ip address> to verify the machine is accessible from the Chef server & ChefDK Workstation. Also from the ChefDK Machine
telnet <ip address>? If not, then we need to very that the node is setup for WINRM!
To verify that the client is LISTENING on the port you can type
netstat -an | find "5985" from CMD. Output on your node/client? You should have an output as follows (You will see I am listening on both IPv4 & IPv6):
C:\>netstat -an | find "5985"
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING
TCP [::]:5985 [::]:0 LISTENING
UDP 127.0.0.1:59853 *:*
If the client machine doesn’t have port 5985 open, you can run the WINRM quick config as detailed here. But the quick (and maybe not the ‘Best practice’ method) way to get going is to type from CMD
winrm qc and respond yes to all prompts. You should end up with an output of something similar to this:
WinRM has been updated for remote management.
WinRM service type changed to delayed auto start.
WinRM service started.
Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this
Then you can rerun the
netstat -an | find "5985" to see if you are now listening on port 5985 (Maybe a quick reboot might also help here).
telnet fails, but
netstat gives you a port
5985 LISTENING output, then I would check your firewall.