similar to: BDC problems

I have a working Samba PDC, I can log in and out from a windows xp workstation. I recently upgraded to 3.0.25b-33 and now, when I add a new user, I get: The system cannot log you on due to the following error: A device attached to the system is not fuctioning Please try again or consult your system administrator I have network connectivity. I was able to join this machine to the

My root account keeps getting locked out automatically. I am running Samba 3.0.25b on a CentOS server, as PDC with LDAP backend. I have accounts set to lock after 8 un-successful login attempts. I zeroed out the bad password count, and then in less than a few seconds the account gets locked again and a /pdbedit -Lv -u root /yields the following: Unix username: root Logon time:

I have Samba 3.0.24 running on CentOS 4 as a PDC with an LDAP backend. When I first set everything up, I could join workstations to the domain automatically with the Windows Network ID Wizard. Now when I try to join a workstation I get: Your computer could not be joined to the domain because the following error has occurred: The user name could not be found. If I add the computer

I have a Samba PDC, running on Centos 4. The samba version is 3.0.23d.30. I have an LDAP backend. Everything seems to be running fine. I recently configured a BDC, to help with load balancing and to act as a backup in the event the PDC went down. Before I installed the PDC, when a new user logged into the domain, their home directory on the PDC was automatically mapped to the drive letter U.

I recently set up a backup domain controller using Samba 3.0.23. I have a Samba PDC already running, and all is working fine, but once I added the BDC, now when people log in to their windows account, their home directory is now being mapped to their home on the BDC (which is empty) instead of the PDC. Conf files from each below: PDC Samba Conf: [global] unix charset = LOCALE

I have a samba PDC with LDAP backend running on CentOs 4. Everything is working fine, but my log watch report showed two users with the same SID. I checked it out and it appears that ROOT and the samba machine ASTER$ both have the same SID. If I do a pdbedit -Lv I get this: --------------- Unix username: aster$ NT username: aster$ Account Flags: [W ] User SID:

I have a Samba PDC with LDAP running on a CentOs 4.4 machine. When I first had it all configured, everything worked fine, but now for some reason, login scripts will not run on the client (even though they have access to the shares the login script is trying to map) and I cannot join client machines to the domain automatically using the Windows XP Network Identification Wizard. When I try to

I have a Samba PDC and a file server (domain member). They are both running CentOS 4, with Samba3-3.0.24-30 and LDAP 2.3 (on PDC). Domain authentication seems to be running fine and file access on the file server works also. I have one share on the file server that gives me trouble. Whenever I access files from this one directory, the network seems to lock up for close to a minute. I get 64%

I created a BDC for my network, running a slave LDAP server. Do I need specify the same workgroup as the PDC in the smb.conf? I was thinking I'd put it on a different workgroup just for organizational purposes. -- *Jason Baker */IT Coordinator/ *Glastender Inc.* 5400 North Michigan Road Saginaw, Michigan 48604 USA 800.748.0423 Phone: 989.752.4275 ext. 228 Fax: 989.752.4444

Greetings, I am running samba-3.0.10-1.4E.9 installed from rpm on CentOS 4.4. I have it configured as a PDC. It is using the /passdb backend = tdbsam/ backend. I am using /pdbedit/ to make some configuration changes to user passwords. I would like to expire a users password, so that they are required to change it the next time they log in. From all that I have read in on-line resources

I have been having some problems since I updated from Samba 3.0.23 to 3.0.25b. I have installed the latest version of smbldap-tools but I am still not able to make certain changes to a user's account. I have created a new user named JROLFE. After I set up a new user, I will set it so they are required to change their password when they first login. I usually do this through LDAP Account

I submitted this question to the Postfix maillist and they suggested that I post to this one. Here's my issue: I have a Postifx email system running on a CentOS 4 box, with Dovecot pop3 and imap. Last week, one of my users reported to me that about a dozen emails suddenly showed up in his in box (as unread messages), but none of them were addressed to him. Under further investigation,

I just got Samba + LDAP up and running as a PDC. If I list the users in the LDAP directory with pdbedit -L I see: root:0:test nobody:99:nobody aster$:1001:Computer toast$:1002:TOAST$ fordprefect:1003:Test Account Shouldn't there be an Administrator account and no root? I don't want my Linux root account even remotely confused or associated with a Samba/LDAP

Hi all, I'm rather new to samba and trying to deploy a PDC/BDC Setup for our company. Got some books and the manpages here to help me :) The config-files are attached at the end of this mail. Used Samba is 3.2.7-11.6 on a SLES11 system. The PDC is running as ROLE_DOMAIN_PDC says testparm, the BDC as ROLE_DOMAIN_BDC. Both DCs use a LDAP (OpenLDAP 2.4.12-7) for user authentication. The LDAP

Hello everybody I am running two Domaincontrollers PDC and BDC both with an LDAP Backend (Master and Slave) and another samba fileserver FS1 who is a Domain Member. We have about 180 win clients (W2k and XP) on the network. We are also running a w2k terminalserver (TS) with about ten clients hooking up to it. We are running a login script assigning shares automatically to the clients. The

I have a PDC+LDAP as well as a BDC+LDAP in another subnet setup with a domain member in the same subnet as the BDC. From my understanding the domain member should be hitting the BDC for all authentication but watching the logs I see the PDC is the one handling it all. The BDC just sits there. Am I missing something? Here are the smb.conf for each servers: PDC: [global] workgroup = X.X.X

Need help debugging the following, thanks. All Samba setup over three subnets: 192.168.4.0-------192.168.1.0--------192.168.3.0 BDC here PDC here BDC here weir ripple hart netmask 255.255.255.0 from log.nmdb at weir after elections have settled: [2004/03/20 02:25:22, 4, pid=1291, effective(0, 0), real(0, 0)]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am trying to get a samba setup with with a pdc/bdc configuration. The backend information stores are openldap ( for passdb and idmap ) I have followed the instructions in the Samba Guide and the documentation provided with the smbldap-tools package. Samba version: 3.0.24 smbldap-tools: Using the version included in samba (

Hi every body, As you may have guessed, I've got a problem ;) What I had : - A PDC Server (Windows NT 4 SP 6a), called SERVER1, for the domain TEST - A BDC Server (Windows NT 4 SP 6a), called SERVER2, for the domain TEST Everything was working fine. Now I switched my NT PDC to a Samba PDC, and I make SERVER1 a BDC for the domain. Until now, no problem. I use samba 3.0.4,

Hi all I have a samba pdc(master LDAP Server) with 1 BDC(slave ldap server), the version of Samba at PDC and BDC is samba 3.0.21c. At BDC , there are some shares declared. The shares are used to store Fox pro files. The client uses foxpro and opens DBF file in the share declared. and also Roaming profiles is also used at BDC. The problem is samba hangs frequently. Once rebooted works for some