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.

-- 


           W. Curtiss Priest, Director, CITS
      Center for Information, Technology & Society
         466 Pleasant St., Melrose, MA  02176
         Voice: 781-662-4044  [EMAIL PROTECTED]
      Fax: 781-662-6882 WWW: http://Cybertrails.org
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to