[WinRM] Process of remote acess to Windows vagrant box is stuck on "vagrant rdp" command

[Mikhail R]

Dear community,


I would like to ask for some help.

I created vagrant box (https://atlas.hashicorp.com/senglin/boxes/win-10-enterprise-vs2015community), start it and when I tried to remotely connect to this machine by using "vagrant rdp" command in terminal on my host machine the process of remote connection got stucked.

D:\Vagrant_Machines>vagrant up --provider virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'senglin/win-10-enterprise-vs2015community' is up to date...
==> default: VirtualBox VM is already running.

D:\Vagrant_Machines>vagrant rdp

D:\Vagrant_Machines>Exiting due to interrupt.


D:\Vagrant_Machines>vagrant rdp

D:\Vagrant_Machines>Exiting due to interrupt.


D:\Vagrant_Machines>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'senglin/win-10-enterprise-vs2015community' is up to date...
==> default: VirtualBox VM is already running.

D:\Vagrant_Machines>vagrant rdp
Exiting due to interrupt.

D:\Vagrant_Machines>vagrant rdp

And that's it. Nothing happens.

Please, advice me smth. Thanks in advance.

[Mikhail R]

D:\Vagrant_Machines>vagrant rdp
VM must be created before running this command. Run `vagrant up` first.

D:\Vagrant_Machines>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...

There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* Forwarded port '3389' (host port) is declared multiple times
with the protocol 'tcp'.


D:\Vagrant_Machines>

[Mikhail R]

Vagrant file

Enter code here# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
  Vagrant.configure(2) do |config|
  config.vm.guest = :windows
  config.vm.communicator = "winrm"
  config.vm.boot_timeout = 600
  config.vm.graceful_halt_timeout = 600
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://atlas.hashicorp.com/search.
  config.vm.box = "senglin/win-10-enterprise-vs2015community"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # config.vm.network "forwarded_port", guest: 80, host: 8080
 
  config.vm.network :forwarded_port, guest: 3389, host: 3389
  config.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct: true

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
  # such as FTP and Heroku are also available. See the documentation at
  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
  # config.push.define "atlas" do |push|
  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
  # end

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   sudo apt-get update
  #   sudo apt-get install -y apache2
  # SHELL
end
...

On Thursday, June 2, 2016 at 3:31:38 PM UTC+3, Mikhail R wrote:

[Mikhail R]

Now I have this

D:\Vagrant_Machines>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'senglin/win-10-enterprise-vs2015community' is up to date...

==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 3389 => 3389. Now on port 2200.
==> default: Fixed port collision for 22 => 2222. Now on port 2201.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 3389 (guest) => 2200 (host) (adapter 1)
    default: 22 (guest) => 2201 (host) (adapter 1)
    default: 2222 (guest) => 8080 (host) (adapter 1)
    default: 5985 (guest) => 5985 (host) (adapter 1)
    default: 5986 (guest) => 55986 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: WinRM address: 127.0.0.1:5985
    default: WinRM username: vagrant
    default: WinRM execution_time_limit: PT2H
    default: WinRM transport: plaintext
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

On Thursday, June 2, 2016 at 3:31:38 PM UTC+3, Mikhail R wrote: