FYI: we created a KB article with troubleshooting tips for VNC connections: https://support.royalapps.com/support/solutions/articles/17000129245-troubleshooting-vnc-connections
Hello,
I have the same error, when trying to connect to a Mac using the integrated TightVNC plugin:
Message:
Specified key is a known weak key for 'DES' and cannot be used.
I talked to the support a couple of weeks ago and only using the external TightVNC Plugin solved my problem.
I am on Royal TS 6.1.10324 - Beta (the official release did not work either)
I tried with the non-integrated tightvnc and seems to work.
yup, opening support ticket now.
Hi Mariano! I'm sorry that this is so confusing. We can't really change that behavior because it's part of the VNC specs/implementation. The error messages we get from the VNC server are sometimes not really helpful.
I see. Mystery solved. Glad you got it working!
These are the generated Test-Passwords which for example won't work:
2uy?$Ib0
0bLbTM%-
r4wFcAO&
I tried to change to a stronger password, but on Mac it is limited to 8 caracters, so unfortunatly no success with that.
Hey Stefan! thanks for letting me know. And thanks for the KB! that would be very helpful for people that run into this again :)
Sure, we always can put up a knowledge base article with some troubleshooting tips if a certain error occurs. I'm hesitant to implement "special error handling" based on generic error messages because in our experience this can also lead to confusion when that error occurs for a completely different reason. This has happened before and in the end we regretted the customized error message because the situation completely changed over time.
I imagined that something like that was happening that was not "fixed" already. (and with fixed I mean just dropping the correct error) Maybe add the error to a troubleshooting guide somewhere? Maybe when connecting to vnc ask for credentials by default? and a checkbox to "do not ask" if still someone out there that leaves a vnc server without a password... Is not difficult to reproduce, just install TightVNC server on any windows 10 or 2019+ server and try to connect to it without setting credentials
Thanks for the reply!
Ok, so, setting the credentials works. Its time to do something at Royal, to ask for credentials, or the error to be "set credentials" that would save 30 minutes of googling to fin this hidden post and read all replies... :D
Ahhh I did not see your last answer. With this it works!!
I did not know that I have to set credentials and I waited for a window to ask me for it.
Thank you very much!
It just dawned on me that I haven't seen any screenshot/configuration from your VNC credential in Royal TS. Did you actually specify the password in the connection's credential page (in the password field while leaving the user name field blank)?
That's weird because the passwords (with 8 chars) we use, work fine in our tests. Can you try a couple 8 char passwords with letters, numbers, symbols and try if that helps. If it doesn't, can you share one of the combinations you tried so that we can verify this on our end? Please don't share any of your "real" passwords ;)
Nicholas DiCola
tightvnc doesnt seem to work with MAC osx.