SMB 3.0 on RH9

How do I setup SMB3.0 as a Domain Controller?  ( I think I have this part...)

Then when I attempt to add a windows machine from its System Properties page.  It fails,  it says I do not have permission..

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I'm kinda new to the world of linux but I'm assuming you are refering to Samba?? This is what i believe you need to do to get up and running. Assuming you have your smb.conf file setup correctly all you need to do is add users.

Step 1

Adduser {USERNAME}

Step 2

smbpasswd -a {USERNAME} (in step 1)

Then you should be set. However you will need to join the domain with a user that has sufficient previleges. I used root.......I believe i just did smbpasswd -a root, then entered a password that was different from the local root account. Note however i was only experiementing with samba and linux, if this is a production Samba server you may not want to use root.

I hope this helps


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
you need to enter the root name/password to add users to the domain, and I think you may actually have to add that user first to samba with the smbpassward -a root
Hii ,
To setup Samba as Primary Domain Controller

Add the following to the global section of your smb.conf file.

# The domain you want to be a PDC for
workgroup = SIMPLE

# Tell Samba to use domain logons
domain logons = yes

# User-level security. Users must
# authenticate themselves with
# valid username and password
security = user

# Set to yes so that nmbd participates
# in local master browser
# elections
local master = yes

# Set Os level value to make sure nmbd
# wins local browse master
# elections. 65 should beat everyone
# according to the man page
os level = 65

# Give nmbd an advantage in local
# master browser elections
preferred master = yes

# Set so that nmbd claims a unique
# NetBIOS name identifying it as
# a domain master
domain master = yes

# The following share is required to support
# domain logons. The directory may be
# created anywhere on your system. Make
# sure the share is non-writeable and also
# not a public share.
comment = The domain logon service
path = /usr/local/samba/netlogon
public = no
writeable = no

The next thing to do is create the users on the Samba server that is to act as the domain controller. You can do this using the useradd command.

useradd –-g smbuser –-d /dev/null –-s /dev/null ntuser

As you can see, both shell and home directory for ntuser is set to /dev/null. If your Windows users are not required to access the Unix box, you should use the above to deny access to the machine. Passwords are also not required to be set because Samba keeps the password hash in a separate file specified in the configuration file.

# Path to Samba password file
# Make sure only root has read/write access
smb passwd file = /usr/local/samba/smbpasswd

After adding a user (you can also use vipw to add a user), you need to add the user to the samba password database.

“smbpasswd –a” will add all users in Unix passwd file to smbpasswd file. The usage and syntax is similar to the Unix passwd command. To change a users’ password use “smbpasswd username”.

That will be enough for Samba to start authenticating Windows 9X clients. For NT workstations, some more work is to be done. You have to create a machine account for each NT client that will logon. A machine account is simply a regular /etc/passwd entry, with a “$” appended to the name of the NT machine.

useradd –-g smbuser -–d /dev/null -–s /dev/null ntclient$

Now add it to the password database

smbpasswd –a –m ntclient (the $ at the end is not required)

Samba can now accept logons from a NT client.

As you can see, configuring samba as a domain controller and domain member is a fairly easy job. The flip side is that since samba is the result of major amounts of hacking and reverse engineering, it doesn’t have all the functionality of a proper domain controller.


Karl Heinz KremerCommented:
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:
Split between yuzh and anupnellip
Please leave any comments here within the next four days.


EE Cleanup Volunteer
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.