vnc server just got screwy.
jnw "at" realvnc.com
Thu Apr 27 17:11:01 2006
What was the _original error_ that you started getting with the standard VNC
server & viewer?
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: marshall "at" cs.utk.edu [mailto:marshall "at" cs.utk.edu]
> Sent: 27 April 2006 00:48
> To: James Weatherall
> Subject: RE: vnc server just got screwy.
> Same problem with the RealVNC server, only the password
> prompt didn't show
> up. Still stalled in the same manner and at the same point in
> the server's
> log file.
> > Hi Marshall,
> > What was the original error that you started getting with
> the standard VNC
> > server & viewer?
> > Basically, it sounds like something is amiss with one or
> other of your
> > systems - have you installed any firewall updates to your
> viewer or server
> > systems, for example?
> > Cheers,
> > Wez @ RealVNC Ltd.
> >> -----Original Message-----
> >> From: vnc-tight-list-admin "at" lists.sourceforge.net
> >> [mailto:vnc-tight-list-admin "at" lists.sourceforge.net] On Behalf
> >> Of marshall "at" cs.utk.edu
> >> Sent: 26 April 2006 04:28
> >> To: vnc-tight-list "at" lists.sourceforge.net
> >> Subject: vnc server just got screwy.
> >> Hi all,
> >> I've been using the free version of RealVNC on my Unix
> >> machine for quite
> >> some time until recently when it simply stopped working
> with all of my
> >> viewers (the ultraVNC viewer on my windows maching and the
> >> .NET viewer on
> >> my Windows Mobile device). I removed RealVNC as I couldn't
> >> get it to work
> >> no matter what I tried. After installing TightVNC, I run into
> >> basically
> >> the same problem. Heres what happens:
> >> With RealVNC Server on Unix, the UltraVNC viewer began hanging on
> >> "Negotiating Protocol." After switching to TightVNC server on
> >> Unix, I was
> >> given an opportunity to enter my password but it would hang
> >> immediately
> >> afterwards, neither accepting nor rejecting correct and incorrect
> >> passwords.
> >> I can connect using a TightVNC viewer, but this means I have
> >> two different
> >> VNC builds on my Windows box, and I'm still stuck without a
> >> viewer on my
> >> PDA.
> >> According to the logfile, when connecting using a TightVNC viewer,
> >> protocol version 3.7 is used and the viewer connects
> >> successfully. With
> >> the currently nonworking viewers I get the following (from
> >> the logfile):
> >> 25/04/06 23:11:02 Using protocol version 3.4
> >> 25/04/06 23:11:02 Non-standard protocol version 3.4, using
> 3.3 instead
> >> This is where it hangs. Any ideas on what's happening? To my
> >> knowledge I
> >> have made absolutely no changes to cause this. I want my old
> >> viewers back!
> >> Regards,
> >> -JM
> >> -------------------------------------------------------
> >> Using Tomcat but need to do more? Need to support web
> >> services, security?
> >> Get stuff done quickly with pre-integrated technology to make
> >> your job easier
> >> Download IBM WebSphere Application Server v.1.0.1 based on
> >> Apache Geronimo
> >> http://sel.as-us.falkag.net/sel?cmd___________________________
> > ________________________________
> >> TightVNC mailing list, VNC-Tight-list "at" lists.sourceforge.net
> >> To change your subscription or to UNSUBSCRIBE, please visit
> >> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list