So I'm wondering if this is by design or a bug?
From: "Brad MELENDY" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: vnc server 4.0 can't call listener if server desktop is locked?
Date: Fri, 30 Jul 2004 16:54:55 +0000
Yes, it is running as a service. The main difference is that for some reason, when executed while the desktop is locked, no action seems to take place with version 4.0 (vnc4.exe) as opposed to the version 3.3.7 (winvnc.exe).
When I go back to 3.3.7, it works, however, I run into another limitation which is that I can't specify an alternate port for the host like this:
winvnc.exe -connect 10.0.0.5:5900
I get an error that it can't understand the host to connect to, but that command works with 4.0, however, not while the desktop is locked. In both cases, vnc is running as a service.
...Brad
Brad MELENDY said:
> Hello,
> Strange thing that use to work with version 3.3.7, but if I schedule a
> batch job to run vnc4.exe with the -connect <host> option, it works great
> while my Xp desktop is logged in, but if the desktop is locked, nothing
> happens.
Are you running VNC as a service?
-- William Hooper _______________________________________________
_______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
