AESV2 Plugin and Service start problem

[axel]

I have Ultra VNC 1.0.2 with the AESV2Plugin.dsm.
I can't logon to VNC serwer on windows start (xp with sp2). Service start is installed, keys are the same and versions of ultra vnc are the same.

When I restart PC and try to connect by VNC there is problem with connect. Error is on the image


I thing the problem is in Registry, and VNC dont start by Windows User Logon.
I have read all the Forum and used all FIXES but nothing works.

On other Pc where are Tight VNC , Real VNC free, and Ultra VNC 1.02 installed EVERYTHING works and the Ultra VNC 1.0.2 start in system service by windows logon.

When I try once to connect by windows logon the service goes down, and on the second time i try to connect "Filed to connect to server !"


Please Help !

[kaldag]

On the problem machine have you tried without any plugin???

Ken

[axel]

On the problem machine have you tried without any plugin???

Ken

Without plugins works fine.

[bevtech]

Did you enable the plugin in the server properties. Stop and restart the service and put a copy of the same plugin on your vnc viewer and tell the viewer to use that encryption as well..


I am not sure if that plugin is supported in other flavors of vnc..

[axel]

Did you enable the plugin in the server properties. Stop and restart the service and put a copy of the same plugin on your vnc viewer and tell the viewer to use that encryption as well..


I am not sure if that plugin is supported in other flavors of vnc..

Of courser I did. When I connect to server the viewer has the plugin enabled and it see the aesv2.key.
When I connect first time by windows logon, The VNC Server shut down by first error. I start the VNC Server from services.msc /s and Run Service Helper, the plugin is enabled and the aesv2.key is Found.

Only Chcecking for environment variable %aesv2pluginkey% is Not Found, and this is mayby the problem ?.

[midnightut]

Hi All,

I'm having the exact same problem that has been described above. When connecting to UltraVNC I get an application error on the server, and eventually I'll get a Connection Failed - Error reading protocol version message on the client.

Symptoms:
* On Client Side - After hitting connect the VNC Viewer Status window comes up, Status: Negotiate Protocol Version...
* On Client Side - The password dialog box is never shown
* On Client Side - After closing error box on the server or after timing out, I get an error message that says "Connection Failed - Error reading protocol version."
* On Server Side - As soon as the client attempts to connect a WinVNC.exe Application Error appears that says "The instruction at "0x7c93426d" referenced memory at "0x000801cb". The memory could not be "read"".

Relevent Information:
* Both Server and Client running Windows XP Pro SP2
* Both Server and Client running UltraVNC 1.0.2, AESV2Plugin.dsm 1.0.0
* Using Classical Authentication.
* Server is behind NAT firewall router. All port forwarding is done correctly.
* If encryption is turned off there isn't a problem.
* The Server is also running RealVNC, different port so there shouldn't be any conflict.

Other Observation:
* If I log into the server with RealVNC first, Open the Admin Properties, Cancel out of the Admin Properties, I can connect perfectly fine. Everything works from then on until I restart the server.

Any ideas? Thanks in advance for any help. I'm going to post this on the other thread that seems to be related to this problem as well.

-Mid