Win10 Hanging After Joining Domain #21
Labels
Comments
|
|
Correct join looks like this: |
|
Not limited to VMWare - I have experienced this twice now on VirtualBox Version 5.1.30 In both cases, reload --provision corrected it. |
|
I'm having an issue with the win10 box joining the domain. [VirtualBox v5.2.6.r.120] ....vagrant reload --provision win10: Stderr from the command: powershell.exe : Add-Computer : Computer 'win10' failed to join domain 'windomain.local' from its current
ception |
|
Hi @labgeek18 - can you check the following? :
That error message indicates that the Win10 host can't successfully connect to or resolve the DC host |
|
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.
|
|
Still trying to run this down. Latest updates appear to be here: hashicorp/vagrant#8639 |
|
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 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! |
|
Closing this issue due to inactivity. It rarely happens now and is easily fixed with a reload. |
|
Re-opening this as I think this still happens a fair amount |
|
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. Debug output: |
|
This hasn't been an issue for quite some time now (knocks on wood). Marking as closed. |
|
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 DC host is all online and pingable. There is an entry for dc.windomain.local in the host file on w10. Results from third reload / provision: Do you have any ideas what might be causing it? |
|
@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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: