UltraVNC

Hello Rudi,

I hope you're doing great! We use a rather old version, very stable, so no reason to post and ask things.

But now we would be interested to protect our repeater with SAML or openIDconnect with an IdP. But, as we found out, this was way too complicated (and would be much work for you ...

I browsed and searched the version log with GIT. No specific updates for WIN11.
But many security fixes since then. There are many good reasons.

I'll mark this topic as answered.

We are very conservative while updating WinVNC because it's vital for us. Never change a running system without good reason. But if there is a good reason, don't hesitate to change.
Trying and failing is less effective. But maybe it's also not that easy and effective to answer. I'm really sorry, if ...

Hello Rudi,

we are using a rather old version 1.2.3.0 and are encountering some refresh problems with Win11.
We do not use any mirror driver, but all needed DLLs.

Here is the question:
Is there a recommendation from your side to upgrade to newer winvnc versions, especially regarding Win11?
Of ...

Works like a charm, thanx Rudi.

Hello Rudi,

we have also a - let's say - trusted environment, where only reverse connections through repeater are made and client and server find each other using a randomly generated repeater ID. So, we also don't need authentication.

Is there a possibility to set "AllowUntrustedServers" in .vnc ...

Regarding SAS / CAD:

sas.dll - no more needed? In actual builds not included.
setcad.exe - Only for tweaking the registry to enable SAS?

I thought to remember that on the first start of winvnc.exe in service mode (copy&paste, no installer!) on a Server 2019 system I was prompted if I wish to ...

Hello Rudi,

previously we already wrote about the long time it takes before winvnc comes back to the repeater when closing the viewer during rdp=1 and an existing rdp session.
I'm not absolutely sure, but I think we figured out that one exe is waiting for the other exe a fixed time instead of ...

Running since 09:00 in production environment, normal (heavily) used. No problems until now.

THX for the answer.

‎Hello Rudi,

from what I heard only viewers were affected by several vulnerabilities. Not the server itself.
1. Is this correct, or were servers also affected?
2. A repeater listening on the standard viewerport for incoming reverse connections is a potential aim of people scanning for vulnerable ...

It's not completely clear what your aim is.
I assume you use Mode II with reverse winvnc connection at the moment?
Same port not possible. Using TLS for server/viewer means using and enforcing secureVNCplugin.
Most firewalls filtering outgoing traffic won't block your reverse winvnc connection, if ...

Hmmm, tested. First of all I noticed that enforcement of handling rdp sessions with rdpmode=1 is still necessary.
From what I understood it shouldn't be necessary because of defaulting to activated.
Maybe I misunderstood something, or it will only be activated by default in future when stable ...

Btw: Tested with RDP connection, switching between the sessions slow but working stable. Without RDP session active reconnect fast as promised. I tested it also before.

Please let me ask one thing:
From what I understood the long timeout is for giving the server part with the connection/session ...

@rdpmode:
Tested: reconnect takes no more extra time.
Not tested: is the rdpmode functioning at all?

Question: Did I understand right, rdpmode=1 is obsolete in future?

Maybe this helps:

PS C:\Users\User\Desktop> query session
SITZUNGSNAME BENUTZERNAME ID STATUS TYP GERÄT
services 0 Getr.
>console User 1 Aktiv
rdp-tcp 65536 Abhör.

Nope, must be something different. Sorry:
Obviously no rdp active.

Tested newest winvnc.exe. Still the same.

Possibly a repeater related issue? Maybe it's a fix which only shows effect in connection with a newer repeater?
Not sure how old our repeater is. Not very old but a little...

Please excuse, just a typo. Of course I tested with 13/10 not 13/09. Re-checking your upload...

Tested with rdpmode=1, it takes still up to 30 seconds to come winvnc.exe back on the repeater. Even though there is no rdp session active or pending.
With rdpmode=0 it still takes only up to 6 seconds.

Tested with 32-bit server from 13.09.
There's no newer one in setup and zip...

oh my god, it's working like a charm!! what a relief... can't believe it.
thank you so much.

And: should something like "path=%userprofile%\desktop" or "path=%userprofile%\documents" work at the moment?

"RDPMODE only switch in rdmode when an active rdp session is found."
Great idea!

Testing 1.2.3.0 pre-release semi-production.
noscreensaver=1 seems to work like charm. THX a lot Rudi!

I know rdpmode=1 is an old option. We plan to activate it by default.
Did this option ever become productiv, or is it still beta?

Regarding "takes a long time to come the server back to the ...

Please excuse, but I tried to test the new screenshot function. In the new viewer I found an option to configure the path.
But how to shot the screen? During the remote session I didn't found any button or menu entry to take the screen shot. Or am I blind?

Ok, tested new secureVNC plugin on server side against old plugin on viewer side. Works obviously.
But (maybe this was the same with old plugin):
We use reverse connection to repeater. After closing the session on viewer side, it takes very long to come the server back on the repeater.
Were there ...

Rudi,

I noticed the x86 securevnc plugin in your provided ZIP is old. It's from 2016.

So my testing was no testing...

Testing new secureVNC plugin right now. No problems until now.

BTW: Have seen a "secure=" option in ultravnc.ini. What's the representation on the GUI?

Tested prevent screensaver. Works like a charm. Going semi-production with preview build. Looking forward for release. Timeline?

Hi Rudi,

for flexible or centralized usage and automation of *.VNC files, it would be nice if environment vars could be used in path. It should be possible to save images to userpaths like documents or desktop without having to use different VNC files.
Something like "path=%userprofile%\documents ...