vagrant up起動に失敗してしまいます。Timed out…

Question

前提・実現したいこと

BOXファイルを追加し、vagrant upをしたら下記エラーメッセージが出てしまい
起動できず困っております。
他にもBOXファイルを使用し環境を作っていますので、全てをアンインストールなどは避けたいです。

発生している問題・エラーメッセージ

set VAGRANT_LOG=infoで出力したエラーメッセージの一部が下記になります。
※一部のキー部分は変更しております。

(途中のログ)
 INFO subprocess: Command not in installer, restoring original environment...
 INFO subprocess: Starting process: ["C:/Program Files/Oracle/VirtualBox/VBoxManage.exe", "showvminfo", "○○○", "--machinereadable"]
 INFO subprocess: Command not in installer, restoring original environment...
 INFO ssh: SSH not ready: #<Vagrant::Errors::NetSSHException: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating>

(最後の方のログ)
INFO interface: error: 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.
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.

試したこと

・https://qiita.com/maten-rou/items/21e4456b8318db877f5b
⇒Vagrantの再インストール以外試しましたが変化なし
・https://qiita.com/sasurai_usagi3/items/2ba572013b16f2703f6a
⇒GUIの方から起動しましたが、メッセージがほとんど変わらず…実行中のまま…

補足情報（FW/ツールのバージョンなど）

・https://teratail.com/questions/99629
⇒マイナーバージョン(ダウングレード)したいがせっかく作成した環境が壊れるのは怖く、またどのバージョンなら起動できるか分からないため試せずにいます。

環境

ホスト
・Windows10Pro(64bit),corei5,CPU:1.60GHz
・Vagrant：2.2.6
・VirtualBox：5.2.36
・Windows セキュリティ
ゲスト
・RedHat(64bit)

---

どなたかお詳しい方、ご教授いただければ幸いです。
また、足りない情報などありましたら教えていただければと思います。

Vagrantfile

※BOX名だけ変更しています。

# -*- 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|
  # 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://vagrantcloud.com/search.
  config.vm.box = "box"

  # 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.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"

  # 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.

  # 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
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL
config.vm.boot_timeout = 400
config.vbguest.auto_update = false
config.vbguest.no_remote = true
  # end
end

Answer 1

検索してヒットしたそれらしいもの

Vagrant起動時のSSH libraryエラー解消法

Vagrantfileの以下のコードをコメントアウトすることで、起動できるようになります。

vb.customize ['modifyvm', :id, '--natdnshostresolver1', 'on']

Comments

[hotaru05]

回答ありがとうございます。
Vagrantfileにこちらのコードが無いのです。
Vagrantfileの内容をアップしましたので見ていただけたら幸いです。