search

clong / DetectionLab

Automate the creation of a lab environment complete with security tooling and logging best practices
MIT License
4.6k stars 980 forks source link

Port collision #167

Closed dnice77 closed 5 years ago

dnice77 commented 5 years ago

Description of the issue:

==> win10: Fixed port collision for 3389 => 3389. Now on port 2202. ==> win10: Fixed port collision for 22 => 2222. Now on port 2203. ==> win10: Starting the VMware VM... ==> win10: Waiting for the VM to receive an address... Some of the defined forwarded ports would collide with existing forwarded ports on VMware network devices. This can be due to existing Vagrant-managed VMware machines, or due to manually configured port forwarding with VMware. Please fix the following port collisions and try again:

55985, 55986

*Is there a config file I need to make a change to?

clong commented 5 years ago

Hmm, I'm not sure how to fix this for Windows. Here's the solution for VMware Fusion, but I'm not sure where the equivalent files are for Windows:

https://github.com/hashicorp/vagrant/issues/8130#issuecomment-272963103

clong commented 5 years ago

@dnice77 were you able to get things working again?

clong commented 5 years ago

Closing due to inactivity

nterl0k commented 5 years ago

Operating System Version: Windows Server 2016 Provider (VirtualBox/VMWare): VMWare Workstation Pro 12.5.9 Vagrant Version: 2.2.1 Vagrant VMWare Desktop Utility Version: 1.0.5 Packer Version: 1.3.2 Is the issue reproducible or intermittent? reproducible

Received similar issue with the provisioning of the DC, stopped install to troubleshoot:

==> dc: Fixed port collision for 3389 => 3389. Now on port 2202. ==> dc: Fixed port collision for 22 => 2222. Now on port 2203. ==> dc: Starting the VMware VM... ==> dc: Waiting for the VM to receive an address... Some of the defined forwarded ports would collide with existing forwarded ports on VMware network devices. This can be due to existing Vagrant-managed VMware machines, or due to manually configured port forwarding with VMware. Please fix the following port collisions and try again: 55985, 55986

Checked the following items:

Attempted Fix:es (using "./vagrant reload dc --provision" after each)

I'm going to attempt to remove all of the components associated with the lab and re-install fresh... Unclear if this will help with the issue.

dnice77 commented 5 years ago

Thank you guys! I've been out with some medical issues but look forward to getting that fixed...Sent from my Sprint Samsung Galaxy S9. -------- Original message --------From: pheerless notifications@github.com Date: 11/25/18 10:16 AM (GMT-05:00) To: clong/DetectionLab DetectionLab@noreply.github.com Cc: dnice77 dbohatec@gmail.com, Mention mention@noreply.github.com Subject: Re: [clong/DetectionLab] Port collision  (#167) Operating System Version: Windows Server 2016 Provider (VirtualBox/VMWare): VMWare Workstation Pro 12.5.9 Vagrant Version: 2.2.1 Vagrant VMWare Desktop Utility Version: 1.0.5 Packer Version: 1.3.2 Is the issue reproducible or intermittent? reproducible Received similar issue with the provisioning of the DC, stopped install to troubleshoot: ==> dc: Fixed port collision for 3389 => 3389. Now on port 2202. ==> dc: Fixed port collision for 22 => 2222. Now on port 2203. ==> dc: Starting the VMware VM... ==> dc: Waiting for the VM to receive an address... Some of the defined forwarded ports would collide with existing forwarded ports on VMware network devices. This can be due to existing Vagrant-managed VMware machines, or due to manually configured port forwarding with VMware. Please fix the following port collisions and try again: 55985, 55986 Checked the following items:

Used "./vagrant up" -failed as above Used "./vagrant reload dc --provision" - failed as above

Attempted Fix:es (using "./vagrant reload dc --provision" after each)

Used "./vagrant destroy" then "./vagrant up" Commented out any existing port forwards, the following link gives the proper location for VWWare Workstation (Similar to Issue #8130) C:\ProgramData\VMware\vmnetnat.conf Removed existing port forwards in the GUI for VMWare under "Edit -> Vitrual Network Editor -> NAT -> NAT Settings" -- Changing NAT Settings via the GUI triggers a restart of NAT services https://docs.vmware.com/en/VMware-Workstation-Pro/12.0/com.vmware.ws.using.doc/GUID-C2EC7B92-A499-4B47-95B6-0BFDDA28AC34.html Checked Host machine port allocations for 55985 and 55986, no associations were found. Cleared "C:\ProgramData\hashicorp\vagrant-vmware-desktop\settings\nat.json" Rebuilt the "VMWare Desktop Utility" via add/remove programs. Toggled Host WinRM service just for good measure, though doubted this would help.

I'm going to attempt to remove all of the components associated with the lab and re-install fresh... Unclear if this will help with the issue.

—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread. {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/clong/DetectionLab","title":"clong/DetectionLab","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/clong/DetectionLab"}},"updates":{"snippets":[{"icon":"PERSON","message":"@pheerless in #167: Operating System Version: Windows Server 2016\r\nProvider (VirtualBox/VMWare): VMWare Workstation Pro 12.5.9\r\nVagrant Version: 2.2.1\r\nVagrant VMWare Desktop Utility Version: 1.0.5\r\nPacker Version: 1.3.2\r\nIs the issue reproducible or intermittent? reproducible\r\n\r\nReceived similar issue with the provisioning of the DC, stopped install to troubleshoot:\r\n\r\n==\u003e dc: Fixed port collision for 3389 =\u003e 3389. Now on port 2202.\r\n==\u003e dc: Fixed port collision for 22 =\u003e 2222. Now on port 2203.\r\n==\u003e dc: Starting the VMware VM...\r\n==\u003e dc: Waiting for the VM to receive an address...\r\nSome of the defined forwarded ports would collide with existing\r\nforwarded ports on VMware network devices. This can be due to\r\nexisting Vagrant-managed VMware machines, or due to manually\r\nconfigured port forwarding with VMware. Please fix the following\r\nport collisions and try again:\r\n55985, 55986\r\n\r\n\r\nChecked the following items:\r\n- Used \"./vagrant up\" -failed as above\r\n- Used \"./vagrant reload dc --provision\" - failed as above\r\n\r\nAttempted Fix:es (using \"./vagrant reload dc --provision\" after each)\r\n- Used \"./vagrant destroy\" then \"./vagrant up\"\r\n- Commented out any existing port forwards, the following link gives the proper location for VWWare Workstation (Similar to Issue #8130) C:\ProgramData\VMware\vmnetnat.conf\r\n- Removed existing port forwards in the GUI for VMWare under \"Edit -\u003e Vitrual Network Editor -\u003e NAT -\u003e NAT Settings\" -- Changing NAT Settings via the GUI triggers a restart of NAT services\r\n- https://docs.vmware.com/en/VMware-Workstation-Pro/12.0/com.vmware.ws.using.doc/GUID-C2EC7B92-A499-4B47-95B6-0BFDDA28AC34.html \r\n- Checked Host machine port allocations for 55985 and 55986, no associations were found.\r\n- Cleared \"C:\ProgramData\hashicorp\vagrant-vmware-desktop\settings\nat.json\"\r\n- Rebuilt the \"VMWare Desktop Utility\" via add/remove programs.\r\n- Toggled Host WinRM service just for good measure, though doubted this would help.\r\n\r\nI'm going to attempt to remove all of the components associated with the lab and re-install fresh... Unclear if this will help with the issue."}],"action":{"name":"View Issue","url":"https://github.com/clong/DetectionLab/issues/167#issuecomment-441447730"}}} [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/clong/DetectionLab/issues/167#issuecomment-441447730", "url": "https://github.com/clong/DetectionLab/issues/167#issuecomment-441447730", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } }, { "@type": "MessageCard", "@context": "http://schema.org/extensions", "hideOriginalBody": "false", "originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB", "title": "Re: [clong/DetectionLab] Port collision (#167)", "sections": [ { "text": "", "activityTitle": "pheerless", "activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png", "activitySubtitle": "@pheerless", "facts": [

] } ], "potentialAction": [ { "name": "Add a comment", "@type": "ActionCard", "inputs": [ { "isMultiLine": true, "@type": "TextInput", "id": "IssueComment", "isRequired": false } ], "actions": [ { "name": "Comment", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"clong/DetectionLab\",\n\"issueId\": 167,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}" } ] }, { "targets": [ { "os": "default", "uri": "https://github.com/clong/DetectionLab/issues/167#issuecomment-441447730" } ], "@type": "OpenUri", "name": "View on GitHub" }, { "name": "Unsubscribe", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 406626844\n}" } ], "themeColor": "26292E" } ]