From owner-freebsd-stable@FreeBSD.ORG Wed Jun 29 09:56:53 2005 Return-Path: X-Original-To: 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 0248016A41C for ; Wed, 29 Jun 2005 09:56:53 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD1DD43D55 for ; Wed, 29 Jun 2005 09:56:52 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 147E651577; Wed, 29 Jun 2005 05:56:51 -0400 (EDT) Date: Wed, 29 Jun 2005 05:56:51 -0400 From: Kris Kennaway To: Maxim Kizik Message-ID: <20050629095651.GA27557@xor.obsecurity.org> References: <20050628181815.M20445@arb-pro.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline In-Reply-To: <20050628181815.M20445@arb-pro.ru> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: smbfs 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: Wed, 29 Jun 2005 09:56:53 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 28, 2005 at 10:35:09PM +0400, Maxim Kizik wrote: > Good Afternoon. >=20 >=20 > After upgrading my system from FreeBSD 4.10 to FreeBSD 5.3, I found > "mount_smbfs -N" broken. The error message is "mount_smbfs: unable to=20 > open connection: syserr =3D Authentication error".=20 > However, the keyboard interactive password works normally. >=20 > The problem still persists in 5.4p2.=20 > I need this feature strongly because of running automatic backup procedur= es. > Is there any solution? The most obvious guess is that it's a configuration error of some kind on your machine. Kris --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCwnBjWry0BWjoQKURArejAKD4DdBSVLCSOZnI5FzlOyhvVzXRCwCg5sEH Cz8go2ArQcHDIiJDiDt9hS8= =ta5z -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO--