Question

Samba server not really authenticating XP users at logon

Asked by: effincomputers

I am replacing a Windows 2k server with an Ubuntu 9.04 desktop running the Samba service. I need it to not only act as a file sharing server, but also authenticating server for XP Pro workstations at login for the domain.
I set the "server" up to be on the domain, be the domain controller, provide security, etc.. I duplicated the users on the 2k domain in the Samba setup. And after turning the 2k server off, I was able to log those users on. So I thought I was 90% of the way there.
But I soon found that I could not login the users (to the Samba server) that were only in the Samba setup, and not the 2k domain setup. Furthermore, I had to of logged on as those users onto the XP computers already, to be able to log them on when the Samba server was the only server in effect. Without this, I got an error message that the domain could not be found.
I then tested it further. I changed the samba user password, and tried to use that new password at the XP logon prompt. The new samba password did not work. The original 2k password did. But then, of course, SAmba shares were inaccessible. What am I doing wrong?
Thanks in advance.
Here's my samba.conf:

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = domain-name
netbios name = SERVER


# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = yes

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
domain master = yes
domain master = yes
preferred master = yes

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
security = user
; guest ok = no
; guest account = nobody
username map = /etc/samba/smbusers

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
; guest ok = no
; read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
; browseable = yes
; read only = yes
; guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom

[share1]
path = /home/user/Public/shares/share1
writeable = yes
; browseable = yes
valid users = user1, user2


[share2]
path = /home/user/Public/shares/share2
writeable = yes
; browseable = yes
valid users = user1, user2

This question is in progress. Our experts are working on an answer right now.
Sign up for immediate access to the solution once it becomes available.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2009-10-22 at 18:23:22ID24836754
Tags

samba

,

ubuntu

,

linux

Topics

Samba File Server

,

Samba File Sharing

,

Linux Network Security

Participating Experts
4
Points
500
Comments
16

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. samba printer
    acess denie un able to connect It show when I connect the printer that connect to linux samba server How can i fix
  2. Ubuntu/Windows Network
    I posted this originally under Ubuntu but no one has been able to solve the problem so her it is for the Windows experts as I feel it is probably a problem with my Windows Network set up which is preventing access. According to Ubuntu it should show the machines of a Windows...
  3. Samba not writeable
    Good morning, Ive been trying to share the htdocs folder on my linux PC, to allow windows to edit the files, however I can only get to see the folder to open in read-only. Im not bothered about security at the moment, as its only a testbed, but cannot even get it working to ...

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: oocytePosted on 2009-10-22 at 18:36:30ID: 25640742

Did you create the machines with smbpasswd -a -m ?

     -m
         This option tells smbpasswd that the account being
         changed is a MACHINE account. Currently this is used
         when Samba is being used as an NT Primary Domain
         Controller.
         This option is only available when running smbpasswd as
         root.

Also, you need to go on every windows machine and disjoin them from the original W2K domain, and "net join" them to your new Samba PDC.


This doc is sort of out-dated, but the procedure still applies:

http://daniel.fiser.cz/?samba

 

by: effincomputersPosted on 2009-10-22 at 18:59:52ID: 25640840

Thanks for the suggestion oocyte. I'll have to look into it tomorrow. I was looking into allowing the server to create machine account on the fly. I was going to try to enable that tomorrow. But first I'm going to try your method. To be clear about what your suggestion is, I would enter:
$ smbpasswd -a -m <machine-name>$
 at the terminal for each computer that's going to be in the domain?
Then take the computers out of the domain, at the computers themselves, and then rejoin the domain?
When I try that, if I run the $ smbpasswd -a -m <machine-name>$  command, will the "trust" between the XP and domain already exist?
Thanks

 

by: oocytePosted on 2009-10-22 at 19:13:22ID: 25640890

The trust will get established when you create the machine in the samba database.

A while back when I was messing around with samba, I added the machine first, then joined it to the domain.  I have no tried the other way around to know if it works or not.

Something worth noting: when you create the add machine scripts in smb.conf, smbd do it by adding the machine first before allowing the machine to join the domain.


 

by: effincomputersPosted on 2009-10-26 at 17:16:43ID: 25668293

I should be able to try this tomorrow. We'll see what happens. Thanks again.

 

by: it4sohoPosted on 2009-10-27 at 10:19:37ID: 25674975

You said earlier that you joined the Linux server to the W2K AD domain. Well, once your turned off that server, that domain went away. Just because Linux is a server OS and joined the AD domain, doesn't mean it became a domain server for that domain.

For your Linux server to authenticate users, it needs to be setup as a Domain Controller. The FIRST change you'll have to make is that one of the repeated lines:
domain master = yes
in your smb.conf file needs to be changed to:
domain logons = yes

Read more (a LOT more) at
https://help.ubuntu.com/8.10/serverguide/C/samba-dc.html

Finally, know that migrating users (and computers) from a Windows 2000 (Active Directory) server to a Linux Samba (Primary Domain Controller) server is not trivial. You actually LOSE a lot of functionality by "degrading" your domain from an AD one to a PDC one. (Personally, I continue to run my Win2K server in a VM on my CentOS 5 Samba Server!)

Good Luck!

Dan
IT4SOHO

 

by: effincomputersPosted on 2009-10-27 at 16:36:41ID: 25678826

Thanks it4soho. I do see that double entry for domain master. But domain logon is already in there, and it's set to "yes".
Thank you for that article. I think the most helpful of the main page from that link will be "system group needs to be mapped to the Windows Domain Admins group. Using the net utility".
Because when I tried creating a machine account, with the command sudo smbpasswd -a -m computername$
I got an error- "failed to modify password entry for user computername$"
I tried going through the process of trying to get a computer on the domain, by disconnecting it from the existing domain, and then reconnecting to the Samba domain. At the point of entering the user id and password of an account that can add the computer to the domain, I got the following error "The following error occurred attempting to join the domain "domainname". The user name could not be found."
I guess I can map that system group and use a member account of that group to be the authorizing user id and password. Any ideas on why I can' t create a machine account manually?

 

by: it4sohoPosted on 2009-10-28 at 04:19:12ID: 25681936

A quick note -- when you use the -m option to smbpasswd, it is telling it to put the $ at the end of the machine name, so you should NOT be using
  sudo smbpasswd -a -m computername$
rather, it should be
  sudo smbpasswd -a -m computername

That fix alone may resolve your problem, as the "name not found" is the result of the smbpasswd failing.

Good Luck!

Dan
IT4SOHO

 

by: effincomputersPosted on 2009-10-29 at 12:30:33ID: 25697347

I believed I ran the command  without the $ on the end. But I tried it again, just to make sure. And I ended up getting the same error, "Failed to modify password entry for user computername$" I created the user name in user manager, and tried again. No luck. Same error.

So I tried that command in the reference you gave me:
sudo net groupmap add ntgroup="Domain Admins" unixgroup=sysadmin rid=512 type=d

I created the two groups "domainadmin" and "sysadmin". I modified the command to:
sudo net groupmap add ntgroup="Domain Admins" unixgroup=sysadmin rid=512 type=d
 and I got the following outcome:

[2009/10/29 15:25:32,  0] param/loadparm.c:lp_do_parameter(7203)
  Ignoring unknown parameter "domain admin group"
[2009/10/29 15:25:32,  0] param/loadparm.c:lp_do_parameter(7203)
  Ignoring unknown parameter "domain admin users"
Successfully added group domainadmin to the mapping db as a domain group


 

by: effincomputersPosted on 2009-10-29 at 13:15:56ID: 25697791

After I tried what's mentioned above, I restarted the samba service and retried adding that computer to the domain. I removed it from the present domain, put it on a switch that's only connected to the samba server, and retried adding to the domain (after rebooting). When I enter the new domain name to be added into, I get a prompt for a user id and password for an account that has these permissions. I tried entering the user id added to the domainadmin group. I got an error "The user name could not be found". When I enter a user id that's added to that group, but not added as a samba user, I get a different error "logon failure: unknown user name or bad password". When I then add that user as a Samba user, I get the first error- "The user name could not be found". So, this process is talking to the samba server. But it's not letting me do what I want to do- add the computer to the domain.

 

by: effincomputersPosted on 2009-10-29 at 17:56:46ID: 25699493

I've been searching everywhere for answers. And I have seen quite a few people who have run into this exact problem. But each and every one of them has gone unresolved. What do I have to do to make this one the exception?

 

by: it4sohoPosted on 2009-10-30 at 10:37:32ID: 25705192

Let's check to make sure everything is in place:

For what I'm typing below, I'm assuming that the system name (netbios) is "system-01" and that it is all lower case (case DOES matter in this instance)

1) There must be an entry in /etc/passwd for the system, for example:
   system-01$:x:16001:16000:Machine Account:/dev/null:/sbin/nologin

HERE, in /etc/passwd, you DO have to place the $ after the name.

If the entry is NOT there, use the command:
  # adduser -u 16001 -g 16000 -c "Machine Account" -h /dev/null -M -s /sbin/nologin 'system-01$'

DO NOT give the account a password!

2) There must be an entry in the SAMBA password file for the system
  # pdbedit -L system-01$
  system05$:16001:Machine Account

If the entry is NOT there, use the command:
  # smbpasswd -a -m system-01

DO NOT put the $ in (it is added by the use of the -m option)

3) JUST FOR NOW - add the root user to the Samba users list. For demo purposes, make the password "Temp"
  # smbpasswd -a root
  <enter Temp twice -- ignoring the warnings!>

4) Attempt to join the system named "system-01" to the domain -- when prompted, use the username "root" and the password "Temp"

You should NOT get a "user name could not be found error"....

After this, we'll work on getting a "real" user to be a domain admin user whose credentials can be used to add a system to the domain.

Let me know how this goes...

Dan
IT4SOHO

 

by: effincomputersPosted on 2009-10-31 at 05:32:36ID: 25709468

Thanks it4soho. I'm going to check thoroughly on each detail once I get back in to that location. Have a great weekend.

 

by: deroodePosted on 2010-01-14 at 03:45:35ID: 26312930

Just chiming in, not very much expertise on samba servers...

I read in your samba.conf config file:

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no

and then it's what it4soho suggested on configuring samba...

 

by: effincomputersPosted on 2010-04-29 at 07:23:52ID: 32346165

I was never able to find a solution for this. Please abandon this question completely.

 

by: zakar1aPosted on 2011-03-08 at 13:39:21ID: 35074057

@effincomputers: do you know that you have to login with the "root" username before you can use any other username? Try that, login with root and see what you get and paste me the error

 

by: it4sohoPosted on 2011-05-23 at 10:47:18ID: 35817564

Although the author asked for this question to be abandoned, I thought I might add a little light to some of the issues he was having.

1) Joining Samba to a Win2K (or 2k3 or 2k8) AD domain makes it a member of the AD domain, not a server on that domain. There is a world of difference between being a file server on an AD domain, and being an AD server.

  To be clear -- Samba version 3.x (including 3.5) is capable of JOINING an AD domain, but is NOT (and never will be) capable of being an AD server itself. That is what Samba 4 is about. In the mean time, Samba 3.x very much IS capable of being a PDC (or BDC) in an older "NT style" of Domain environment.

2) When you switched Samba over from being an AD member to being a PDC (changing the smb.conf file), Samba automatically created a new "Domain ID" (my term, not the MS term which is an SID).... that is, the ID that is pre-pended to all user and/or group IDs on the Domain to ensure that different domains, even if called the same name, don't interact with each other "accidentally".

  As a result of the above, the machine accounts for all machines in the AD domain were immediately invalidated when you created the PDC domain in Samba. Furthermore, if you created the PDC in the same name as the previous AD domain name, then the machines got REALLY confused -- after all, you went BACKWARDS in technology, and they just weren't programmed for that (it's beyond the MS engineers' comprehension why someone might want to move BACKWARDS in technology!)

So long as the domain names matched, the windows hosts (client systems) would not change the domain ID, so any attempt to join the PDC domain would fail. Now there is one curious thing to note here -- in Windows, there is no way to manipulate the domain ID value -- it's just not permitted as a security measure... but in Samba, it most certainly IS possible to adjust that value (it's stored in the secrets.tdb file).... that being said, its simply "better form" to re-name the domain and join the client systems to the new domain with the new ID (or SID).

For more information, including debugging tips, read Chapter 6 in the official Samba HowTo
  http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/domain-member.html

I hope this helps someone in the future!

Dan
IT4SOHO

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...