X-Spam-Check-By: sourceware.org
Mime-Version: 1.0
Message-Id: <p06240804c2d62eb767d6@[192.168.1.8]>
Date: Wed, 1 Aug 2007 08:39:28 -0400
To: cygwin AT cygwin DOT com
From: Daniel Griscom <griscom AT suitable DOT com>
Subject: Launching TightVNC over ssh using cygwin
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Antivirus-Scanner: This message has been scanned by ClamAV.
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

I'm using TightVNC on a remote windows machine for maintenance 
purposes, communicating via an ssh tunnel (sshd installed using 
cygwin).

Everything works when I start TightVNC as a Windows service, but I'd 
like to leave TightVNC turned completely off, and only launch it when 
I need it. To do that I need to be able to launch it from an ssh 
command line.

I can ssh in and use cygstart to launch TightVNC, but then when I try 
to connect to TightVNC the connection is refused. Here's the TightVNC 
log (first four lines is when I launched TightVNC; rest is my 
attempted connection):

>Wed Aug 01 08:09:54 2007
>vncServer.cpp:  trying port number 5900
>Wed Aug 01 08:09:55 2007
>vncSockConnect.cpp:     started socket connection thread
>Wed Aug 01 08:10:09 2007
>vncSockConnect.cpp:     accepted connection from 127.0.0.1
>vncClient.cpp:  client connected : 127.0.0.1 (id 1)
>vncClient.cpp:  performing VNC authentication
>WallpaperUtils.cpp:     KillActiveDesktop
>vncService.cpp: unable to open desktop, error=1
>vncService.cpp: SelectHDESK failed to close old desktop 24, error=170
>vncServer.cpp:  failed to initialize desktop object

No, there's no other copy of TightVNC running.

Any ideas on what abilities Cygwin isn't granting to TightVNC that 
TightVNC needs for it to work?


Thanks,
Dan

-- 
Daniel T. Griscom             griscom AT suitable DOT com
Suitable Systems              http://www.suitable.com/
1 Centre Street, Suite 204    (781) 665-0053
Wakefield, MA  01880-2400

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/