{"action":"closed","issue":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/4993","labels_url":"https://api.github.com/repos/mitchellh/vagrant/issues/4993/labels{/name}","comments_url":"https://api.github.com/repos/mitchellh/vagrant/issues/4993/comments","events_url":"https://api.github.com/repos/mitchellh/vagrant/issues/4993/events","html_url":"https://github.com/mitchellh/vagrant/issues/4993","id":52100382,"number":4993,"title":"Vagrant with VMWare on Windows not detecting port collisions","user":{"login":"bartmeuris","id":2588174,"avatar_url":"https://avatars.githubusercontent.com/u/2588174?v=3","gravatar_id":"","url":"https://api.github.com/users/bartmeuris","html_url":"https://github.com/bartmeuris","followers_url":"https://api.github.com/users/bartmeuris/followers","following_url":"https://api.github.com/users/bartmeuris/following{/other_user}","gists_url":"https://api.github.com/users/bartmeuris/gists{/gist_id}","starred_url":"https://api.github.com/users/bartmeuris/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bartmeuris/subscriptions","organizations_url":"https://api.github.com/users/bartmeuris/orgs","repos_url":"https://api.github.com/users/bartmeuris/repos","events_url":"https://api.github.com/users/bartmeuris/events{/privacy}","received_events_url":"https://api.github.com/users/bartmeuris/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2014-12-16T11:13:39Z","updated_at":"2015-01-06T05:43:53Z","closed_at":"2015-01-06T05:43:53Z","body":"This issue has been reported before as #4577 - but it was closed. However the problem still remains.\r\n\r\nI must stress that this is NOT a firewall related issue as was suggested when closing the issue: Vagrant + VirtualBox on the same machine works just fine as you would expect, detecting port collisions and remapping them. Vagrant + VMWare however removes the conflicting ports of the VM that was started first, and redirects them to the new-one the moment you do a `vagrant up`. This is a VMWare specific issue.\r\n\r\nThis still occurs on Windows 7 Professional with Vagrant 1.7.1 on Windows with VMWare Workstation 10.0.3.\r\n\r\n[edit] And using the vagrant-vmware-workstation version 3.1.2 plugin"}}