[SOLVED] TigerVNC - No password configured for VNC Auth
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am currently running Slackware64 14.0 with TigerVNC 1.1.0. I had this working previously, but I can not connect to my computer via my Android tablet within my own network. When I try to connect I get an error : "No password configured for VNC Auth".
I checked in my /home/*user*/.vnc directory and I see the passwd file there. I have deleted, I've used vncpasswd to recreate the passwd file, I have deleted it again, ran vncserver again to put in a new password...but when I try to connect I continue to get the same error.
Hi,
I can connect to my server through windows and linux, but I cannot connect from a specific windows machine to the server. The strange thing is that I get this message, although vnc works fine. Any ideas.
Hi,
I can connect to my server through windows and linux, but I cannot connect from a specific windows machine to the server. The strange thing is that I get this message, although vnc works fine. Any ideas.
First of all:
Next time, create your own new thread instead of digging up an old closed thread, it is considered to be against LinuxQuestions etiquette.
Your case is different, only the error message is the same.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.