Windows 10: Client can't join primary domain controller but secondary domain controller is working normal?

Hi team,I have two domain controller primary and secondary domain controller on windows server 2016 Standard. Now i have some issue with my client any new client PC with windows 10 can't join primary domain controller but my secondary domain controller is working fine. I notice that yesterday i have try to install WSUS server But this server is other Host then a new PC can't join and also client configure DNS primary domain controller also can't access to website but ping to IP is working fine. I'm not sure 100% with WSUS server. Any idea?Best Regards,Kimseng

:)

 

Anyone with domain controller migration experience?

I'm testing migration of our domain controllers on vmware from 2003 to 2008 before we go ahead with it on production. I have copies of two of the DCs in vmware, and two 2k8 installs. They're all host only with IPs in the same network. On the main 2k8 DC, I try and go through the migration process. But when it gets to the point of copying the data it gives an error:

The operation failed because:

The attempt failed to join this computer to the domain failed. "This operation is only allowed for the Primary Domain Controller of the domain."

Been googling this but not much luck so far

 

Trust relationship between client and domain controller faild

Our Primary Domain Controller physically failed and now is
off . Then I had to seize FSMO rolls to
additional DC in our Domain .All needed rolls seized successfully ( netdom query shows the succession ) . but now I can not get session to the shared folders on servers or any client in domain by
ip ( \ client-or-server-ip )and the message "
the trust relationship between this workstation and primary domain controller failed " is shown . plus I
have not any problem in Login to servers or clients and remote desktop is ok plus take session with name of server or client is ok
but ip is not working and the mentioned message above is given . Can any body help ???

 

Duplicated Domain Controllers

I was in the process of configuring Password and Desktop Background Polices at a company, but it has been unsuccessful so far. I tried ruining group policy updates on the client computers but not luck with that. I tried rejoining client computers to domain.

Initially I was told that there were 2 domain controllers with replication, only one has Group Policy Management configured.

After diving in, i realize there were 3 domain controllers , DC1,DC2,DC3.In the DNS entry it shows DC2 and DC3 have same IP Addresses. I'm not too sure if that's possible or if it may be the cause of the GPO issues. This is my first time coming across this
and working with more than one domain controller in a domain.

When I connect using remote desktop, DC2 and DC3 brings me to the same desktop.When i run a nslookup they both bring back the same IP Address.

The Domain Controllers Also encounter issues replicating.In Group Policy Management it shows that DC3 is inaccessible.

DC2 is the Primary Domain Controller.

Should i delete DC3?