The sample use the localhost, so server connect to viewer running on the same host (replace localhost in helpdesk.txt to connect to a real external host)Ĭheck helpdesk.txt and SC_20.ini in sample to see how to add it. Rename pubkey to SC_Server_ClientAuth.pubkey and viewer key to SC_Viewer_ClientAuth.pkeyģ) Run vncviewer (make sure the viewer key is in the same folder), select encryption and start listener I will do some tests.Zip can contain (SC_Server_ClientAuth.pubkey, helpdesk.txt SC_20.ini background.bmp logo.bmp)ġ) Start normal winvnc.exe, select encryption SecureVNCPlugin.dsm and generate keys. Thinking about the SDMPluginConfig for example. My Ini has been migrated since quite a while. Knowing you can't reproduce the issue I can play with some ini options. Weirdly a repeater connection seems to work without winvnc.exe crashing and even displaying notification properly.
I tried disabling mslogon2 at no avail as I thought it might be related. I am getting an authentication prompt but after entering the password the winvnc.exe service is crashing and re-spawning immediately, dropping the connection from the client. Perhaps its my configuration but I am unable to connect to the service using UltraVNC 1.4.0.2 client. Unfortunately I still get winvnc.exe processes crashing immediately when directly connecting to the service (using SecureVNC plugin). Sadly I have to report that I still got issues.įirst the good news: The notification message now seems to work for me using repeater connection. Where do you actually still get machines which are 32-bit only and which (supported) OS do you run on them? Is there any other reason to still run any 32-bit applications? First of all many thanks for having a look.
0 kommentar(er)
