similar to: Windows 7 against Samba+LDAP does not work with some passwords

Hello, a heave a share on a samba server 3.6.3 that is used as a DFS-Root. The DFS Links a working on Client with Windows 7 but not on Windows XP clients. Searching on the internet gives me a hint that it can be a problem with "security = ADS". The Samba server is member of a windows 2003 R2 Domain, and the Unix user info (uid, gid) are stored on the domain in der RFC 2302

Hi, I've been fighting against a file server with samba 3.6.9-151.el6 authenticating from a windows 2003 server. I've read a thousand posts and howtos with all kind of samba versions without success. It looks like windbind is not processing things right. I've set the unix permissions on the folder to CANAL4\graficos right and the parent folder is world readable so this should not be

Using LDAP and the smbldap-tools. When attempting to join the domain with an administrative user, the computer gets added to the Computers list in LDAP with the following attributes: cn: workstation75$ description: Computer gecos: Computer gidNumber: 515 homeDirectory: /dev/null loginShell: /bin/false objectClass: top, account, posixAccount uid: workstation75$ uidNumber:

I got a very similar issue like the following link. https://lists.samba.org/archive/samba/2010-November/159606.html Environment: samba-3.5.6 arm linux 2.6.31.8 smb.conf with "reset on vc zero = yes" Here's the procedure to reproduce: 1. Copy a file from PC to samba device 2. Unplug the LAN port during copying (simulate the flaky network) 3. Then the samba client timeout 4. Plug the

Hello good people, I am fighting with following issue: our users are complaining about very slow/delayed displaying of main folders during accessing server using \\dns.name.of.server (using \\IP or \\netbios_name is it with same slowness). But once they are authenticated, displaying contents of (sub-)folders are getting normal. Once the user hit "enter" key on

=20 \\128.252.123.123\sharename <file:///\\128.252.123.123\sharename>=20 =20 And it works as expected - my clients are in the same domain, no password is asked for, etc. =20 Using any form of the hostname in the URI, either \\hostname\sharename <file:///\\hostname\sharename> or \\hostname.domain.name\sharename <file:///\\hostname.domain.name\sharename> in the URI will

Helpp! :) We didn't catch this in testing and now it's killing me in production! I'm getting stuck with my fresh build of Samba 3.6.10. It isn't honoring groups specified in the valid users clause of the share configuration. I'm running in security = SHARE mode, and user authentication is working just fine. Even if I specify individual users on the valid users = line, it

Hi at All Samba stop my transfert when i want to copie one files or is very low. I don't for why in my log, i have when my copie crash : [2013/01/10 21:40:56.442652, 3] smbd/oplock.c:895(init_oplocks) init_oplocks: initializing messages. [2013/01/10 21:40:56.442712, 3] smbd/oplock_linux.c:224(linux_init_kernel_oplocks) Linux kernel oplocks enabled [2013/01/10 21:40:56.445978, 3]

On 18/04/15 15:06, Itamar Gal wrote: > Hey Jeremy, > > Thanks for the advice. I followed your suggestion collected the logged > information for a single connection attempt (i.e. smbclient > //servername/sharename -U username); I've included the log data below (in > the postscript). It looks like Samba is still looking for a Unix user > account and not finding one. I should

I'm beating my head up against the wall here.. Need some extra eyes!!! Setup -- Samba4 Domain Controller and samba3 print server.. DNS FlatFile,, All dns works.. Issue, When I browse to the print Server vi \\IP-Address I am able to connect just fine.. When I browse using \\netbios-name I connect to the server but it opens up a username/pass dialog box and no name or passwords will work..

OK - I finally am able to join machines to the domain, but I cant log in to them (at least not my test client anyway). If anyone can help I would be really really appreciative! Platform: Solaris 9, Samba 3.0.5, Sun One Directory Server 5.1 error is: The system could not log you on. Make sure your User name and domain are correct, then type your password again. Letters in passwords must be

I am running Samba 3.6.15 on a RHEL6 server. The server has been joined to the campus AD. The complaint I am getting from users is that this is much slower than other, earlier versions of Samba. We have older versions running on both RHEL4 and RHEL5, but this version on RHEL6 seems to be running much slower. One thing to note is that I had first installed and had Samba 4 working. But,

I'm running Centos 4.3 and Samba 3.0.24. I have an OpenLDAP backend. I have successfully got a Windows Domain to work, Windows XP -> Samba -> OpenLDAP. I can add machines to the domain and I can login and change passwords. The trouble is that I'm using NTLM and have been told that I must upgrade to NTLMv2, but I'm having great difficulty doing so. I have existing NTLM users. I

I have an issue with getting my students access to the samba shares for our lab's server. I am using authentication through our university's active directory. I followed the directions for getting this set up using winbind. I am using winbind for both samba authentication as well as user logins through pam. The trouble is this: I have no problems logging in and getting access to the

I'm running 3.4.6 (was running 3.0.28a but upgraded in hopes to fix this issue). Clients running Windows 7 that are NOT joined to the AD domain (samba authenticates against it via "security = server") cannot authenticate to access the server. Clients running Windows 7 that are on the domain as well as Windows XP, Windows 2003 on and off the domain work as expected. Any help would

System Summary: centos 6.2 samba 3.5 smbldap-tools 0.9.6 openldap 2.4.23 Hello, I am installing smb 3.5 on a CentOS 6.2 host using smbldap-tools. I've previously installed a similar configuration on RHEL4 using smb 3.0 but CentOS now uses nss-pam-ldapd and nslcd instead of nss_ldap, so the configurations cannot be moved straight across. Currently, when I attempt to connect to an smb share

after setting up a PDC with ldap according to the book samba 3 by example, almost everything worked out fine, the validations listed in the books turned out as expected with minor differences, but these are the problems : 1. According to the book the account that can be used to join a domain is the Administrator account with the password set from the ldap admin dn which is secret is my

Hey Jeremy, Thanks for the advice. I followed your suggestion collected the logged information for a single connection attempt (i.e. smbclient //servername/sharename -U username); I've included the log data below (in the postscript). It looks like Samba is still looking for a Unix user account and not finding one. I should mention that it seems that I am able to authenticate as the user; the

On 18/04/15 15:39, Itamar Gal wrote: > Hey Rowland, > > Thanks for the advice. The host is running Ubuntu 12.04 and I've > included the smb.conf below (reverted it to its "original" state prior > to following Jeremy's advice). I don't suppose you know why the user > is able obtain a list of Samba services (i.e. smbclient -L host -U > user) if they

Hi There's a lot of this all over the web but there doesn't seem to be much in the way of in-depth investigation. I have a RHEL5.3 server on which I've installed samba 3.5.7 from http://ftp.sernet.de/pub/samba/3.5/rhel/5/i386/ It's set up with identical kdc.conf and smb.conf files to a server I set up on the same network last week which is working flawlessly. I can log on to