Comments (14)
clong
commented on May 28, 2024
==> win10: Adding Win10 to the domain. Sometimes this step times out. If that happens, just run 'vagrant reload win10 --provision'
INFO interface: info: VERBOSE: Performing the operation "Join in domain 'windomain.local'" on target "win10".
INFO interface: info: ==> win10: VERBOSE: Performing the operation "Join in domain 'windomain.local'" on target "win10".
==> win10: VERBOSE: Performing the operation "Join in domain 'windomain.local'" on target "win10".
DEBUG winrmshell: [WinRM] Waiting for output...
DEBUG winrmshell: [WinRM] cleaning up command_id: E6298A4D-A61F-4B23-9222-3ADE12310298 on shell_id A462F65E-6032-46CA-862F-0C11FD81F055
ERROR warden: Error occurred: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
from detectionlab.
clong
commented on May 28, 2024
Correct join looks like this:
==> wef: Now join the domain
DEBUG winrmshell: [WinRM] Waiting for output...
DEBUG winrmshell: [WinRM] Processing output
INFO interface: info: HasSucceeded : True
INFO interface: info: ==> wef: HasSucceeded : True
==> wef: HasSucceeded : True
INFO interface: info: ComputerName : wef
INFO interface: info: ==> wef: ComputerName : wef
==> wef: ComputerName : wef
INFO interface: info: WARNING: The changes will take effect after you restart the computer wef.
INFO interface: info: ==> wef: WARNING: The changes will take effect after you restart the computer wef.
==> wef: WARNING: The changes will take effect after you restart the computer wef.
INFO interface: info: Hint: vagrant reload wef --provision
INFO interface: info: ==> wef: Hint: vagrant reload wef --provision
==> wef: Hint: vagrant reload wef --provision```
from detectionlab.
digital4rensics
commented on May 28, 2024
Not limited to VMWare - I have experienced this twice now on VirtualBox Version 5.1.30
In both cases, reload --provision corrected it.
from detectionlab.
labgeek18
commented on May 28, 2024
I'm having an issue with the win10 box joining the domain. [VirtualBox v5.2.6.r.120]
(Detection Lab files are up to date)
....vagrant reload --provision win10:
Stderr from the command:
powershell.exe : Add-Computer : Computer 'win10' failed to join domain 'windomain.local' from its current
+ CategoryInfo : NotSpecified: (Add-Computer : ...om its current :String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
workgroup 'WORKGROUP' with following error message: The specified domain either does not exist or
could not be contacted.
At C:\vagrant\scripts\join-domain.ps1:22 char:3
- Add-Computer -DomainName "windomain.local" -credential $DomainCred ...
-
+ CategoryInfo : OperationStopped: (win10:String) [Add-Computer], InvalidOperationEx
ception
+ FullyQualifiedErrorId : FailToJoinDomainFromWorkgroup,Microsoft.PowerShell.Commands.AddComp
uterCommand
from detectionlab.
clong
commented on May 28, 2024
Hi @labgeek18 - can you check the following? :
- DC host is online while Win10 host is being provisioned (necessary to join the domain)
- Win10 host can ping "windomain.local" and resolve it successfully
That error message indicates that the Win10 host can't successfully connect to or resolve the DC host
from detectionlab.
labgeek18
commented on May 28, 2024
Looks like the networking had gotten a bit confused somehow. ..
1) The DC is up
2) The Win10 host cannot ping "windomain.local"
3) The image below is from the DC:
(no image show)
All of the DT hosts appear to be getting the same IP address. 10.0.2.15
When I ping "windomain.local" the only host that even gets a response ping is the DC. answer is: 10.0.2.15
…On Wed, Feb 28, 2018 at 3:44 AM, Chris Long ***@***.***> wrote:
Hi @labgeek18 <https://github.com/labgeek18> - can you check the
following? :
- DC host is online while Win10 host is being provisioned (necessary
to join the domain)
- Win10 host can ping "windomain.local" and resolve it successfully
That error message indicates that the Win10 host can't successfully
connect to or resolve the DC host
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AjKh6oay2b1oHBA1szzjtnE3O1YraBT0ks5tZRH9gaJpZM4P5pYd>
.
--
Corey L. Johnson Sr.
from detectionlab.
clong
commented on May 28, 2024
Still trying to run this down. Latest updates appear to be here: hashicorp/vagrant#8639
from detectionlab.
mikeesparza
commented on May 28, 2024
I'm was having the exact same issue as above with the duplicated IP issues.
The IP Issue half-resolved itself when I updated Vagrant and VirtualBox.
Ubuntu 16.04 Desktop
Vagrant 2.2.0
VirtualBox 5.2.20 r125813
It's half-resolved because I now get the 192.168.38.102 IP as the DC IP but i also get the 10.0.2.15 on another Ethernet adapter.
I believe the bug is also causing issues with AD as the 'configure-out.ps1' script is giving an error that it is not able to contact the server.
I will continue to work on my lab trying to fix this issues.
Apologies for my brevity, I'm new to this, but trying to learn!
from detectionlab.
clong
commented on May 28, 2024
Closing this issue due to inactivity. It rarely happens now and is easily fixed with a reload.
from detectionlab.
clong
commented on May 28, 2024
Re-opening this as I think this still happens a fair amount
from detectionlab.
clong
commented on May 28, 2024
Confirmed this is still happening. I was able to capture debug output. The odd thing is that WinRM responds just fine to new connections using the forwarded port. I'm not sure what happens during the domain join that makes Vagrant barf and seemingly lose track of the connection.
$ winrm-cli -username vagrant -password vagrant -hostname localhost -port 2207 ipconfig
Windows IP Configuration
Ethernet adapter Ethernet0:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::6832:e426:a56c:ee5%6
IPv4 Address. . . . . . . . . . . : 192.168.38.104
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.38.1
Ethernet adapter Ethernet0 2:
Connection-specific DNS Suffix . : localdomain
Link-local IPv6 Address . . . . . : fe80::ac02:8fa7:75a8:edd%4
IPv4 Address. . . . . . . . . . . : 172.16.142.152
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.142.2
Debug output:
win10: Adding Win10 to the domain. Sometimes this step times out. If that happens, just run 'vagrant reload win10 --provision'
DEBUG winrmshell: [WinRM] Waiting for output...
DEBUG winrmshell: [WinRM] cleaning up command_id: 89470424-6AF5-4AB3-ADF9-44C68956F1C7 on shell_id 99297D2B-F6B6-49F9-8845-8EA44FE2986D
ERROR warden: Error occurred: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::HandleForwardedPortCollisions:0x00000001029fc920>
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000000100c58ef0>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000000102338350>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Calling recover: VMware Middleware: Import
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmrun", "list"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Total running VMs: 4
/censored/DetectionLab/Vagrant/.vagrant/machines/wef/vmware_desktop/acfaab4a-dfb8-4d91-8a73-975c7700259c/WindowsServer2016.vmx
/censored/DetectionLab/Vagrant/.vagrant/machines/win10/vmware_desktop/5657352f-436c-4dfc-a633-cbd89f9f512a/windows_10.vmx
/censored/DetectionLab/Vagrant/.vagrant/machines/dc/vmware_desktop/09362cf2-a643-4ce5-aa26-5302f78b1fd1/WindowsServer2016.vmx
/censored/DetectionLab/Vagrant/.vagrant/machines/logger/vmware_desktop/92936ec4-5db8-4d4e-bc5a-e191c5ddd7f9/ubuntu-16.04-amd64.vmx
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG vmware: VM state requested. Current state: running
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000001023e2378>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO environment: Released process lock: machine-action-4a4fd29ffd708d5dfa188c1a0dfac23a
INFO environment: Running hook: environment_unload
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 2 hooks defined.
INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x000000010239ac58>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x0000000102390640>
INFO warden: Calling IN action: HashiCorp Background Check: End
INFO logger: Cleaning up background activation thread...
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x0000000101d0f1b8>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x0000000101d0f1b8>
INFO warden: Calling OUT action: HashiCorp Background Check: End
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x0000000102390640>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<VagrantPlugins::CommunicatorWinRM::Errors::ConnectionTimeout: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.>
ERROR vagrant: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
ERROR vagrant: /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/winrm/shell.rb:180:in `raise_winrm_exception'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/winrm/shell.rb:140:in `rescue in execute_with_rescue'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/winrm/shell.rb:137:in `execute_with_rescue'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/winrm/shell.rb:63:in `block in powershell'
/opt/vagrant/embedded/gems/2.2.4/gems/winrm-2.3.1/lib/winrm/connection.rb:42:in `shell'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/winrm/shell.rb:62:in `powershell'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/winrm/communicator.rb:152:in `execute'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/provisioners/shell/provisioner.rb:227:in `block (2 levels) in provision_winrm'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/provisioners/shell/provisioner.rb:174:in `tap'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/provisioners/shell/provisioner.rb:174:in `block in provision_winrm'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/provisioners/shell/provisioner.rb:297:in `with_script_file'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/provisioners/shell/provisioner.rb:173:in `provision_winrm'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/provisioners/shell/provisioner.rb:27:in `provision'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/provision.rb:138:in `run_provisioner'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:121:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:121:in `block in finalize_action'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `block in run'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `run'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/environment.rb:527:in `hook'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/provision.rb:126:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/provision.rb:126:in `block in call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/provision.rb:103:in `each'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/provision.rb:103:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:121:in `block in finalize_action'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `block in run'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `run'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/censored/.vagrant.d/gems/2.4.4/gems/vagrant-vmware-desktop-2.0.1/lib/vagrant-vmware-desktop/action_farm.rb:1296:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/censored/.vagrant.d/gems/2.4.4/gems/vagrant-vmware-desktop-2.0.1/lib/vagrant-vmware-desktop/action_farm.rb:130:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:121:in `block in finalize_action'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `block in run'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `run'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/box_check_outdated.rb:84:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/censored/.vagrant.d/gems/2.4.4/gems/vagrant-vmware-desktop-2.0.1/lib/vagrant-vmware-desktop/action_farm.rb:447:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/censored/.vagrant.d/gems/2.4.4/gems/vagrant-vmware-desktop-2.0.1/lib/vagrant-vmware-desktop/action_farm.rb:288:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/censored/.vagrant.d/gems/2.4.4/gems/vagrant-vmware-desktop-2.0.1/lib/vagrant-vmware-desktop/action_farm.rb:1375:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/censored/.vagrant.d/gems/2.4.4/gems/vagrant-vmware-desktop-2.0.1/lib/vagrant-vmware-desktop/action_farm.rb:693:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/prepare_clone.rb:15:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:121:in `block in finalize_action'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `block in run'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `run'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/censored/.vagrant.d/gems/2.4.4/gems/vagrant-vmware-desktop-2.0.1/lib/vagrant-vmware-desktop/action_farm.rb:158:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/censored/.vagrant.d/gems/2.4.4/gems/vagrant-vmware-desktop-2.0.1/lib/vagrant-vmware-desktop/action_farm.rb:447:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/censored/.vagrant.d/gems/2.4.4/gems/vagrant-vmware-desktop-2.0.1/lib/vagrant-vmware-desktop/action_farm.rb:305:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `block in run'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `run'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:238:in `action_raw'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:209:in `block in action'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/environment.rb:615:in `lock'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:195:in `call'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:195:in `action'
/opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
/opt/vagrant/embedded/gems/2.2.4/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in `block in create_with_logging_context'
INFO interface: error: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
INFO interface: Machine: error-exit ["VagrantPlugins::CommunicatorWinRM::Errors::ConnectionTimeout", "Vagrant timed out while attempting to connect via WinRM. This usually\nmeans that the VM booted, but there are issues with the WinRM configuration\nor network connectivity issues. Please try to `vagrant reload` or\n`vagrant up` again."]
from detectionlab.
clong
commented on May 28, 2024
This hasn't been an issue for quite some time now (knocks on wood). Marking as closed.
from detectionlab.
BaffledJimmy
commented on May 28, 2024
I think I might be having a similar issue, I have tripled the cfg.boottimeout and the cfg.winrm timeout for the w10 box, but still get the same issue I'm afraid.
VBox version - 6.1.4
Vagrant version - Vagrant 2.2.7
Host - Server 2k19 x64
DC host is all online and pingable. There is an entry for dc.windomain.local in the host file on w10.
192.168.38.102 dc.windomain.local
Results from third reload / provision:
PS C:\DetectionLab\Vagrant> vagrant reload win10 --provision
==> win10: Attempting graceful shutdown of VM...
==> win10: Checking if box 'detectionlab/win10' version '1.4' is up to date...
==> win10: Clearing any previously set forwarded ports...
==> win10: Fixed port collision for 5985 => 55985. Now on port 2204.
==> win10: Fixed port collision for 5986 => 55986. Now on port 2205.
==> win10: Fixed port collision for 22 => 2222. Now on port 2206.
==> win10: Clearing any previously set network interfaces...
==> win10: Preparing network interfaces based on configuration...
win10: Adapter 1: nat
win10: Adapter 2: hostonly
==> win10: Forwarding ports...
win10: 5985 (guest) => 2204 (host) (adapter 1)
win10: 5986 (guest) => 2205 (host) (adapter 1)
win10: 22 (guest) => 2206 (host) (adapter 1)
==> win10: Running 'pre-boot' VM customizations...
==> win10: Booting VM...
==> win10: Waiting for machine to boot. This may take a few minutes...
win10: WinRM address: 127.0.0.1:2204
win10: WinRM username: vagrant
win10: WinRM execution_time_limit: PT2H
win10: WinRM transport: negotiate
==> win10: Machine booted and ready!
==> win10: Checking for guest additions in VM...
win10: The guest additions on this VM do not match the installed version of
win10: VirtualBox! In most cases this is fine, but in rare cases it can
win10: prevent things such as shared folders from working properly. If you see
win10: shared folder errors, please make sure the guest additions within the
win10: virtual machine match the version of VirtualBox you have installed on
win10: your host and reload your VM.
win10:
win10: Guest Additions Version: 6.0.10
win10: VirtualBox Version: 6.1
==> win10: Setting hostname...
==> win10: Configuring and enabling network interfaces...
==> win10: Mounting shared folders...
win10: /vagrant => C:/DetectionLab/Vagrant
==> win10: Running provisioner: shell...
win10: Running: scripts/fix-second-network.ps1 as c:\tmp\vagrant-shell.ps1
win10: Nothing to do for other providers than VMware.
==> win10: Running provisioner: shell...
win10: Running: scripts/MakeWindows10GreatAgain.ps1 as c:\tmp\vagrant-shell.ps1
win10: [02:48] Making Windows 10 Great again
win10: [02:48] Importing registry keys...
win10: [02:48] Removing OneDrive...
win10: [02:48] Disabling automatic screen turnoff in order to prevent screen locking...
win10: [02:48] Downloading ShutUp10...
win10: [02:48] Installing ShutUp10 and disabling Windows Defender
win10: powershell.exe : Invoke-WebRequest : Unable to connect to the remote server
win10: + CategoryInfo : NotSpecified: (Invoke-WebReque...e remote server:String) [], RemoteException
win10: + FullyQualifiedErrorId : NativeCommandError
win10: At C:\tmp\vagrant-shell.ps1:35 char:3
win10: + Invoke-WebRequest -Uri "$shutUp10DownloadUrl" -OutFile $shutUp10Rep ...
win10: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
win10: + CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invok
win10: e-WebRequest], WebException
win10: + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeW
win10: ebRequestCommand
win10:
win10: . : The term 'C:\Users\vagrant\AppData\Local\Temp\OOSU10.exe' is not recognized as the name of a
win10: cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path
win10: was included, verify that the path is correct and try again.
win10: At C:\tmp\vagrant-shell.ps1:36 char:5
win10: + . $shutUp10RepoPath c:\vagrant\resources\windows\shutup10.cfg /quie ...
win10: + ~~~~~~~~~~~~~~~~~
win10: + CategoryInfo : ObjectNotFound: (C:\Users\vagran...Temp\OOSU10.exe:String) [], Comm
win10: andNotFoundException
win10: + FullyQualifiedErrorId : CommandNotFoundException
win10:
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
powershell -ExecutionPolicy Bypass -OutputFormat Text -file "c:\tmp\vagrant-shell.ps1"
Stdout from the command:
[02:48] Making Windows 10 Great again
[02:48] Importing registry keys...
[02:48] Removing OneDrive...
[02:48] Disabling automatic screen turnoff in order to prevent screen locking...
[02:48] Downloading ShutUp10...
[02:48] Installing ShutUp10 and disabling Windows Defender
Stderr from the command:
powershell.exe : Invoke-WebRequest : Unable to connect to the remote server
+ CategoryInfo : NotSpecified: (Invoke-WebReque...e remote server:String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
At C:\tmp\vagrant-shell.ps1:35 char:3
+ Invoke-WebRequest -Uri "$shutUp10DownloadUrl" -OutFile $shutUp10Rep ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invok
e-WebRequest], WebException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeW
ebRequestCommand
. : The term 'C:\Users\vagrant\AppData\Local\Temp\OOSU10.exe' is not recognized as the name of a
cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path
was included, verify that the path is correct and try again.
At C:\tmp\vagrant-shell.ps1:36 char:5
+ . $shutUp10RepoPath c:\vagrant\resources\windows\shutup10.cfg /quie ...
+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\Users\vagran...Temp\OOSU10.exe:String) [], Comm
andNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Do you have any ideas what might be causing it?
from detectionlab.
clong
commented on May 28, 2024
@BaffledJimmy this is a different issue. Your win10 host had trouble reaching an external website rather than joining the domain. I'll triage this in the task you opened.
from detectionlab.
Related Issues (20)
- "As of 2023-01-01, DetectionLab is no longer being actively maintained". What is an alternative? HOT 5
- AWS AMI not anymore available HOT 2
- Trouble installed using Proxmox. Broken pipe / use of closed network connection
- Winpcap chocolatey installation faliure HOT 1
- Repositorio del backed
- Fork of detectionlab HOT 3
- Expired TLS certificate on ping.detectionlab.network, preventing retrieval of the preseed config for ESXi deployment HOT 3
- An error occurred executing a remote WinRM command
- Everything installs except Velociraptor HOT 7
- Vagrant up error: Failed to power on '/path/filename.vmx
- error in wef and win10 provision: much needed help HOT 6
- Windows Activation Issues During Deployment
- Can't access Velociraptor HOT 3
- Vagrant Timeout Issue with VMware Fusion on MacBook with M1 Chip HOT 3
- error when I configure DetectionLab in proxmax VE.
- error executing "/tmp/terraform_1945368180.sh": wait: remote command exited │ without exit status or exit signal
- Install-AtomicRedTeam : The term 'Install-AtomicRedTeam' is not recognized as the name of a cmdlet
- velociraptor instoling prablome HOT 1
- Create with the WEF by vagrant, got a warning: "WARNING: Try #1 of .NET framework install failed with exit code '87'. Trying again."
- WEF Install Issues
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from detectionlab.