From owner-freebsd-questions@FreeBSD.ORG Fri Feb 17 15:15:23 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 2825316A420 for ; Fri, 17 Feb 2006 15:15:23 +0000 (GMT) (envelope-from freebsd-questions@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5813143D58 for ; Fri, 17 Feb 2006 15:15:21 +0000 (GMT) (envelope-from freebsd-questions@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FA7Jj-0003v6-Tg for freebsd-questions@freebsd.org; Fri, 17 Feb 2006 16:14:43 +0100 Received: from 65.213.7.6 ([65.213.7.6]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 17 Feb 2006 16:14:43 +0100 Received: from scott by 65.213.7.6 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 17 Feb 2006 16:14:43 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: "Scott I. Remick" Date: Fri, 17 Feb 2006 10:13:54 -0500 Lines: 44 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 65.213.7.6 User-Agent: 40tude_Dialog/2.0.15.1 X-Archive: encrypt Sender: news Subject: VNC forwarding over sshd issue X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: scott@sremick.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2006 15:15:23 -0000 I'm having a weird problem that surfaces sometimes and I am having trouble pinning down the cause. What I do is use VNC to remote-control my home FreeBSD box remotely. Most of the time, this works fine. My home router forwards the external port to my FreeBSD (6.0R) box. I use PuTTY as a Windows ssh client, and have a saved session that does the VNC port-forwarding (local port 7000 forwards over ssh to remote port 5900). I run Gnome (2.12.2) and vino as my VNC server and connect to my home desktop. Sshd is OpenSSH 2.6.1, PuTTY 0.53b, TightVNC 1.2.9 But every now and then (like right now), the VNC side of things fails. I can still connect via SSH just fine. The PuTTY logs show the port is successfully being forwarded with no error: 2006-02-17 09:38:58 Local port 7000 forwarding to localhost:5900 But when I try to launch a VNC client on the remote PC (in this case, TightVNC) I get a "Connection closed" error. The PuTTY logs show: 2006-02-17 09:52:42 Opening forwarded connection to localhost:5900 2006-02-17 09:52:42 Forwarded port closed On the FreeBSD box, no log files seem to get changed after the attempt. In particular, I check messages and auth.log but doing a listing sorted by time, I see nothing logged. What I DO know is if I went home and restarted the FreeBSD box, it'd work. I've tried -HUP on both sshd and vino-server to no avail. I cannot find any docs for vino-server to determine additional params I could pass it for more-detailed logging. Enabling additional debugging info on sshd with the -d option seems to not be an option remotely since it prevents it from going into daemon mode and it'll only handle one connection, and I can't make the problem surface on-request in order to test it while at home. The problem is particularly annoying because I can't MAKE it happen. It just sometimes does, with no settings changes, and will work again after rebooting the FreeBSD system, again with no settings changes. SSH never stops working... it's always the VNC-port-forwarding side of things. Any suggestions? Somewhere else to look for info? Some way to get more debug info from sshd or vino-server? Thanks