SERVER 2019 No logon on RDS SESSION DUE TO A AD NO ANSWEARING

Alexandre BARBOSA 1 Reputation point
2020-12-12T14:53:49.837+00:00

HI

a setup two VMs RUNNING SERVER 2019 STD.

VM1 AD / DNS /DHCP
VM2 RDS

I follow the process to setup the both VMS but every days all the users loose the AD access.
so they can't SCAN on server or they can't logon RDS server.

this issue make me crazy please could you help me to find a solution

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,444 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,227 questions
0 comments No comments
{count} votes

8 answers

Sort by: Most helpful
  1. Dave Patrick 426K Reputation points MVP
    2020-12-12T15:14:18.183+00:00

    Pretty vague but I'd check the domain controller and problem members all have the static ip address of domain controller listed for DNS on connection properties and no others such as router or public DNS

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

    0 comments No comments

  2. Alexandre BARBOSA 1 Reputation point
    2020-12-13T18:53:03.793+00:00

    hi Patrick

    thanks for your answer . to help us, i give to you more informations about my customer config :
    an hyoer V server on windows 2019 run to VMS.
    the AD VM IP 192.168.1.3 and the RDS VM IP 192.168.1.4

    On the RDS server have got every 6 hours the netlogon error 5719
    I still have an error dns number 10016
    and the error 1129 about group policy issue.

    when i am logged in the AD server i can't see the both server on the server control panel
    when i am logged in RDS SERVER i have an target kerberos issue when i wan't to see the AD server.

    thank you for helping me.

    0 comments No comments

  3. Dave Patrick 426K Reputation points MVP
    2020-12-13T19:00:46.22+00:00

    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:\problemRDS.txt

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

    0 comments No comments

  4. Alexandre BARBOSA 1 Reputation point
    2020-12-13T19:21:33.97+00:00
    0 comments No comments

  5. Dave Patrick 426K Reputation points MVP
    2020-12-13T19:36:55.337+00:00
    • On SRVADROBAT remove the google public DNS (8.8.8.8) from connection properties.
    • There also appears to be an IPv6 DHCP server on the network (possibly a router?) If not configured correctly this will cause no end to grief for active directory DNS So I'd turn this off on router.
    • On SRVRDSROBAT remove the google public DNS (8.8.8.8) from connection properties.

    After corrections on both do an ipconfig /flushdns, ipconfig /registerdns and restart the netlogon service.

    I didn't really look further than this because these are show stoppers. If problems persist after corrections then put up a new set of files to look at.

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

    0 comments No comments