From owner-freebsd-stable@FreeBSD.ORG Fri Dec 8 22:00:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 33B6A16A4D0 for ; Fri, 8 Dec 2006 22:00:27 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5023E43D88 for ; Fri, 8 Dec 2006 21:58:27 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from vanquish.pgh.priv.collaborativefusion.com (vanquish.pgh.priv.collaborativefusion.com [192.168.2.61]) (SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Fri, 08 Dec 2006 16:59:26 -0500 id 0005641B.4579E03E.0000357E Date: Fri, 8 Dec 2006 16:59:24 -0500 From: Bill Moran To: "Gerald Host" Message-Id: <20061208165924.83487443.wmoran@collaborativefusion.com> In-Reply-To: <527a7620612081356w2a54df6eq18492f3ec945b537@mail.gmail.com> References: <527a7620612081356w2a54df6eq18492f3ec945b537@mail.gmail.com> Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.9 (GTK+ 2.10.6; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: mount_smbfs: unable to open connection: syserr = Operation timed out 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: Fri, 08 Dec 2006 22:00:27 -0000 In response to "Gerald Host" : > I used some non-default kernel options to have more RAM (PAE). > > On one BSD machine this command works and mounts as expected. On another > one it fails: > > bsd# mount_smbfs -I 192.168.1.10 //administrator@mpa-fnp/restorereports > /mnt/reports > mount_smbfs: unable to open connection: syserr = Operation timed out > > > The difference between the machines is the kernel options and one failing is > behind a router, but I don't think any ports are blocked. Both are 6.1servers: I would take some extra time to turn "think" into "know" before wasting any time pissing around with kernels. The above error sounds like a routing and/or port-blocked issue. -- Bill Moran Collaborative Fusion Inc.