Cannot add to Domain

[enaugavule]

I've recently configured and setup a DC and AD account on Server 2019. Configured Hyper-V and ran AD, DC services and and also two other VM's for Windows XP and Ubuntu Desktop. This is a standalone setup and when I want to add windows XP and Ubuntu desktop on a the newly Domain created, it comes up with this error message below however I'm able to ping from server to clients and vice versa 

Please note I've tried the possible solutions below:

1. Turned off Firewall

2. entered the IP address static

3. Reset the Ad and DC server 3 times 

4. gone on other forums to find a solutions 

Appreciate if someone can assist 

[#2]

It's unlikely an old operating system like XP will be able to join a Server 2019 domain. Better to try a newer supported desktop operating system at least to confirm the domain controller is operational.

Try Windows 10 Enterprise on Microsoft Evaluation Center

[#3]

@Dave Patrick I've did what you had recommended and used the link to download Windows 10 Enterprise however I get the below error message:

I can ping from Point A to Point B and vice versa. I 'am not sure why its like this and also I've tried putting a static ip address and dynamic as well to see if it goes through, etc 

[#4]

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


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

[#5]

ok will do, shall I run this from the server or client machine?

[#6]

Both

[#7]

@Dave Patrick  I couldn't open up the link for OneDrive you had sent through.

[#8]

Please do not zip the files. Put the files up on OneDrive and share a link.

[#9]

got iit.

https://1drv.ms/u/s!AkYdYvMF_DB2gQFd-t-QweTzco4C?e=aoiMzY

[#10]

None of the files have contents. Do not edit the commands.

[#11]

You must enable SMBv1 on all Domain Controllers WIndows Server 2019

Thanks

[#12]

Hello.

I could not see in the pic. Are you entering the domain name or fully qualified domain name? Try entering the fqdn. Tell me how you.

Cheers

[#13]

@Dave Patrick this is what i get from the client machine 

[#14]

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on domain controller)
repadmin /showrepl >C:\repl.txt (run on domain controller)
ipconfig /all > C:\dc1.txt (run on domain controller)
ipconfig /all > C:\problemworkstation.txt (run on problem workstation)

[#15]

tried both still the same thing

[#16]

done
https://1drv.ms/u/s!AkYdYvMF_DB2gQFd-t-QweTzco4C?e=8rrG9T

[#17]

Is DC windows Server 2019?

[#18]

correct, running it on Hyper-V
Also note it is a standalone device which I 'am currently testing out before deploying the final production onsite.
I know it should be an easy one joining to a Domain however this is the worst experience I've had in trying to resolve something simple

[#19]

As I replied top: Was DC enable SMBv1? because with Windows 2008R2 or easier use smbv1 protocol to join domain. Thus if you wanna join Windows XP, enable smbv1 on DC force.

[#20 · Accepted solution]

On Jenserver I'd add server's own static ip address (192.168.1.76) listed for DNS then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service.

On the DESKTOP-T93V54F I'd add the static ip address (192.168.1.76) of domain controller listed for DNS and remove the IPv6 addresses