similar to: Samba configuration error

Hello, I am kind of confused with this situation. I am attempting to build a PDC using TLS/SSL with the following version of software. Samba 3.0.23 OpenLDAP 2.3.19 Fedora Core 5 When I startup the Samba server via the "service" command (service smb start) I get the following errors in my logs. Using SSL: Jul 13 09:52:34 prism smbd[23161]: smbldap_search_suffix: Problem during

Hi Scenario: Lan with opensuse 11.4 Samba and LDAP server. Linux, win-xp and win7 clients. The Linux clients can login fine under TLS: Nov 10 11:31:22 hh1 slapd[1727]: conn=1243 op=0 STARTTLS Nov 10 11:31:22 hh1 slapd[1727]: conn=1243 op=0 RESULT oid= err=0 text= Nov 10 11:31:22 hh1 slapd[1727]: conn=1243 fd=23 TLS established tls_ssf=256 ssf=256 Nov 10 11:31:22 hh1 slapd[1727]: conn=1243 op=1

I have read louis`s howto from december, tried to use kunbuntu, this failed at the ldap server test stage, tried various things, could not make it work, so downloaded debian. Followed louis`s howto and compiled a 2.6.8 kernel (louis, the compile instructions do not work as given). Followed the howto, downloaded samba etc, setup slapd etc as per instructions and it failed again at the same place.

We have a central LDAP server for our enterprise on a Linux box. I have installed Samba 3.4.4 server on an AIX server and trying to get users authenticated via LDAP server. So far my efforts have been unsuccessful. Here is my ldap section of the smb.conf file: passdb backend = ldapsam:ldaps://<company_ldap_server>/ ldap ssl = start tls ldap suffix = dc=xxx,dc=yyy,dc=zzz ldap delete dn =

Hi I have Samba 3.4.0 and slapd 2.4.15 . In my samba log appears this lines again and again: [2009/09/09 01:53:31, 0] lib/smbldap.c:smb_ldap_start_tls(600) Failed to issue the StartTLS instruction: Protocol error [2009/09/09 01:53:31, 1] lib/smbldap.c:another_ldap_try(1175) Connection to LDAP server failed for the 1 try! this means he cant connect to the LDAP Server because he want uses

Hi, I'm a new user. I'm trying to get Samba setup as an member server in an Active Directory Domain and operating as a File Server with SSO. I've been getting lots of these errors in the messages file. I also get a similar message in bash with ldapsearch -ZZ Feb 20 00:19:32 linux-hh3x net: [2010/02/20 00:19:32, 0] lib/smbldap.c:smb_ldap_start_tls(596) Feb 20 00:19:32 linux-hh3x

On 01/06/2016 01:34 PM, Lee Brown wrote: > On Wed, Jan 6, 2016 at 10:36 AM, Graham Allan <allan at physics.umn.edu > <mailto:allan at physics.umn.edu>> wrote: > > On 01/06/2016 09:53 AM, Graham Allan wrote: > > > The packet dump is a good idea. I get the same failure using > straight > SSL to port 636, but wireshark might be able

On Wed, Jan 6, 2016 at 12:56 PM, Graham Allan <allan at physics.umn.edu> wrote: > On 01/06/2016 01:34 PM, Lee Brown wrote: > >> On Wed, Jan 6, 2016 at 10:36 AM, Graham Allan <allan at physics.umn.edu >> <mailto:allan at physics.umn.edu>> wrote: >> >> On 01/06/2016 09:53 AM, Graham Allan wrote: >> >> >> The packet dump

Hi! We are using 2 Samba 3.4.1 on CentOS 5.3. The PDC is working without bigger problems, but I can't get the BDC to work. We have a replica of the ldap on the BDC and I tried the connect with an linux smbclient and with the standard mount -t cifs both not sucessfull: smbclient: Receiving SMB: Server stopped responding session setup failed: Call timed out: server did not respond after

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When WinXP users login to the samba domain a text file opens that contains: [.ShellClassInfo] LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787 This seems to be tied to the roaming profile, it only surfaced once I enabled roaming profiles but I am not sure how to correct it. I also noticed that the desktop background setting is

On Wed, Jan 6, 2016 at 10:36 AM, Graham Allan <allan at physics.umn.edu> wrote: > On 01/06/2016 09:53 AM, Graham Allan wrote: > >> >> The packet dump is a good idea. I get the same failure using straight >> SSL to port 636, but wireshark might be able to decode any StartTLS >> negotiation attempt on the default port. Failing that I guess I'll >>

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 aren't known to Samba? I find that confusing. - Itamar

Hey Samba list, First a brief comment regarding my background and situation. This is my first time posting to this list. I've been asked to resolve a Samba authentication issue, but I have next to no experience using Samba. Unfortunately no one else here knows how to use it either; we're operating with an inherited environment from a sysadmin who left minimal documentation, and we have

Hi there, I'm having some issues with a samba PDC. Using debian etch, kernel version 2.6.18-6-686. I have samba-3.0.24, smbldap-tools-0.9.2, openldap-2.3.30, bind-9.3.4 and isc dhcp-server-3.0.4 with ddns on the same server, I can join and remove Windows XP machines from the domain but I have this Windows NT Workstation that can't join the domain at all. The error it gives is something

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Seems the only way I can get Vista to mount a share when a user logs in is using a netlogon script. My XP clients auto mount the home share on login just fine, but vista won't. Has anyone experience this with vista and if so what did you do to get passed this? I could use a netlogon script to rectify the issue, but since I have XP and vista

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have found bits and pieces of howto's for configuring Windows XP clients to do Kerberos authentication but I have been unable to find anything regarding how to enable Samba to use Kerberos. Has anyone enabled Samba to use Kerberos and if so how the smb.conf file needs to be configured to support this? Thanks. -----BEGIN PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have my samba deployment using an ldap backend. I made changes to the password policy that is stored in the sambadomain object but windows clients are not adhering to the policy. Do I need something in the smb.conf file that "enables" this or something else I am missing? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)