> From: =?iso-8859-1?Q?=22Beerse=2C_Corn=E9=22?= <[EMAIL PROTECTED]> > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > Subject: RE: Unknown authentication screen? > Date: Mon, 1 Jul 2002 09:38:58 +0200 > Reply-To: [EMAIL PROTECTED] > > > -----Original Message----- > > From: Shing-Fat Fred Ma [mailto:[EMAIL PROTECTED]] > > I'm using 3.3.3r2+tight1.2.2. I've got a vncserver running > > on solaris 8 for a while, and connect to it regularly from a > > PC running of WinME using cygwin's ssh together with local > > loopback to the ssh port. Works fine normally, but I > > recently encountered an error message after typing in my VNC > > password, something like "Unknown authentication scheme". > > The vncserver log file has 987 ctrl-@ symbols at the point > > where I try to connect, followed by > > > >>>>>>>>>>>>>>>>>> log removed <<<<<<<< > > > > Even though the vncserver seems to continue beyond the > > authentication point, the vncviewer doesn't (it just > > terminates). > > That's because it cannot get the connection. > I got a similar (the same?) message while twiggling file rights on the unix > side: The vnc password file (~/.vnc/...) must be readable by the Xvnc > process. Try to give everyone read rights to the password file AND give > everyone execute rights to the directory ( ~ and ~/.vnc ) so the file can be > accessed.
Actually, it is a personal directory (I'm a vanilla user). I tend to believe your explanation below, since the problem only occurred with my running vncservers that day. > > Would anyone have any clues about this, or even just similar > > experience? I haven't ruled out the fact that our solaris > > network is glitchy as it undergoing some kind of upgrade > > (partially completed on Friday, to be completed Tuesday). > > Other details include that I run into this problem with the > > several vncservers that were running since before Friday, > > and that the problem goes away if I clobber all the servers > > and start a new one. > > If your home directory is on the network, it's possible the Xvnc process has > lost the route to the passwordfile due to a network drop. It's possible all > works by now (after the weekend, hopefully without network drops). If not, > then best to restart the vncservers. Done. It worked. No further problems. > If there is any work in the current running services, you can try to send > them a HUP or a 'signal 15' (kill -15 Xvnc-pid) but that might also kill > them... That's what I did. Killed 'zem all....Mwaa-Haaa-Haaa-Haaa-Haaaa !!! And you're right, all procsses as well (but then, I used my "zonk" script, which does exactly that). Too bad one can't redirect and app from one display to another. > CBee Thanks, Fred ------------------------------------------- Fred Ma Department of Electronics Carleton University, Mackenzie Building 1125 Colonel By Drive Ottawa, Ontario Canada K1S 5B6 [EMAIL PROTECTED] =========================================== _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
