similar to: Samba + LDAP Login problem

Greetings, I've been pulling my hair out on this problem for several days and I'm not really any closer to a solution. I hope someone out there can help me. I'm trying to set up a samba PDC on a Fedora Core 2 box using an LDAP backend (on another server). The base install of everything is working fine. At the unix level LDAP connectivity is configured and working properly for

I'm having problems using smbldap-tools 0.8.2 from idealix, I'm using the following entry in my smb.conf file: add machine script = smbldap-useradd.pl -w -g 553 %u Then, while I try to add a workstation to my domain, the script adds a posixAccount, and then I get this error: ------ [2004/01/14 18:15:49, 1] passdb/pdb_ldap.c:ldapsam_modify_entry(1173) ldapsam_modify_entry: Failed to

Hello, We have an otherwise working Samba PDC+LDAP setup but for one minor detail. The shadowLastChange is not updated when the user sets his password from a Windows workstation (all the necessary Samba*-fields as well as userPassword is updated in LDAP). We've enabled 'ldap passwd sync = Yes' in smb.conf. slapd.conf contains the appropriate access rule for the said field. The

Hi I have a small problem with joining a XP box to a Samba domain, which I hope that someone can put some light on. The setup: Samba 3.0.4 using ldap for users. All users are created with both posix and samba accounts. Users can login with ssh (pam/nss), smbclient and net use \\pdc\share /USER:username (also from XP pro). W2k workstations can join the domain. When I try to join a XP (pro)

Guys, We have a Samba 4 PDC with TDB backend. We're now trying to a BDC so we need to migrate from TDB to LDAP . I've read the Samba documentation which says using tdb in both servers will cause issues. So the question is how do we migrate from TDB to LDAP in the PDC. The setup we are going for is each DC will have LDAP setup. The LDAP servers will then be replicated. Reading the official

Hi I am unfortunate not able to browse any users in my samba-ldap domain. ex. if I want to add the user swi more premissions on a samba share folder (security-->add-> advanced-->find now--> the smbldap domain users and groups are not shown anymore? This same goes if i want to add a user as local administrator on a joined XP PC - same problem. I am using and a RHES 4 update 3

Hello, I have a problem with a LDAP backed based Samba PDC. Last week, due an hardware problem, I lost my primary LDAP server and PDC. I reinstalled the LDAP server and populated it with the old data, I also reinstalled Samba. The problem is that I can't log in to samba as root (cn=root,dc=info,dc=uvt,dc=ro). All others user accounts ar working except root. Eg.:

I'm setting up a PDC with LDAP (Posix and Samba accounts) backend. Samba version is 3.0.10 (FC3 x86_64 version). I'm following the instructions on the IDEALX site. I've done this before with older versions. It appears some things have changed in LDAP, Samba, and the smbldap-tools, but for the most part the procedure is the same. The problem I'm getting is with the 'net

I have our Samba server mostly working, however it will not allow me to change the password on the client desktop or via USRMGR. The error message we are getting is "the system cannot change your password now because the domain TOPC is not available". USRMGR reports "Could no find domain controller for this domain" Everything is authenticating properly. Any ideas? I'm

Hi, I've just upgraded an old samba 3.0.23 on an old Fedora Core 5 to samba 3.5.4 using an rpm built from the source. Everything works fine, but when i start the server i get some error messages(see below). Before i start the server there is no connection (tested with lsof and fuser) on the 139 and 445 ports, smbd or nmbd aren't running. With the old version i never had this

I am trying to lock down Samba's null session accessibility by using the "restrict anonymous = 2" setting but when I configure this option it stops the test XP client from being able to logon in to the domain. "restrict anonymous = 1" allows logins to work correctly but Samba still shows some account information when checking with the GetAcct tool. I am using a Samba

Hoping this is an error of stupidity or ignorance on my part. Running Centos 4.6, after the big update from 4.5. Samba would not communicate with our samba PDC (3.0.10), kept getting NT_STATUS_BAD_NETWORK_NAME errors. I will most likely update all our samba servers, but do not want to do it knowing that the two versions may not talk. Here's my smb.conf, currently functional - does not

Hi I want the following share setup in samba 3.0.10 without the use of POSIX ACL kernel support on the /dev/sdi01 partition: A group should be able to be "Windows owner" when ever a windows file or folder is created. A group should be able to be have windows full access when ever a file or folder is created. Only group should have login access to the hidden share

Hi all! I work as a computer technician for a small school and have recently upgraded our network to use samba servers. Our main computers are a PDC, a BDC, a file server and a backup server, all using Red Hat Fedora Core 3 as a base. The clients on our network consist of machines with Windows XP and a few with Windows NT. Everything seems to work just fine except for some minor but annoying

Am in testing phase with just a few lucky users to go live with samba. However, I just had a thought. What happens when we eventually do vista? Seems like I may need to add %a to my path = statement, but it did not work. No profile was created for the user under the "windows version" directory.. Here's my testing smb.conf. Please have a look and see what I may need to do to

Hi All I have installed Samba 3 under RHEL v4, with LDAP support for the authentication and as a PDC Domain, it seems everything works fine, but the only problem was the network browser list. We have a different subnet 192.168.X., 192.168.Y., 192.168.Z., etc..., Samba local browser works fine, but the remote subnet and workgroup are inaccessible, I double check the nmbd logs, there an error which

Hi folks, I have been asked to force NTLMv2 logins to avoid use of LM hashes. To meet the requirement I added some lines to the smb.conf in [Global] (we only have that section anyway - this is purely for domain authentication with an ldap backend): client lanman auth = no client NTLMv2 auth = yes lanman auth = no min protocol = LANMAN2 ntlm auth = no This seemed to work - users

i currently have a samba pdc, samba bdc and samba member server all running samba-3.0.23c-1.fc5. up until the 3.0.22 releases, i never had any problems with users authenticating to member servers. problem now is, a user from windows xp professional (which is part of the domain) can auth to the pdc and bdc, but not to the domain member server. the same thing happens from windows xp home (even

Hi All, I've happily had Samba (3.0.24) operating as DC for my Win2k/XP network for years. I've just upgraded to Vista and eveything seems to be working fine (shares, domain logons) apart from roaming profiles. Just after logging on, the following error appears in a bubble from the system tray: "Your user profile was not loaded correctly! You have been logged on with a temporary

Dear Samba Team, There are three issues happening in my Samba 3.6.6 Issue 1: After upgrade, when upload file which is more 100mb to Samba, it shows error "File name too long cannot copy" in windows xp. Tried to use 3 different pc to upload different files more than 100mb, it also fail to transfer the file and show the error. Tested to upload file which is 25mb or 50mb, it is okay, no