From owner-freebsd-stable@FreeBSD.ORG Sat Feb 18 08:56:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B5BD16A420 for ; Sat, 18 Feb 2006 08:56:03 +0000 (GMT) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFC3E43D45 for ; Sat, 18 Feb 2006 08:56:02 +0000 (GMT) (envelope-from peo@intersonic.se) Received: from localhost (terrapin.inter-sonic.com [172.16.1.12]) by neonpark.inter-sonic.com (Postfix) with ESMTP id ED765818E22 for ; Sat, 18 Feb 2006 09:56:01 +0100 (CET) Message-ID: <43F6E11E.4050806@intersonic.se> Date: Sat, 18 Feb 2006 09:55:58 +0100 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Thunderbird 1.5 (X11/20060120) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <43F4DD9C.6000704@intersonic.se> In-Reply-To: <43F4DD9C.6000704@intersonic.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at inter-sonic.com Subject: Re: smb_ntencrypt: password encryption is not available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Feb 2006 08:56:03 -0000 Per olof Ljungmark wrote: > Rebuilt from 6-STABLE sources just now and mount_smbfs fails with the > following message: > > mount_smbfs: unable to open connection: syserr = Authentication error > smb_encrypt: password encryption is not available > smb_ntencrypt: password encryption is not available > > I'm just now making a new kernel with > options NETSMBCRYPTO > options NETSMB > to see if it helps. This machine worked like charm before, is there a > change somewhere? > I'll answer myself then... I still don't know why I needed to make a kernel with options NETSMBCRYPTO but it did solve the problem. There must be a change somewhere, either I did it here or in the system. Other pre-02/17/06 systems here are ok without this kernel option. Sigh.