Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
1.3.9 dev 2
1.3.9 dev 2
Sorry, I have not tested the new cloud features of UltraVNC. I am just trying to use the 1.3.9 dev 2 vncviewer to connect to an existing 1.3.8.2 install. I tried various encoding settings and the Auto Encoding setting, but each time I try to connect to the remote PC I am getting the error message: "Info Message / No supported authentication methods!". BTY, the 1.3.9 dev 1 vncviewer will connect to the exiting 1.3.8.2 install without issue.
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: 1.3.9 dev 2
I know... the damm initial message breaks a lot of code
Fixing A breaks B and fixing B breaks C
Fixing C breaks A again...
Real fun
Fixing A breaks B and fixing B breaks C
Fixing C breaks A again...
Real fun