Vagrand 2.0.1 + VMWare WS 14 // ERR: Failed to add NAT port entry

[Sven Bluege]

I try to run vagrant 2.0.1 with VMware Workstation 14. While I had no issues with VMWare Workstation 12, I get now this message: 

==> machine1: Starting the VMware VM...

==> machine1: Waiting for the VM to receive an address...

==> machine1: Forwarding ports...

    machine1: -- 22 => 2222

C:/Users/User.Name/.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/driver.rb:2138:in `win_set_forwarded_port': Port forward registry set failure. (RuntimeError)

OUT:

ERR: Failed to add NAT port entry: Zugriff verweigert

        from C:/Users/User.Name/.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/driver.rb:1825:in `block in forward_ports'

I'm running this from an elevated command line. 

Can somebody help with this error message? How can I get a running vm back?

Thanks!!

[Alvaro Miranda Aguilera]

vagrant 2.X with plugin 5.x can be run as a normal user.

the Zugriff verweigert is coming from somewhere.

try running this as normal user

if still fails, try disabling AntiVirus 

Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/8cb68fc2-5d88-42ad-a50b-583e4bbd444c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Sven Bluege]

If I run vagrant from a normal command line, I get this: 

Vagrant failed to initialize at a very early stage:

Failed to invoke the VMware utility task.

  Cause: FEHLER: Zugriff verweigert

Please address the issue above and try again. If

this problem persists, please contact sup...@hashicorp.com

Virus scanner is disabled and did not change the behavior.

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/8cb68fc2-5d88-42ad-a50b-583e4bbd444c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Stephen Funkhouser]

I have the exact same issue.

Vagrant happens in both 2.0.0 and 2.0.1

Vagrant pluins:

vagrant-share (1.1.9)

vagrant-triggers (0.5.3)

vagrant-vmware-workstation (0.5.3)

[Sven Bluege]

I had a long conversation with the support team. In the end, they were not able to help me. My solution was to go back to an older Vagrant version. But more important was the version of VMWare and the vmware plugin: I switched back to VMWare 12 and vagrant-vmware-workstation 4.0.23. Now it works again. 

Seems like they have a lot of trouble with permission management on Windows systems in a Domain. My private computer at home works perfectly with the latest versions.