I have some time to prepare an update, a list could be handy as starting point.

List1) Repeater 2014 + server ( added keepalive messages ) : Both need to be updated, backward compatible not possible as repeater was original made without a version check. (OK)2) Save passwd/options fix: Current it fail if the logged user is a domain admin. (REQUIRE TEST)3) Logmein alternative ( test started, waiting feedback)

Rudi De Vos wrote:1) Repeater 2014 + server ( added keepalive messages ) : Both need to be updated, backward compatible not possible as repeater was original made without a version check. (OK)

Please excuse this stupid question, but which side do you mean to be not backward compatible? Server or repeater side?If I want to update the repeater now, but I have old 2013 winvnc.exe out there, this will work, won't it? But a new winvnc.exe won't work with old repeater, will it?

This means the 2014 server is not backward compatible to old repeater, right? (I hope so!!)

No, the new repeaters keepalive message is only understood by the new servers.The old server get a unknown message and close connection.

The old server doesn't crash. And if auto reconnect is set it reconnect to the repeater.But the keepalive message behave like a disconnect message.

-------------old server--------Server send init, server wait viewer answer.It's the server that's waiting for the viewer and the viewer answer need in some specific format.If some other format arrive -> close connection

Rudi De Vos wrote:It's just impossible to make something that works with old servers

But it's also impossible to update 600 customers helpdesk the same time!

This means, we won't be able to update repeater (and viewer?) as long old winvnc.exe are out there.And if we wait updating our side (repeater and viewer) and we role out the new server and hope that in a few months only new servers exist? As far as I understood this won't be also not possible, because the new server will close the connection with an old repeater/viewer. Is this correct?

new server understand keepalive, when not used it just behave like before.

old repeater + new server -> works like 1196 , keepalive is never send by the repeaternew repeater + new server -> repeater send keepalive, it's understood and server doesn't timeout new repeater + old server -> repeater send keeplaive, server don't understand it and reconnect

For the viewer it doesn't make a difference, the keepalive is only send on the server site.

Old servers will still work with the new repeater.The only difference is that with the old repeater ( during "waiting for viewer connection") reconnected every x minutes, the new every minute.We can increase this value to 5-15 minutes, 1 minute is just for testing and isn't needed to keep the line open.But is still think that the new repeater with a 25 minute keepalive interval behave better then the old repeater, even with an old server.Yes the server reconnect, but all is proper done and sockets are proper cleaned on both sites.

OK, we'll have a big update roll out within 4 weeks. So it's recommend to roll out the new server with this update. We'll keep the old repeater as long as technical possible. If we have to renew the repeater one day hopefully only new servers are out there...

When will we have a stable 1.2? Can we help testing? What are the neuralgic functions to test?

I have connected 100 (id) serverdiscovered the problem:sometimes come IDwhen I want to connect to the IDRepeater shows that there is no such ID but after restarting Repetar this ID is presented, and can connect to this ID.

it has already been tested with the latest version (winvnc64.exe Changes for 2014)but I expect that there is not the problem server UltraVNС this problem in the Repeater

On the client side, I would like a "rate limit mouse cursor messages" to avoid flooding the server with so many packets.This option has always been present on RealVNC. Can this be added back to UltraVNC ?

OK, I needed 2 explanations. But after the second one I thought I understood. But obviously I didn't:

If I run a test winvnc 2014 (service mode) against distributor/repeater 2013, which as far as I understood should work, winvnc-service tries 8 times to connect with winvnc+service_commandline and stops trying.

Can anybody confirm that winvnc 2014 is able to connect to repeater 2013?

old repeater + new server -> works like 1196 , keepalive is never send by the repeater

Can anybody confirm that winvnc 2014 is actually able to connect to repeater 2013? I already reported this, but I'll do it again:

Prisma wrote:

If I run a test winvnc 2014 (service mode) against distributor/repeater 2013, which as far as I understood should work, winvnc-service tries 8 times to connect with winvnc+service_commandline and stops trying.

-A "restart service" button under the "stop service"-An option in the repeater to kick people. Would be nice if combined with previous option.-A multi-tab client, so I could connect to 3 servers in the same window, with a tab layour like modern browsers.-WoL client built in the repeater. We already have the last IP (and MAC if you decided to keep it). Its not a big deal to configure a persistent DB in the repeater to remember the last IP/MAC from each ID

More advanced things:-A way to send a file to a server and force it to execute it/store it somewhere, without even sending any image to the client. It would be usefull for massive deplyments. You could add a login feature if needed.-An easy way (or an API) for external applications to communicate with the repeater. My idea is to make a frontend which asks the repeater for info about stablished connections, waiting servers etc.-Some way for an application to ask a running server about the current state of his connecion. My idea it to build a service to watch over the UVNC service and avoid connection losses.