Royal Apps

We did get some more information from the vendor but there's still no fix for it on the horizon. In previous .NET versions, the vendor put in an override for the DES weakness check which is built into .NET. Since we switched to .NET 5/6 (previously known as .NET Core) the code in the framework changed and cannot be overwritten as easy as before.

It does seem to be related to the configured password though. If you change the password to a stronger one, it should work. Can you try that and let us know if that's the case?

Thanks for confirming, Nicholas!

Would you be able to switch back to the integrated plugin, enable Debug or Verbose logging in the Options, freshly start Royal TS, initiate the VNC connection (which fails) and send us the log (via support ticket)?

This way we can forward the communication log to Glavsoft (company writing TightVNC) to investigate.

Thanks,
Stefan

That's strange. I'm not able to reproduce the error on my test systems. 

What version of Royal TS are you running?

Can you switch to the other TightVNC plugin which is using the locally installed client?

Regards,
Stefan

Hi Nicholas,

we tried to integrate RealVNC several times but it doesn't "play nice" and cannot be embedded like other clients.

You can make TightVNC work with macOS when enabling Screen Sharing with VNC clients permitted:

https://support.apple.com/guide/mac-help/turn-screen-sharing-on-or-off-mh11848/mac

Once macOS is configured you have to specify the password without the user name.

Let me know if this helps.

Regards,
Stefan