I’m stuck trying to get Windows Server 2025 to function as a domain controller. The setup goes smoothly like in past versions. But when it comes time to connect a workstation it just errors out saying the domain could not be contacted. My network shows Domain network and not Public. I’ve restarted the NLA service. I’ve disabled and re-enabled the network adapter.
Please help!
Loading Zentyal Server in a virtual machine. Utterly pathetic Microsoft.
Quick questions:
Is 2025 acting as: DNS or DHCP for your network? Is it assigning out DNS to itself? Do you try to join domain as XYZ.Local? Is it virtualized (where it can end up on the other side of a VLAN?)
I’ve done enough 2025 domain installs that it just flies through… trying to think of some snags you may have but I don’t have enough information. The workstations you are trying to connect are Windows 10/11, none are older, and all are updated on current update cycle?
No software to block transport (like McAfee/Norton garbage)
Is this the first dc in a new forest? is it the first 2025 server in an existing forest? If so have you run dcpromo?
I appreciate the response but I finally gave up on Windows Server 2025. I didn’t have enough time this weekend to keep troubleshooting the issue.
I experienced something very similar to this guy. Except even with all the fixes applied it still doesn’t work. Oh well.
oh the public vs private network … that can be fixed right in the network setting gui of any windows 10 / 11. It’s literally a check box or circle. Found out about that issue when I was trying to connect to my local nas boxes.
