-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WinRM not working with Windows baseboxes & Vagrant 1.6 #68
Comments
Vagrantfile (or template) needs to be formatted as follows:
Key is tagging the 5985 port forward to have the id "winrm". Slowly rolling this fix out |
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:
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. |
Sure thing, can’t hurt. On May 7, 2014, at 3:34 AM, Stefan Scherer notifications@github.com wrote:
|
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. |
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 sshThe text was updated successfully, but these errors were encountered: