From owner-freebsd-ports@FreeBSD.ORG Sun Aug 31 07:14:54 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6608B16A4BF for ; Sun, 31 Aug 2003 07:14:54 -0700 (PDT) Received: from relay.butya.kz (butya-gw.butya.kz [212.19.129.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8DE043FF7 for ; Sun, 31 Aug 2003 07:14:52 -0700 (PDT) (envelope-from bp@butya.kz) Received: by relay.butya.kz (Postfix, from userid 1000) id 3D89558F3; Sun, 31 Aug 2003 21:14:51 +0700 (ALMST) Date: Sun, 31 Aug 2003 21:14:51 +0700 From: Boris Popov To: "Richard J. Valenta" Message-ID: <20030831141450.GU99009@vertex.kz> References: <5EEBE9C3C61D1142994C6B620C51E84707A0D0@ip-64-32-234-4.dsl.iad.megapath.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5EEBE9C3C61D1142994C6B620C51E84707A0D0@ip-64-32-234-4.dsl.iad.megapath.net> User-Agent: Mutt/1.4.1i cc: ports@freebsd.org Subject: Re: FreeBSD Port: smbfs-1.4.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2003 14:14:54 -0000 On Thu, Aug 14, 2003 at 11:04:54AM -0500, Richard J. Valenta wrote: > > I have been able to mount windows shares flawlessly with mount_smbfs on i386 > machines, but the same commands to the same win2k servers seem to have problems > under alpha (5.0release and 5.0current) - do you know what might cause this, > and/or ideas on how i can repair it? > > This is the error: > > skunkworx# mount_smbfs -I 24.32.34.14 //backup@web1/www /archive/backup > Password: > mount_smbfs: unable to open connection: syserr = Connection reset by peer > skunkworx# Looks like incorrect port number supplied to connect() call. I'm not sure why you mention smbfs-1.4.1 because smbfs now maintained in the main tree. Please verify your install (eg remove stalled port files) and if the problem persists try to take a tcpdump on the session of interest. -- Boris Popov http://rbp.euro.ru