I'm doing like this as well but there's a problem: whenever winvnc crashes, there's a dialog box popped up on the console asking if I want to terminate it or to debug it (that I suppose is a consequence of installing Visual Studio). So, I have to get to the console (using TS client or walking to server room) to press the key to let VNC service restart again.
> -----Message d'origine----- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Envoyi : jeudi 11 mars 2004 02:25 > @ : [EMAIL PROTECTED] > Objet : Re: VNC 3.3.7 does not work w/ Windows 2003 Server > > Well Mike, I'm using VNC 3.3.7 server on Windows 2003 server, but remember after > installing it, set the VNC server to start as a service and then set the service > properties to re- > start the VNC server if the VNC server service fails. > > It works fine, but on the odd occasion VNC 3.3.7 server crashes on connect. If you > configure the service to re-start one minute after a failure then it's possible to > live with this > problem. > > If you wish to be able to lock the console on a disconnect, expected or unexpected, > then > avoid VNC 4 beta as it does not have the `workstation lock on disconnect` feature. > This > feature is going to be in a future release of VNC4. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
