The server passed all tests with the only exception being: There are warning or error events within the last 24 hours after the SYSVOL has been shared.
In trying to troubleshoot I ran dcdiag on both the server and client.
Nslookup is correctly resolving for both forward and reverse lookup zones: Server: Ĭ:\Users\simon>nslookup Minimum = 16ms, Maximum = 17ms, Average = 16ms Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Īpproximate round trip times in milli-seconds: I am able to ping the AD (simon.adtest) and the server (): Reply from 45.76.xx.xx: bytes=32 time=17ms TTL=116 : 45.76.xx.xx (correct address of AD/DNS server confirmed) : Intel(R) 82574L Gigabit Network Connection #2 Here is the ipconfig /all from the client: Windows IP Configuration It also should be noted that this is not a production system and I would not normally advocate lowering the firewall. It should be noted that the firewall has been disabled on both the server and client for troubleshooting. However no domain controllers could be contacted. The following domain controllers were identified by the query: In Windows 10, when attempting to join the domain, I get the message "An Active Directory Domain Controller (AC DC) for the domain "simon.adtest" could not be contacted", with further information: The query was for the SRV record for _ldap._tcp.dc._ The setup went smoothly but I can't get a client to connect to the DC. The client is a Windows 10 box on our internal LAN. The server is a vanilla Windows Server 2019 install on a public cloud computing enviromnent, setup following this virtualgyanis guide. I am setting up an AD/DNS server for development purposes, but am having difficulty connecting to it from any client.
0 kommentar(er)
