On Sat, 2003-01-11 at 12:48, Daniel wrote: > I'm running VNC 3.3.6 on Windows 2000 Pro. SP3, if I start VNC normal and > later close it with the taskbar menu only the taskbar icon will be removed > but the Server is still running. > If I start VNC as a system service, and try to close the service the system > is trying to close VNC and aborts with an error message. > Has anybody else this problem?
This behaviour usually means that WinVNC was unable to connect back to itself to free the threads that accept incoming connections (the accept() call in Winsock is unfortunately pretty broken.) When you notice that WinVNC will not stop, can you run "netstat -an" from a command line and check how many sockets are *listening* on ports in the range 5900-5999? If there are two listening sockets on the same WinVNC port number then this can cause serious problems. Cheers, -- Wez @ RealVNC Ltd. - http://www.realvnc.com Open Source VNC - Commercial Support & Development _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
