Re: Re: WinRM cannot connect


#1

Actually windows server 2003 doesn’t come with it installed by default and I didn’t have the cd to install winrm with, so I got it from microsoft and it is version 1.1. Is there anyway to add port 5985 to the config of winrm instead of passing that parameter? I have my windows xp box working fine but the installer is a different name than the one I got from the winrm v1.1 microsoft page.

William,
I’m pretty sure Windows Server 2003 ships with WinRM 1.1 which listens on port 80 by default. Out of the box ‘knife winrm’ will attempt to use the WinRM 2.0 port which is 5985. You will have to add a ‘-p 80’ option to your command to override this default behavior.


Seth Chisamore
Software Development Engineer, Opscode, Inc.
IRC, Skype, Twitter, Github: schisamo

On Friday, March 23, 2012 at 11:19 AM, Soula, William wrote:
I’ve started using chef so I apologize if this is the wrong mailing list for my questions or if what I am trying to do is unsupported. I’m trying to setup a windows server 2003 R2 machine and then connect to it through knife and winrm. I ran winrm quickconfig –q on the server and at first was getting an error about not enough end points or something about end points. Then I figured out that the windows firewall had to be turned on for the quickconfig to work. So I turned this on and now the server is setup for remote management. But when I try to connect to it and run ipconfig I get an error:

ERROR: Network Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. - connect(2)

The command I am running is:

knife winrm [server] ipconfig -m -x [localadmin] -P [password]

localadmin exists on the server as a local administrator

Can anyone help me or is it a winRM problem and I should ask on a different mailing list, or is it a knife problem that should be asked on a different mailing list?

Thanks,
Will