I've been trying to setup Samba as an AD DC on Ubuntu Server 20.04 but keep running into some issues.
Some information:
Domain = mvz.intern
DC { hostname = dc02.mvz.intern - ipv4 = 192.168.50.239 }
PC { hostname = pc - ipv4 = 192.168.50.163
dns1 = dc - dns2 = router }
DC is a Hyper V VM Ubuntu Server 20.04
PC is the Hyper V host ( regular workstation )
Hosts on client:
192.168.50.239 dc02.mvz.intern
#192.168.50.239 dc02
#192.168.50.239 mvz.intern
DC netplan
config (nameserver changed to 192.168.50.239
):
![Screenshot 1](https://i.stack.imgur.com/L6jzn.jpg)
DC smb.conf
(tried DNS forwarder 8.8.8.8
):
![Screenshot 2](https://i.stack.imgur.com/KiWux.jpg)
I missed out on setting the DC as its own nameserver. After fixing that, netplan
apply and rebooting both systems, I'm still not able to ping neither DC from my PC nor my PC from DC. If I nslookup
the domain, it says server unknown
, but has the correct IP.
samba-tool domain forest list
shows me the forest function level so the domain seems to be up.
Trying to:
AddComputer -DomainName MVZ.INTERN
on the client isn't able to establish a connection, of course.
I've heard about the collision of SMB versions. Could this be the issue?
Or even a Chicken or the egg thing (Hyper-V)?
How would you troubleshoot this?
The guide I followed mentioned setting hostname+fqdn as hostname, e.g. dc02.mvz.intern, could this be causing trouble?