This is the story of how I finally replaced a Windows 2003 Domain Controller with a Linux based domain controller and used it with a mixture of Linux and Windows workstations. My main reason for doing this was to demonstrate that it could be done and to find out how. It is written in the form of a Howto, and hopefully it will be of use to other people trying the same exercise.
Acknowledgments:
This document is a continuation, if you will, of the Samba Howto that can be found at http://directory.fedoraproject.org/w...ntation#Howtos. To the author(s) of that document I offer my heartfelt thanks, but found that the document did not cover all the steps required to implement a Domain Controller using FDS. This document is my attempt to continue that document to include all necessary steps.
Needless to say, any error and omissions in this document are mine and mine alone: and I would appreciate it if you would let me know of any that you find.
Part 1 - Installing the Software
Background:
Over a number of years I have developed a home network that I use to test my wilder flights of fancy. Typically I use this setup to evaluate operating system, software packages, hardware components. I use it both for functional tests and performance testing, and so all the hardware is available to be re-used and re-configured at any time. The only exception to this are three disks that are reserved as data disks, and they contain either the original or backup copies of all data that I do not want to lose. For this reason, I tend to use separate disks for the operating system in all my machines, and keep the data on other disks.
So this is my testbed. It comprises two servers and three workstations. The whole is physically wired together and shared a single IP addressing scheme, but with a Windows 2003 PDC the Windows and Linux portions were effectively separate. This I wanted to rectify. I used the same hardware (from the Windows Server) but changed to a Fedora 8 system with Samba 3 and a Fedora Directory Server backend to manage user accounts.
For those hardware junkies amongst you this is the hardware that I used for my test network:
seagoon Domain Controller
Fedora 8 (Formerly Windows 2003)
Sempron 2800+, 576 MB Memory
Asus K8V-VM Motherboard
VIA K8M890 Integrated Graphics Controller
20 GB system disk
250 GB data disk
320 GB data disk
DVD+R
minnie Workstation
Fedora 8
Sempron 2800+, 512 MB Memory
Asus A7V400-MX Motherboard
Asus A9250 Graphics Controller
10 GB system disk
35 GB data disk
9 GB data disk
5 GB data disk
DVD+RW
bloodnock Workstation for testing
Fedora 8
Athlon 64 X2 3800+, 1 GB Memory
Asus M2N-MX SE+ Motherboard
Saffire Radeon X550 Graphics Controller
20 GB system disk
DVD+R
eccles General Purpose Workstation
Windows XP
Athlon 64 6000+, 2 GB Memory
Asus M2NPV-VM Motherboard
Asus EN7300GT Graphics Controller
80 GB system disk
DVD+R
DVD+RW
bluebottle Web Server
Fedora 8
Pentium III 550MHz, 512 MB Memory
HP Motherboard
ATI Radeon 7000 Graphics Controller
20 GB system disk
DVD+R
CD+RW
Prerequisites for the domain controller:
Fedora 8 clean install. I installed a fresh version of Fedora 8 for this, and added all the upgrades so that I had the latest versions of all the software packages. I installed a minimum number of packages - just enough to run the server and nothing else. I did not install any of the development packages, and only the Servers I needed (BIND, SMB, HTTP). Once I finished the install, I configured the Services so that only the minimum that I needed were started.
Samba SMB server. I used the latest from the release, 3.0.28.
Apache web server 2.2.8-1
DNS for the network. For this I used BIND 9.5.0-23, which was the latest. Prior to starting configuring the PDC I needed to set this up. This bit is fairly significant. It allows the Windows workstations to access the domain controller without requiring a third party modifications such as pGina. You will see from the list below that my domain is called "home" (imaginative) and uses the 192.168.1 addresses. The service records are there to enable Windows to identify and talk to the domain controller. This is the data that I used:
@ SOA seagoon root.seagoon.home. ( 7
3H
1H
1W
1H )
NS seagoon
seagoon IN 1H A 192.168.1.2
bloodnock IN 1H A 192.168.1.120
minnie IN 1H A 192.168.1.150
eccles IN 1H A 192.168.1.100
bluebottle IN 1H A 192.168.1.5
_ldap._tcp.dc._msdcs IN 1H SRV 0 100 389 seagoon
_ldap._tcp.pdc._msdcs IN 1H SRV 0 100 389 seagoon
IN 1H SRV 0 100 389 seagoon.home
_ldap._tcp IN 1H SRV 0 100 389 seagoon
_ldap._tcp.home-site._sites IN 1H SRV 0 100 389 seagoon
_ldap._tcp.home_site._sites.dc_msdcs IN 1H SRV 0 100 389 seagoon
_ldap._tcp.gc._msdcs IN 1H SRV 0 100 389 seagoon
_gc._tcp IN 1H SRV 0 100 3268 seagoon
_gc._tcp.home-site._sites IN 1H SRV 0 100 3268 seagoon
I wanted to use the openLDAP migrations tools, which I extracted from the openLDAP rpm file and copied to the /usr/share/openldap/migration directory.
Finally I needed the ol-schema-migration.pl tool mentioned in the howto; this can be obtained from http://directory.fedoraproject.org/d...ema-migrate.pl
Now we can begin configuring.
Firstly, add the necessary repositories so that we can get the latest version of the DS code
$ cd /etc/yum.repos.d
$ wget http://directory.fedoraproject.org/s...idmcommon.repo
$ wget http://directory.fedoraproject.org/sources/dirsrv.repo
Now install Fedora Directory Server software, and then configure it.
$ yum install fedora-ds
$ setup-ds-admin
In the interests of space I have just posted the replies I made to the setup script. The whole thing will not fit into this post, so I have just included my choices.
Choose a setup type [2]: 2
Computer name [seagoon]: seagoon.home
System User [nobody]:
System Group [nobody]:
Do you want to register this software with an existing
configuration directory server? [no]:
Please enter the administrator ID for the configuration directory
Configuration directory server administrator ID [admin]:
Password
Password (confirm)
Administration Domain [home]
Directory server network port [389]
Directory server identifier [seagoon]
Suffix [dc=home]
Directory Manager DN [cn=Directory Manager]
Password
Password (confirm)
Administration port [9830]
Log file is '/tmp/setupqbdJiS.log'
Just test to see if it's working - this will open the admin screen. If it does, everything is working fine and you can breathe again. If not, it's time to troubleshoot. Check the logs, or repeat the install
$ fedora-idm-console
Now create an ldif file to add the samba schema to FDS and load it into the server:
$ ./ol-schema-migrate.pl -b /usr/share/doc/samba-*/LDAP/samba.schema
> /etc/dirsrv/slapd-seagoon/schema/61samba.ldif
$ service dirsrv restart
Use the Authentication application to enable LDAP and Winbind for user information and LDAP, Winbind and SMB for authentication.


Reply With Quote
m_process() - Processing configuration file "/etc/samba/smb.conf"
