Curt, Here is another possible workaround. I've haven't used it specifically for VNC, but I have used it for situations where I needed to get into an NT box remotely to stop some process.
The latest release of the cygnus windows tools (www.cygwin.com) includes a windows side server for ssh (and sftp, etc.) I make an ssh connection to the windows box and do whatever is necessary (in your case stopping and restarting VNC). This isn't a fix, but it can be used until a fix is available. I think that people are still working on VNC, as there have been recent releases. I suspect that they don't have NT environments for testing. (I don't either, unless I load up a machine with NT for testing purposes.) The development folks can confirm (or deny) the accuracy of that statement. Seth On Saturday 31 August 2002 14:15, W. Curtiss Priest wrote: > OK. > > Let me do a brief review: > > 1. A person can see in the Services list that VNC is > still running (when it is hung) at the remote machine > > 2. A person can see it in the Task list running > (when it is hung) at the remote machine > > 3. The hang occurs upon closing the VNC client window -- > never during a session > > A probe of the VNC server via telnet X.X.X.X:5900, > when the VNC server is hung, does not produce a reply > RFB 003.003 > > But a probe of the VNC server via telnet X.X.X.X:5900 > does produce the reply RFB 003.003 even when > there is a VNC client connection to the same machine > being probed this way > > 4. If we stop and restart, VNC, as a service at the remote > server, manually, everything is fine again > > 5. The firewall lets VNC through, so it is hard to > pin the problem on the wirewall (by Norton, which is > running on the same machineas the VNC server) > > 6. The inability to reconnect occurs after working > with the machine for some time; if it is > reconnecting, I can disconnect and reconnect again > and again (exiting by closing the client window) > as many times as I wish > > 7. I have found a more sure way to assure reconnection > by running this script to disconnect: > > NET STOP winVNC > NET START winVNC > > [this closes my client window and restarts VNC > after I am gone] > > As a Service I should not try: > > winVNC -kill > winVNC -run > > as -kill and -run does NOT apply to a Service > > 8. It is believed that the hang relates to having at > least one app. abnormally abort, but this > may simply be happenstance > > I am running the latest AT&T release V. 3.3.3 R9 > > One reader (Seth) replied he heard of such a problem but > thought it was fixed in the current release. > > *** > > Question. > > Is someone still updating VNC who has an interest in fixing > this? > > Yes, I could use Microsoft's Remote terminal client, but, I hate > Microsoft with a vengeance as they leave little room for 3rd > party products (like VNC !) :) And, I am familiar with VNC and > like it's ability to run, e.g., under NT4, etc. -- ----------------------------------- Seth Kurtzberg M. I. S. Corp. 1-480-661-1849 _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
