Win10 Hanging After Joining Domain

[clong]

==> win10: PSComputerName   :
==> win10: Now join the domain
==> win10: HasSucceeded : True
==> win10: ComputerName : win10
==> win10: WARNING: The changes will take effect after you restart the computer win10.
==> win10: Setting timezone to UTC
==> win10: Hint: vagrant reload win10 --provision
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.

[clong]

==> 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.

[clong]

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```

[digital4rensics]

Not limited to VMWare - I have experienced this twice now on VirtualBox Version 5.1.30

In both cases, reload --provision corrected it.

[labgeek18]

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

[clong]

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

[labgeek18]

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.

[clong]

Still trying to run this down. Latest updates appear to be here: hashicorp/vagrant#8639

[mikeesparza]

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!

[clong]

Closing this issue due to inactivity. It rarely happens now and is easily fixed with a reload.

[clong]

Re-opening this as I think this still happens a fair amount