From owner-freebsd-questions@FreeBSD.ORG Wed Oct 8 14:59:57 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1252816A4B3 for ; Wed, 8 Oct 2003 14:59:57 -0700 (PDT) Received: from mx1.lphp.org (APastourelles-107-1-20-240.w81-49.abo.wanadoo.fr [81.49.209.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E64243FDF for ; Wed, 8 Oct 2003 14:59:55 -0700 (PDT) (envelope-from ajacoutot@lphp.org) Received: from sta01 (sta01.lphp.org.local [192.168.0.4]) by mx1.lphp.org (8.12.8p2/8.12.8) with ESMTP id h98M0Ck1006866 for ; Thu, 9 Oct 2003 00:00:12 +0200 (CEST) (envelope-from ajacoutot@lphp.org) From: Antoine Jacoutot To: freebsd-questions@freebsd.org Date: Wed, 8 Oct 2003 23:59:33 +0200 User-Agent: KMail/1.5.4 References: <5E833948-F8F3-11D7-8478-000A95A05832@skilltreeconsulting.com> <10226B26-F9BB-11D7-8B74-000A95A05832@skilltreeconsulting.com> <3F847E59.8060404@despammed.com> In-Reply-To: <3F847E59.8060404@despammed.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200310082359.35778.ajacoutot@lphp.org> X-Scanned-By: MIMEDefang 2.37 Subject: Re: Samba Change Password from Windows using ctrl-alt-delete X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Oct 2003 21:59:57 -0000 On Wednesday 08 October 2003 23:15, Uwe Laverenz wrote: > passwd chat =3D *New*password* %n\n *Retype*new**password* %n\n > *password*has*been*changed* > And please, don't let me see statements like "don't run Samba 2.x on > FreeBSD" again, because I've been doing this for many years. Thank you... Just to add my 2 cents... this does NOT work, this is why the original post= er=20 asked for help. Password sync is broken under FreeBSD with samba-2.x, and=20 this is not a configuration issue. I ran into the same issue a month ago and add to use samba-3. Antoine