What goes wrong when starting virtualbox with vagrant?

Question

virtual box

Good afternoon.
I'm trying to set up a VM for vagrant.
Host OS: Windows Server 2012R2
Guest OS: Windows 10 Pro Follow
the instructions: huestones.co.uk/node/305
Everything works until ```vagrant up```:

D:\Data\vagrant\test>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 3389 (guest) => 3389 (host) (adapter 1)
    default: 5985 (guest) => 5985 (host) (adapter 1)
    default: 5986 (guest) => 55986 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> 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: negotiate
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
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.

D:\Data\vagrant\test>

Machine up and running:

D:\Data\vagrant\test>vagrant status
Current machine states:

default                   running (virtualbox)

The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.

You can log in through the virtualbox gui, but management through winrm, apparently, does not work. Nor does ```vagrant rdp```:

D:\Data\vagrant\test>vagrant rdp
An authorization error occurred while connecting to WinRM.

User: vagrant
Endpoint: http://127.0.0.1:5985/wsman
Message: WinRM::WinRMAuthorizationError

openssh installed out of the box win10.
User "vagrant" with password "vagrant".
ssh from host to guest works (```ssh -p 2222 -l vagrant localhost```)
What is going wrong and what needs to be done to make it work properly?

Answer 1

Yes, you should probably bring the Vagrantfile itself:

Vagrant.configure("2") do |config|
  config.vm.box = "windows10-rus"
end

Answer 2

do not make such sites)

Answer 3

In this case, you don't even need a video container - any video from YouTube, insert the iframe of the video on the page, apply the properties

overflow: hidden;
position: fixed;
width: 100%;
height: 100%;

and all.