similar to: Can No Longer Join to Domain

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

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

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

I've scoured the mailing list archives and the internet...has anyone actually figured out how to enforce strong passwords when using Samba and LDAP as a PDC? My users are allowed to change their Windows XP passwords, how do I enforce the use of strong passwords (either locally or globally)? -- *Jason Baker */IT Coordinator/ *Glastender Inc.* 5400 North Michigan Road Saginaw, Michigan

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> <span class="postbody">Greetings,<br> I am running Asterisk 1.4.25 with Dahdi Complete 2.2.0, on a Digium TE121B PCI express card with a </span>VPMADT032<span

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

I'm not sure if this is the right place to post this, but here goes. I just put together a PDC using Samba. I have given users the ability to change their passwords (once every 7 days) if they wish. I used to keep a list of usernames and passwords in a spread-sheet, so I could keep track of the servers that I needed to update with the correct password if anything changed. That being said.

Hello all, I've installed samba on pretty basic install on centos 4.4. I'm running a P4 2.8Ghz, 1G Ram, Raid 5 SATA-2 disks running on both a 3ware and Highpoint Rocket raid (this is going to get swapped out for a 3ware card soon). When users copy files from a mac os x client I'm seeing the cpu load avg (in top) get up to 7. These copies included 150+Gigs of lots of smaller

I have a strange issue with roaming profiles. It only happens for users which has no roaming profile on a Samba server yet. When a user logs out for the first time, some files can't be copied from: C:\Documents and Settings\username\SendTo\ to a profiles directory on the server. (Files like 31/2Floppy(A).lnk, some *.tmp files etc.). Only very rarely, a first-time logout process happens

I'm running Samba 3.0.10 as a PDC for Win XP Pro (SP2) workstations. User Outlook .pst files on desktop machines are (obviously) very important, and must be synced with server at logout for proper backup (which occurs on server). I've noticed that said Outlook .pst files are stored on the XP Pro desktops in a folder called: "C:\Documents and Settings\<user_name>\Local

Recent list messages got me thinking... Is there a way to support both local and roaming profile with one server / domain? As I understand it, the "magic" line that tells Samba not to do roaming profiles is the smb.conf line: logon path = Which the line must exist, and must be set to null. But that is in the global section. So is there a way to support both local and roaming...

Ok, I got the W2K3 resource kit tool to move my local profile to my domain profile (moveuser.exe). Didn't really work that cleanly. Even though I used the /k (keep the local account), it didn't really. It seemed to change the permissions on MOST of the files. It didn't really move the files either. It's just pointed my profile (or parts of it) to the existing folder. Can't