search

misheska / basebox-packer

Packer templates for vagrant baseboxes
286 stars 80 forks source link

WinRM not working with Windows baseboxes & Vagrant 1.6 #68

Open misheska opened 10 years ago

misheska commented 10 years ago

When I disable the SSH server on the Windows basebox and try to use config.vm.communicator = "winrm" - vagrant ssh still seems to try to be using ssh

misheska commented 10 years ago

Vagrantfile (or template) needs to be formatted as follows:

config.vm.network :forwarded_port, guest: 3389, host: 3389  
config.vm.communicator = "winrm"
config.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct:true

Key is tagging the 5985 port forward to have the id "winrm". Slowly rolling this fix out

StefanScherer commented 10 years ago

I suggest an id for the RDP port as well as the auto correction, as working on a windows host the port 3389 is already in use:

config.vm.network :forwarded_port, guest: 3389, host: 3389, id: "rdp", auto_correct:true

BTW: I have played with Vagrant 1.6 greatest feature today and wish that these two port forwardings could be done without the (template) Vagrantfile as it is done with the ssh port in Vagrant's plugins/kernel_v2/config/vm.rb line 357. As you can see, also the ssh port has an id called "ssh", so the "rdp" id should be fine.

misheska commented 10 years ago

Sure thing, can’t hurt.

On May 7, 2014, at 3:34 AM, Stefan Scherer notifications@github.com wrote:

I suggest an id for the RDP port as well as the auto correction, as working on a windows host the port 3389 is already in use:

config.vm.network :forwarded_port, guest: 3389, host: 3389, id: "rdp", auto_correct:true
BTW: I have played with Vagrant 1.6 greatest feature today and wish that these two port forwardings could be done without the (template) Vagrantfile as it is done with the ssh port in Vagrant's plugins/kernel_v2/config/vm.rb line 357. As you can see, also the ssh port has an id called "ssh", so the "rdp" id should be fine.

— Reply to this email directly or view it on GitHub.

StefanScherer commented 10 years ago

An upcoming version of Vagrant 1.6.x may obsolete these port forwardings, as it seems the winrm communicator will do this automatically, as suggested in Vagrant issue #3685. But for the moment it is useful.