similar to: Backup Domain not working

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 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

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 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 have had a samba PDC up and running for about a month now with no issues, this weekend I added a BDC and it seems that all my clients are now logging into the BDC automatically instead of the PDC. I had to mount the homes from the PDC to the BDC so that users can have access to their home directories and set the path to the profiles directory on the BDC to that of the PDC. I also had to

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

Hi, I recently migrated to a Samba3x domain. One issue that has been reported to me is that XP users cannot change their password from their PC. I have done some searching and I haven't seen a straight forward answer to this. My config is ldap primary + Samba PDC on host A ldap slave + samba BDC on host B I see this error in the machine log when someone attempts to change their password:

My Configuration, On my PDC: Samba version 3.2.15 /LDAP-Master (slurpd)/SMBD4wins <-- version 3.3.12 not working. Downgrade again On my BDC: Samba version 3.3.12 /LDAP-Slave <-- version 3.3.12 working [global] on PDC [global] workgroup = tuepdc.local bind interfaces only = true interfaces = 192.168.135.143/24 127.0.0.0/8 socket address = 192.168.135.255 profile acls = no hosts allow

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

Dear all, I have created two virtual machines on my computer (With Vmware 5.5.3). One is running SuSE Linux Enterprise Server 10 with Samba 3.0.22. The other one is runnung a WinXP SP2 client (name: test01). I can browse the shares of the Samba Server. Furthermore I can connect to them with different user names. When trying to join the client to the domain I get an error message that the

When I stop the BDC all clients log on to the PDC. And to my confusion when I restarted the BDC today and made a testparm on both PDC and BDC both showd role domain pdc --> Server role: ROLE_DOMAIN_PDC Here my smb.confs: PDC: [global] security=user smb ports = 139 logon script = logon.bat logon path = \\%L\%U\profile\%U logon drive = S: domain

What about your openvpn config? The tun net must have an entry in your hosts allow. If you work with briding the remote network has to be the same subnet as the local!? Bridging is the best way to have a remote net integrated. I have one logging in form Berlin on my Samba-Domain. Daniel ----------------------------------------------- EDV Daniel M?ller Leitung EDV Tropenklinik

Hi All, I'm having a problem with cross subnet browsing and name resolution across an openvpn tunnel. i've found quite a few people who've had the same on mail lists but none of their fixes have worked. The spec of the setups at both ends of the tunnel are as follows: OS - CentOS 5.5 Samba Version 3.5.4 OpenVPN Version 2.0.9-1 Each server is configured in gateway mode with two NICS,

Hi Im looking to config a BDC with ldap. It seems the connection with ldap primary server works, but Im confused with the shared folders. I understood when you creates a BDC needs to put the same global information: [global] workgroup = DOMAIN netbios name = DOMAIN-PDC security = user enable privileges = yes interfaces = 127.0.0.0/8 eth0 10.0.1.0/24 10.0.0.0/24 server string =

I have noticed while testing my Samba 3.0.2a primary and backup domain controllers with Windows XP clients, that when I attempt to login to the Samba PDC, the XP client will sometimes randomly choose the backup domain controller. I only want the client to join the backup domain controller when the PDC is offline. I am not experiencing any random network outages or DNS failures so I am bewildered

Hi, Trying to be simple and direct. My last email didn't get answers. Thank you and best regards. Problem: ----------- W2K workstations remains connected do samba server at port 139, even after logoff, and this causes: false wtmp information and no possibility do control (even no fail proof) simultaneous logins. Workaround ( not acceptable )

-----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, I installed a SaMBa PDC and a BDC. When I log in to an XP client with a new user, sometimes I get the initial profile settings from the netlogon share, but often from local. When I get the local default settings, it is not syncronized to the server at logout. Even if I get the new profile from the server, on the same client, next time, with a new user, I get the new profile from local. I

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

Hi all I have a samba 3.0.21c with OpenLDAP 2.3.19 as Primary Domain Controller. I would like to enable Roaming Profiles per user basis , not for all users. below is my smb.conf , [global] workgroup = mydomain.com <http://msdpl.com/> netbios name = mydomain passdb backend = ldapsam:ldap://mydomain.com server string = Domain Controller hosts allow = 192.168.128. 192.168.129.