Monday, June 7, 2010

How to install and configure Samba PDC domain controller on linux redhat rhel5

Sponsored Links
Samba PDC is used for centralized authentication and domain control of Windows
operating systems.

Here we will set a samba PDC machine with domain name lap.work and create some
users. And we will check whether these users are able to login to this domain from different
machines.

In this example we are working on rhel5. It will also work on other distributions like Centos, Fedora, SUSE etc.

Samba PDC Machine:
rhel 5.4
IP : 192.168.0.25

Windows Client:
Windows  XP Professional SP2
Computer Name : lap-xp
Domain Name : lap.work
IP : 192.168.0.26

Installation:

Install samba packages:
[root@sambapdc ~]# yum install samba*

Configuration:

open the samba configuration file and make the following edits.
[root@sambapdc ~]# vim /etc/samba/smb.conf

Uncomment or edit the lines as shown below.

In global settings:

workgroup = lap.work #domain name
server string = Samba PDC Server #as host name. just to identify
netbios name = samba #netbios name for communication
local master = yes
preferred master = yes
domain master = yes
domain logons = yes
logon path = \\%L\Profiles\%U #profile entry
security = user
passdb backend = tdbsam

In share definishions:

[homes]
browseable = yes
writable = yes

[netlogon]
path = /home/netlogon
writable = no

[Profiles]
path = /home/profiles
create mask = 0755
directory mask = 0755
writable = yes #should give. Else you will get ACCESS DENIED errors

Now create the following directories:

[root@sambapdc ~]# mkdir -m 1777 /home/profiles
[root@sambapdc ~]# mkdir -m 1777 /home/netlogon

Attaching a windows machine:

Now create a group named machine and add a user with the name of windows client
[root@sambapdc ~]# groupadd -g 200 machine
[root@sambapdc ~]# useradd -d /dev/null -g 200 -s /sbin/nologin lap-xp$
Where lap-xp is the name of the machine we are attaching to samba PDC
[root@sambapdc ~]# smbpasswd -m -a lap-xp

Start the samba service:

[root@sambapdc ~]# service smb start
[root@sambapdc ~]# chkconfig smb on
Run testparm and test your configuration settings:
[root@sambapdc ~]# testparm
[root@sambapdc ~]# smbpasswd -a root
[root@sambapdc ~]# smbpasswd -e root

Add two more users for testing:

#useradd user1
#smbpasswd -a user1
#smbpasswd -e user
#useradd user2
#smbpasswd -a user2
#smbpasswd -e user2
[root@sambapdc ~]# service smb restart

On windows machine:

Right click the My Computer icon
Take properties
Take Computer name tab
Add the system to lap.work domain
you will be prompted for a username and password. Give root and its password.
System may need to restart

you can see that when we are logged as user1 a directory user1 will be created in /home/profiles
in samba PDC machine. This will be the home directory of that user. He will he able to login
from all machines in this domain and will be getting to this same directory.

Thats it. Enjoy. Have fun.
Sponsored Links

4 comments:

  1. By following this article, anyone can get the DNS error message while connecting this domain from any win XP...

    we can resolve it either by installing DNS server or enabling WINS support in smb.conf

    ReplyDelete
  2. By following this article, anyone can get the DNS error message while connecting this domain from any win XP...

    we can resolve it either by installing DNS server or enabling WINS support in smb.conf

    ReplyDelete
  3. Thank you....It is successfully working for me

    ReplyDelete

  4. I am running samba PDC on CentOS 6.3 . The windows xp could able to join as member of the PDC domain.But could able to be a roaming profile.

    My Doubt is should i have to do any patches in the registry of the Windows XP ? Kindly help me clear this below error.


    ********************************************

    Your roaming profile is not available. You
    are logged on with the locally stored
    profile. Changes to the profile will not be
    copied to the server. Possible causes of
    this error include network problems or
    insufficient security rights. If this problem
    persists, contact your network
    administrator.
    ******************************

    ReplyDelete

Be nice. That's all.