Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: 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://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

ConnectPriority=2 ... 3?

Post Reply
AnotherUVNCuser
40
40
Posts: 68
Joined: 2017-09-13 00:40

ConnectPriority=2 ... 3?

Post by AnotherUVNCuser »

Hello,

I've tried to search for an answer but failed to do so.

Despite having played with the various ConnectPriority settings using a reverse loopback connection.
None of the possible settings seem to do anything/have any effect.

Maybe this is normal/as intended for (reverse) local/loopback connections but regardless of this small inconvenience
i would like to know what the differences/purpose are of ConnectPriority=2 and ConnectPriority=3.

ConnectPriority=3 (Refuse all new connection) seems obvious: only allow 1 connection and refuse ALL/ANY new incoming connections

But ConnectPriority=2 (Refuse the new connection): Refuse a new incoming connection, one time??

Please enlighten me.

/AnotherUVNCuser
Post Reply