2x winvnc.exe - as a service under SYSTEM (listen) + as a user process call command line (connect to other machine), on the same machine at the same time.

[SIT-JK]

Command line: "winvnc.exe -connect IPADDRESS".
I last worked on version 1.2.1.6. Version 1.2.1.7 no longer works.
Calling "winvnc.exe -connect IPADDRESS" also works in version 1.4.3.6, but requires running with admin rights.
If I stop the service and call "winvnc.exe -connect IPADDRESS" in version 1.4.3.6, it also works, moreover without admin rights.
Some idea?

[RudiDeVos]

The injection was considered unsecure. A guest can initiate a remote connection.
This is off by default and need to be enabled in the ini.
[admin]
AllowInjection=1

[SIT-JK]

OK, I tried AllowInjection=1 and it still doesn't work.

[RudiDeVos]

I just tested and it still seems to work.

However first time failed as i added AllowInjection=1 while AllowInjection=0 was also set as option.
I needed to replace the 0 by 1 and not adding the same option.

After change the service need to restart
Don't know if it's the same on your site, please verify

As test i use winvnc -connect , this open the connection dialog and winvnc -connect localhost with a listening viewer.

[SIT-JK]

It doesn't work the same as in the 1.2.1.6 version mentioned, but I got a workaround it in a different way. One question related to this, is it possible to force the winvnc.exe service to reload the INI file other than by restarting it? And if not, are you considering such a feature?

[Neustradamus]

@RudiDeVos: Have you seen the latest @SIT-JK answer?

[RudiDeVos]

Using the server admindialogs, changes are pushed in the running server and saved to ini.
But when ini is changed extern, it isn't detected.
A ini monitor could indeed be a nice feature.