Been using TightVNC viewer/server for many years. It seems they released a new version that is all screwed up. First, it’s not backward compatible with my existing .vnc files. When I click they fail to open up the remote session. Next I open up the TightVNC viewer, enter the host name and password then it lets me in. Old .vnc files all have to be deleted. I can’t connect to any of my machines running the old server. Had to upgrade each machine I remote to or not connect. Next I click the save configuration button on top. Sometimes it prompts me to save the password and sometimes it does not. When it does prompt me to save the password the next time I open the .vnc file for that connection and it’s still prompting me for a password. This is unacceptable for my LAN. The next issue is it prompts me to Connect without encryption and there’s a checkbox to remember this setting but the next time you open up the .vnc file it is STILL prompting. They also changed the icon to something new? Why did they change a TRUSTED brand? So now I have to run it without password protection to avoid having to enter the password each time. What did TightVNC do? Should have left well enough alone. It was working BEAUTIFULLY until they messed with it. I wish I had the old installer but I don’t and couldn’t find it. No password protection on my LAN now.
You may also like
I’m another user going around this merry-go round again. I purchased a Synology NAS DS718+, installed Plex and Docker (calibre-web-server), and have […]
I’m a new hired developer for a company that is using Magento CE as their CMS. I’m trying to set up a […]
18 November 2011 Last updated at 18:13 ET By Mark Ward Technology correspondent, BBC News In a few short years many of […]
I am using a rocky8 system on which I need to build, install and run a 3.10 kernel. I managed to get […]