RE: Cannot access locked server

[Simon R. <si...@ca...>]

Did you install it as a service?

It should work even when you lock the machine if it runs as a service.

Simon

-----Original Message-----
From: vnc...@li...
[mailto:vnc...@li...] On Behalf Of Jim
Bohnsack
Sent: 29 ao=FBt, 2005 14:53
To: vnc...@li...
Subject: Cannot access locked server

I have recently installed TightVNC after having problems with the older=20
RealVNC I had been using until the early August MS upgrades.  My server =
is=20
running Win2K and the PC at home I use to access it with is WinXP.  If I =

lock the server PC and then try to access it from the client, I never =
get a=20
response from the client.  In the WINVNC.log I see:

Mon Aug 29 14:42:31 2005
vncSockConnect.cpp : accepted connection from xxx.xxx.xx.xx
vncClient.cpp : client connected : xxx.xxx.xx.xx (id 1)

with the x's being the correct client ip addr.  I can connect with no=20
problem if I do not lock the server, but I really don't like to do that=20
when I leave for the day or weekend.

Is there a server or client configuration choice that I've missed?  I=20
always used to be able to do that with the older RealVNC client (3.3.6)=20
that I was running, at least I could before the early August updates.

Jim

Jim Bohnsack
Cornell Univ.
(607) 255-1760





-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle =
Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & =
QA
Security * Process Improvement & Measurement * =
http://www.sqe.com/bsce5sf
___________________________________________________________
TightVNC mailing list, VNC...@li...
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list