TECHNICAL · SYSTEMS
Setting up domains on Windows and Pardus/Linux
Over the past few weeks, I've been working on setting up domains and joining clients to them on both Windows and Pardus/Linux systems.
First, I configured Active Directory Domain Services on Windows Server. After setting up the Domain Controller, I adjusted the DNS and IP settings and joined a Windows client to the domain I created. I created domain users and tested centralized user management and signing in with a domain account.
Next, I built a similar setup in Pardus. I configured a Host-Only network so that a Pardus server running in VirtualBox could communicate with a physical Pardus client. I also used a NAT connection to give the server internet access.
On the Pardus side, I:
- Set up a Samba Active Directory Domain Controller.
- Created the ADLAB.TEST domain.
- Configured DNS, LDAP, and Kerberos services.
- Joined the physical Pardus client to the domain.
- Created centralized domain users.
- Tested Kerberos authentication with kinit.
- Signed in to the physical Pardus client with a domain user.
- Connected from the physical client to the virtual server via SSH.
These exercises gave me hands-on experience setting up both Windows Server- and Samba-based Active Directory, joining clients to domains, managing users centrally, and handling authentication.
Along the way, I worked with Active Directory, Samba AD DC, DNS, LDAP, Kerberos, SSSD, SSH, IP configuration, and VirtualBox networking modes.