similar to: Winbind can't connect to ldap server after 3.0.6

I am running Redhat Linux 9, openldap 2.2.15, Bdb - 4.2.52, openssl - 0.9.7d, smbldap-tools-0.8.5 and samba - 3.0.6. When I try to migrate my users from NT 4 domain to Samba, using the net vampire command, I get the following error: [2004/08/25 14:58:59, 0]Lib/smbldap.c:smbldap_open_connection(623) Failed to issue the StartTLS instruction: Connect error Broken pipe Am I missing

Hello all Just in case anyone has similar problems: We have a kixtart script which maps folders for users, I am not sure where it happened, but I made a mistake with users home directories. A couple of users were not copied from our old 2000 server during the move to samba and so were created manually. This worked fine with /homes/user, but since the upgrade to 3.0.6 some users have failed to

Hello world, I have a very strange update problem: this night I upgraded from 3.0.5 to 3.0.6 (debian unstable) and the system broke completely with very strange errors (I did not change anything to smb.conf) - win98 users can log in, copy and everything - xp users can log in, they see the shares but they cannot access the files (read error in xp). I have tested it with Xp-Prof SP1 und SP2

I do if you're interested... -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent: Monday, August 23, 2004 11:45 AM To: mlueck@lueckdatasystems.com Cc: samba@lists.samba.org Subject: Re: [Samba] Update -> Someone with "Access Denied" from Windows plstry this test to compare notes with me -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael

We've had the following problem with samba-3.0.4 - samba.3.0.5: Very strange behavior on mapped shares when the user is a member of "Domain Admins", Unix group "domadm". samba-3.0.0 - samba-3.0.5: Setting "hide unreadable" on a share hides everything when "security=DOMAIN". These problems disappeared from our test environment after upgrading to

Hi all, yesterday i switched from Samba 3.0.5 to 3.0.6 RC2 because we want to upgrade our Windows XP clients to SP2 which seems to cause printing problems with all older versions of Samba. Unfortunately this reintroduced a problem regarding DOS ( please see http://lists.samba.org/archive/samba/2004-July/089609.html ) which i already had experienced when i switched from Samba 3.0.4 to

Redhat 6.2 kernel 2.2.14-12 Samba 3.0.6 compiled with ./configure --prefix=/usr/local/samba --localstatedir=/var/log/samba --with-lockdir=/var/lock/samba --with-privatedir=/etc/rc-abas.d --with-configdir=/etc/rc-abas.d --enable-debug I can list directories and write files on a samba share but cannot read files. This happens with Windows XP client or smbclient. After downgrading to 3.0.5 samba

Running into a lot of people upgrading to the 3.0.6 package that all of a sudden begin to experience the "Failed to verify incoming ticket!" errors etc., that are generally associated with a kerberos package incompatibility. However many of these people are running later versions of kerberos *and* reverting to a previous version of Samba appears to fix the issue. Is there something new

Hi, I'm having problems creating hard links on a samba share from a samba client. My environment is as follows: - PDC on a Windows NT - samba-3.0.5 client - samba-3.0.5 server (homes) I use winbindd to authenticate and it is working fine, I can create, remove and change files without any problems. The mount command line I'm using is: mount -t smbfs //10.101.0.231/homes /mnt -o

Hi, I have installed samba 3.0.6 based on the "Official HOWTO" to join out Active Directory environment, with winbind and pam support. I have join the samba to the domain using "net ads join -Umyloginame". I can do the "wbinfo -g", "getent passwd" and "getent group" correctly. I also can list shares on other machine, using kerberos: # kinit

I installed samba 3.0.6 today. I had to upgrade samba.schema in openldap as well to include sambaPasswordHistory and sambaLoginTime, otherwise certain things would not work (e.g. smbpasswd or users changing passwords) openldap failed to start because both attributes have the same OID, ...2.1.50. In order to get started anyway, I changed the sambaPasswordHistory OID to ...2.1.52 (which, in my

hello, i tried to upgrade from 3.0.2a to 3.0.6 tonight. my smb.conf is below. (i upgraded by apt-get install "samba samba-common winbind" ) it didnt work : i was asked for a username and password for everything even when i tried to acces the shares' root with its unc name ( \\server ). do u have any information on that ? somethng changed in the authentification ? my server is a

Hello all, Just a quick note to other Solaris users that upgrading to samba-3.0.5 seems to cause cron to core dump into /var/spool/cron/atjobs. After investigating this for a few days, it appears to be due to the winbind entry in /etc/nsswith.conf. Of course, once I restart the cron daemon, and it picks up the new libnss_winbind and pam_winbind.so files, everything is fine. However, this has left

Running on a Debian server, 3.0r Sid, 2.4.18 kernel. I recently did an apt-get upgrade which upgraded samba from 3.0.5 to 3.0.6 After this upgrade, access to all shares for all users slowed to a crawl. It was possible to browse the folders, to 3-4 folders deep but then Explorer would freeze on the client.Opening files failed. Copying files locally resulted in corrupt files. Clients included

Hi All. Trying to use the file /samba-3.0.6/examples/LDAP/samba.schema I found that it has duplicate entries for atributetype > grep 1.3.6.1.4.1.7165.2.1.50 /usr/local/etc/openldap/schema/* /usr/local/etc/openldap/schema/samba.schema.new:attributetype ( 1.3.6.1.4.1.7165 .2.1.50 NAME 'sambaLogonHours' /usr/local/etc/openldap/schema/samba.schema.new:attributetype ( 1.3.6.1.4.1.7165

Hello samba users, Samba 3.0.6 comes with new samba.schema with new attributies but attributetype sambaPasswordHistory have the same OID with attributetype sambaLogonHours and slapd failed to start attributetype ( 1.3.6.1.4.1.7165.2.1.50 NAME 'sambaLogonHours' DESC 'Logon Hours' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{42}

Hi, I'm running a samba server version 3.0.6-2.FC2 on a Dell PowerEdge 2600 SC RAID5, linux Fedora Core 2 (Up to date). Windows user often experience critical speed problem when writing files on a samba share (ex: 19mn for a 36 mb file instead of nearly 10s), or printing. A "top", or "ps -ax", or even samba log files do not indicate anything. I have to make a 'kill

Hi! I have a curious problem. I updated my Fedora Core 1 box yesterday from samba-3.0.2 to samba-3.0.6. All the packages that were suggested by yum. I have the box join an NT4 Domain, and while yesterday before the update a smbstatus would list the users as CENTRUM+Username (CENTRUM is my NT Domain) today it refuses to do so, and any shares apart from the public ones are not available any

system is redhat 9 on a dell power edge 2450 running latest krb5 and openldap rpm It worked perfectly on 3.0.4 but arcserve wouldn't back up so I upgraded to 306 and everything installed correctly but now when you try and connect to the server it pops the user login box up. I can run net ads user -U Administrator and log in with my admin password and it lists all my user accounts. I can add

I have been running samba 2.2.8a with approx 400 users accessing it for their network drives. What I need to do now is to upgrade it to version 3.0.6. I have been trying to upgrade my development system with limited success this is what I have done. ? stopped samba ? /usr/src/samba-3.0.6/source ? used the same configure options as when I installed 2.2.8a i.e ? ./configure --prefix=/usr