does vagrant if rdp port is on a different port than 3389 ? or, does winrm fails as not all the vms have por 5985 forwarded?
On Sat, May 17, 2014 at 11:19 AM, Michael Legleux <[email protected]> wrote: > I created a base box of windows 7 and 8 using virtualbox. > I configured the winrm according to the vagrant-windows port-forwarding > for rdp and winrm. > also this post helped since: > https://github.com/mitchellh/vagrant/issues/3685 > > config.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", > auto_correct: true > > config.vm.network :forwarded_port, guest: 3389, host: 3389, id: "rdp", > auto_correct: true > > Using linux, my custom box imported and boots fine. The basebox winrm > configuring seems to work as vagrant doesn't hang and give up while > "waiting for machine to boot." > > However... when trying on a windows machine, vagrant complains that it > can't forward the specified ports on this vm because it is already in use > on the host machine. > The port being 3389, which is windows remote desktop port. > > When I changed the forwarded ports for the guest (as it suggests) vagrant > is unable to communicate with the windows box. > Now I am unsure how to proceed. > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
