Thank you so much for reaching out, you’re a lifesaver. Yes, the situation you described is correct.
I followed your instructions and opened up a second terminal and started vagrant, however, I’m still getting the same error of “command not found”.
This is the output that I get when I run: vagrant up
sh: netsh: command not found
sh: cscript: command not found
It seems that you don’t have the privileges to change the firewall rules. NFS will not work without that firewall
changes. Execute the following commands via cmd as administrator:
netsh advfirewall firewall add rule name=“VagrantWinNFSd-1.4.0” dir=“in” action=allow protocol=any program="\Users\alaniwaasa.vagrant.d\gems\2.6.6\gems\vagrant-winnfsd-1.4.0\bin\winnfsd.exe" profile=any
netsh advfirewall firewall add rule name=“VagrantWinNFSd-1.4.0” dir=“out” action=allow protocol=any program="\Users\alaniwaasa.vagrant.d\gems\2.6.6\gems\vagrant-winnfsd-1.4.0\bin\winnfsd.exe" profile=any
If you are an Windows XP user run the following command instead:
netsh firewall add allowedprogram “\Users\alaniwaasa.vagrant.d\gems\2.6.6\gems\vagrant-winnfsd-1.4.0\bin\winnfsd.exe” VagrantWinNFSd-1.4.0 ENABLE
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Clearing any previously set forwarded ports…
==> default: Clearing any previously set network interfaces…
==> default: Preparing network interfaces based on configuration…
default: Adapter 1: nat
==> default: Forwarding ports…
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM…
==> default: Waiting for machine to boot. This may take a few minutes…
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Machine booted and ready!
[default] GuestAdditions 6.1.16 running — OK.
==> default: Checking for guest additions in VM…
NFS requires a host-only network to be created.
Please add a host-only network to the machine (with either DHCP or a
static IP) for NFS to work.