Active Directory user unable to connect to computer connected to the domain.

Question

Hello,

In one of the offices of our firm we are experiencing issues with I suppose the Domain Controller.

On one of the computers User 1 is unable to sign in with their AD account on PC 1. User 2 has no issues logging in. At the same time User 1 has no issues logging in on PC 2. Not every computer in the office has this issue and not every AD user. All computers are connected in the same network and the same Domain. All users are Members Of the DomainUser group we have.

Answer 1

Hello

Thank you for your question and reaching out. I can understand you are having issues related to computers unable to connect to the domain.

1. Please ensure on your User computers DNS ip should be of your Domain controller.
2. Disable any Antivirus program or Windows firewall you may have for temporary purpose.
3. Please verify date and time should be same on Client and Domain controller.
4. On your Domain controller make sure DNS service is running and DC ip should be static and not DHCP ip.

------------------------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept as answer--

Answer 2

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log <- run on any domain controller
repadmin /showrepl >C:\repl.txt <- run on any domain controller
ipconfig /all > C:\dc1.txt <- run on domain controller 1
ipconfig /all > C:\dc2.txt <- run on domain controller 2
ipconfig /all > C:\dc3.txt <- run on domain controller 3
ipconfig /all > C:\problemworkstation.txt <- run on problem member

then put unzipped text files up on OneDrive and share a link.

Answer 3

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt
ipconfig /all > C:\dc3.txt
ipconfig /all > C:\problemworkstation.txt

then put unzipped text files up on OneDrive and share a link.

Answer 4

I'd check the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS.

--please don't forget to upvote and Accept as answer if the reply is helpful--