Error while joining Client server to a domain
I have a lab setup of Windows Server 2022 machine in Oracle VirtualBox to connect to an existing Active Directory (AD) domain but are facing network connectivity and DNS resolution issues. Network adapter is set to Bridged for both AD and normal server.
Current Lab Setup:
AD Server (Windows Server 2019) - Already Configured
- IP: 10.0.2.100
- Subnet Mask: 255.255.255.0
- Default Gateway: 10.0.2.2
- Preferred DNS: 10.0.2.100
- Roles Installed: AD DS, DNS, DHCP, DFS
- Forward Lookup Zone: Configured
- Reverse Lookup Zone: Configured (No PTR records yet)
- Forward Lookup Zone: Configured
- Roles Installed: AD DS, DNS, DHCP, DFS
- Preferred DNS: 10.0.2.100
- Default Gateway: 10.0.2.2
- Subnet Mask: 255.255.255.0
- New Server (Windows Server 2022) - Issue Occurs Here
- IP: 10.0.2.101
- Subnet Mask: 255.255.255.0
- Default Gateway: 10.0.2.2
- Preferred DNS: 10.0.2.100 (AD Server IP)
- Not yet joined to the domain.
- Ping to AD Server (10.0.2.100) works.
Troubleshooting Steps Taken So Far:
✅ Checked network settings (Static IP assigned correctly). ✅ Disabled and re-enabled network adapters on both servers. ✅ Rebooted both servers after reconfiguring DNS. ✅ Disabled Windows Firewall on both servers. ✅ Confirmed DNS settings (Forward Lookup Zone configured, Reverse Lookup Zone created but no PTR records yet).
Assistance Needed:
- Why is the new server (2022) unable to reach the AD Server (2019) via ping or DNS?
- Is NAT the correct network setting in VirtualBox, or should another mode be used (Bridged, Host-Only, Internal, etc.)?
- Any additional DNS or firewall settings required for proper connectivity?