Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adfs2 failed to join domain windomain.local #3

Open
HtmlMak opened this issue Feb 16, 2018 · 4 comments
Open

adfs2 failed to join domain windomain.local #3

HtmlMak opened this issue Feb 16, 2018 · 4 comments

Comments

@HtmlMak
Copy link

HtmlMak commented Feb 16, 2018

When launching vagrant up adfs2, there is no connection. Do I need to make any settings after starting DC? Or maybe incompatibility with virtualbox 5.2 and vagrant 2.0?

Log:

Ooops, workgroup!
Join the domain
First, set DNS to DC to join the domain


__GENUS          : 2
__CLASS          : __PARAMETERS
__SUPERCLASS     :
__DYNASTY        : __PARAMETERS
__RELPATH        :
__PROPERTY_COUNT : 1
__DERIVATION     : {}
__SERVER         :
__NAMESPACE      :
__PATH           :
ReturnValue      : 0
PSComputerName   :

Now join the domain
HasSucceeded : False
ComputerName : adfs2

Hint: vagrant reload adfs2 --provision




Stderr from the command:

powershell.exe : Add-Computer : Computer 'adfs2' failed to join domain 'windomain.local' from its current workgroup 'WORKGROUP' with
    + CategoryInfo          : NotSpecified: (Add-Computer : ...ORKGROUP' with :String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
following error message: The specified domain either does not exist or could not be contacted.
At C:\vagrant\scripts\join-domain.ps1:17 char:1
+ Add-Computer -DomainName "windomain.local" -credential $DomainCred -PassThru
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (adfs2:String) [Add-Computer], InvalidOperationException
    + FullyQualifiedErrorId : FailToJoinDomainFromWorkgroup,Microsoft.PowerShell.Commands.AddComputerCommand
@danielmenezesbr
Copy link
Contributor

I got the same error.

In my case, the root cause was SID duplication. It causes problems to join into DC.

My workaround:

  • Use opentable/win-2012r2-standard-amd64-nocm box for DC;
  • Use opentable/win-2012r2-datacenter-amd64-nocm for second box (in your case adfs2; in my case web).

@StefanScherer
Copy link
Owner

Maybe a look at the https://github.com/clong/DetectionLab may help. This is also a domain setup inspired by this repo.

@clong
Copy link

clong commented Mar 23, 2019

Ironically I'm running into the same issue as well (albeit at a different point): clong/DetectionLab#221

Not sure how it's possible that the domain controller can't find the domain :-/

@StefanScherer
Copy link
Owner

Thanks for the hint and solution clong/DetectionLab#222
I haven't used the Vagrant setup lately, only the steps to create a DC in an Azure VM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants