Using samba as a PDC, can't get on domain from XP Pro machines.....
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Using samba as a PDC, can't get on domain from XP Pro machines.....
Hey guys I am trying to use Samba as a PDC for my network, I am kind of new to the situation but have slowly been learning, I made a machine name for the computer that I am trying to connect to the domain in samba and linux itself, the machine's name is MEDIAPLAYER. The error I get is at the bottom.
# Samba config file created using SWAT
# from 192.168.1.101 (192.168.1.101)
# Date: 2008/07/09 15:10:11
[global]
netbios name = SHEASERVER
server string = SheaServer for the Shea Family
security = SHARE
log file = /var/log/samba/%m.log
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = cups
domain logons = Yes
preferred master = Yes
domain master = Yes
wins support = Yes
guest ok = Yes
printing = cups
print command =
lpq command = %p
lprm command =
[printers]
path = /home/smbprint
printer admin = @ntadmin, root
create mask = 0700
guest only = Yes
printable = Yes
use client driver = Yes
browseable = No
[print$]
comment = Printer Drivers
path = /usr/share/cups/drivers
write list = root, @ntadmin, sheaserver
read only = No
[cdrom]
comment = Samba server's CD-ROM
path = /media/cdrom0
locking = No
When I try to join the WORKGROUP domain on my XP Pro machine and log in as root it tells me that "An error occured when trying to join the WORKGROUP domain: The Parameter is incorrect"
As far as I understand, you have not added the MEDIAPLAYER$ user in /etc/passwd file, did you?
All samba users must be linux users too (or LDAP entries, but that's another story).
All you need (do I understand correctly?) is to setup a password/file server. In that case you do not need a PDC.
Well I want the users to be able to logon from the XP machines and automatically have their home directories mounted, so I don't really know if I need a PDC or an LDAP server.
oh and here are the few lines that matter from cat /etc/passwd
sheaserver:x:1000:1000:SheaServer,,,:/home/sheaserver:/bin/bash
smbprint:x:109:65534::/home/smbprint:/bin/false
openldap:x:110:114:OpenLDAP Server Account,,,:/var/lib/ldap:/bin/false
mysql:x:111:115:MySQL Server,,,:/var/lib/mysql:/bin/false
DShea-PC$:x:1001:1001:,,,:/home/DShea-PC$:/bin/bash
MEDIAPLAYER$:x:1002:1002:MEDIAPLAYER,,,:/home/MEDIAPLAYER$:/bin/bash
OK, that's odd.
The next thing I can think right now, is to delete MEDIAPLAYER$ user and try to add it from Windows. Add the add machine script to your smb.conf. My smb.conf on the production server (over 60 pcs) is:
Code:
server string = Samba Server Version %v
interfaces = eth0, lo
bind interfaces only = Yes
passdb backend = tdbsam:/etc/samba/passdb.tdb
pam password change = Yes
passwd program = /usr/bin/passwd '%u'
username map = /etc/samba/smbusers
unix password sync = Yes
client NTLMv2 auth = Yes
client lanman auth = No
client plaintext auth = No
log level = 2 passdb:5 auth:7 winbind:1
smb ports = 445
time server = Yes
add user script = /usr/sbin/useradd -g users -s /bin/bash -m %u
delete user script = /usr/sbin/userdel -rf %u
add group script = /usr/sbin/groupadd -f %g
add user to group script = /usr/sbin/usermod -G '%g' '%u'
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
logon path =
logon drive = P:
Believe me, it worked. One more thing. I just noticed that you used the WORKGROUP name. And I did not see and workgroup=WORKGROUP declaration. Unless you forgot to include it, it could be the problem. Also, please post the portion of /var/log/messages that is written when you try to join the domain.
I added the workgroup = WORKGROUP and it still didn't work with the machine script does it add the user automatically when the computer tries to join the domain? Anyways here is the log from the last time I tried to join the domain:
Code:
Jul 10 23:53:12 daneshea gconfd (root-10183): starting (version 2.16.1), pid 10183 user 'root'
Jul 10 23:53:12 daneshea gconfd (root-10183): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 10 23:53:12 daneshea gconfd (root-10183): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jul 10 23:53:12 daneshea gconfd (root-10183): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 10 23:53:12 daneshea gconfd (root-10183): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 10 23:53:12 daneshea gconfd (root-10183): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 10 23:53:42 daneshea gconfd (root-10183): SIGHUP received, reloading all databases
Jul 10 23:53:42 daneshea gconfd (root-10183): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 10 23:53:42 daneshea gconfd (root-10183): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jul 10 23:53:42 daneshea gconfd (root-10183): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 10 23:53:42 daneshea gconfd (root-10183): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 10 23:53:42 daneshea gconfd (root-10183): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 10 23:53:42 daneshea gconfd (root-10183): GConf server is not in use, shutting down.
Jul 10 23:53:42 daneshea gconfd (root-10183): Exiting
OK, let's review a couple of issues:
a. The log is not for samba. Either every logged action goes to /var/log/samba/smbd/log (or something like that), or, Win did not connected to server!
b. SMB users MUST be unix users before anything else.
c. With the add machine script, you ensure that an account with name computer$ and description "Machine" will be automatically added to /etc/passwd file.
d. If you wish, you can add a user during the trust computer initialization (computer join the domain).
To me, it seems that the problem is on the windows side. Try to use a different workgroup name, such as home. If that fails too, then we see.
also I'm missing your workgroup = variable in your smb.conf file, or did you leave it out when pasting your text here?
and indeed please check if you have an entry in your samba log file.. for debian it's located at: /var/log/samba/log.smbd
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.