MSRC4 1.1.8 RC2 aborts connections

MhicAoidh · Post by **MhicAoidh** » 2005-07-09 17:28

Using UVNC 1.0 on XP Pro SP2 as server, clients are 2000 Pro SP4 connecting over WLAN with WPA-PSK AES. Clients also running v1.0 of UVNC.

With MSRC4 118, everything works as expected. However, when 118RC2 is used, the server aborts the connection (according to logs ... available from link at bottom). The client receives a window ...

This error is presented with MS Logon and regular authentication. This happens whether the server is run as service or app as well. Also, with server on one of the 2000 clients, and connecting from XP, the same error is presented. Disabling WPA encryption on the wireless doesn't change results either.

Server and clients are using the same version of UltraVNC (1.0), same version of MSRC4 plugin (118RC2) NoReg, and same key in rc4.key file.

Logs:
http://home.mchsi.com/~mhicaoidh/misc/logs.zip

scovel · Post by **scovel** » 2005-07-09 19:16

Sam, Rudi,

There is something odd going on here. I can't re-create the problem on my test machines.

From the plugin log it looks like it never gets to transforming the buffer. There should be a log entry for the first transform and restore buffer call, but it never gets there. It appears that the server is aborting the connection before it gets there.

In the winvnc.log it appears the server IS aborting, something about "removing unauthorized client."

Sean

redge · Post by **redge** » 2005-07-10 01:30

Network: LAN <--> LAN same subnet 100Mbit/s workgroup (no domain)
Network: LAN <--> WLAN unprotected same subnet 100Mbit/s workgroup (no domain)
OS: XP SP2 pro us (viewer and host)

winvnc port 5900: 1.1.0.1 as service + vnc authen. +dsmplugin
winvnc port 5900: 1.1.0.1 as service + mslogon I +dsmplugin
winvnc port 5900: 1.1.0.1 as service + ms-logon II +dsmplugin
dsmplugin: msrc4plugin118r2_noreg.dsm (same viewer + host)
video hook driver use: yes

vncviewer: 1.1.0.1 + dsmplugin
quick option = lan

-------------------------------------------------------
test connection: direct winvnc port standard

msrc4plugin118r2_noreg.dsm + VNC authen. , successfull
msrc4plugin118r2_noreg.dsm + MS-Logon I, successfull without domain
msrc4plugin118r2_noreg.dsm + MS-Logon II , authentication always fail without domain

------------------------

test connection: with repeater 1.1.0.4 mode I port non standard
winvnc port standard

msrc4plugin118r2_noreg.dsm + VNC authen --> successfull
msrc4plugin118r2_noreg.dsm + MS-Logon I --> successfull
msrc4plugin118r2_noreg.dsm + MS-Logon II --> authentication always fail without domain

------------------------------------------------------

Don't forget to stop and restart winvnc service for validate dsmplugin because there no dynamic loading plugin
(missing feature:
dmsplugin to be loading dynamicallyg would be greatly appreciated without stoping winvnc if possible ?)

MhicAoidh · Post by **MhicAoidh** » 2005-07-10 01:56

I am running version 1.0.0 ... where is 1.1.01 available? Also, a bit of an update. When I uncheck "New MS Logon (supports multiple domains)" the connect still fails, but I don't get the aforementioned error. The status window gets stuck with the following display, and the viewer locks up ... forcing an End Task in Task Manager ...

redge · Post by **redge** » 2005-07-10 02:49

Pre-release 1.0.1( fixes)
[topic=3418][/topic]

MhicAoidh · Post by **MhicAoidh** » 2005-07-10 03:12

Danke. I'll check it out ...

Tried the 1.1.0.1 versions of server and viewer with 118RC2 ... unfortunately no relief. Get same "invalid protocol" window.

redge · Post by **redge** » 2005-07-10 21:46

MhicAoidh

check Task Manager there no vncviewer.exe memory leak

then...
delete:
C:\Documents and Settings\username\Local Settings\Temp\options.vnc
or
from vncviewer
press Delete saved settings
and close vncviewer
start vncviewer and put again all informations

I was retry again and continue successfull connection.

update
when i forgot check activate dsmplugin on server side, I have same error of you, negotiating protocol version (like missing checker RFB)

MhicAoidh · Post by **MhicAoidh** » 2005-07-19 21:14

I tried that, and I no longer get the first error, but the Connection window is stuck at "Negotiating Protocol Version ..." and does not advance to logon prompt.

enzyme · Post by **enzyme** » 2005-07-21 13:48

I have a solution, but it is not great. You first install UltraVNC with service started, you generate your key. You remove your service, you delete all the files except MSRC4Plugin.dsm and rc4.key. You reinstall UltraVNC with service, when he asks you to change the password, you also check DSM plugin use and you select the plugin. Then, installation is finishing normally. Then you do this for all your computers with the same rc4.key and you try.

redge · Post by **redge** » 2005-08-02 21:22

Yes, now, I had same issue with winvnc 1.0.1 and viewer 1.0.1 sometime

discovered cause
vnc password authentication corruption

workaround:
winvnc as service
Run Service Helper

right click on systray icon winvnc
Admin properties
--- Authentication ---
VNC Password:
input again your same vnc password authentication will fix this issue !
close winvnc
net start winvnc
Run Service Helper

after a fews tests, work as waiting be happy

even others beta plugin without rc4.key ask me always a 1st VNC password because i can't inactive it, and then let met login with MS Logon !

Guest · Post by **Guest** » 2005-08-15 20:12

I have on one host same problem ( UVNC on both ends is version 1.0.1 ) I can do anything but always get Invalid protocol error.

Bambid · Post by **Bambid** » 2005-08-16 08:59

Anonymous wrote:I have on one host same problem ( UVNC on both ends is version 1.0.1 ) I can do anything but always get Invalid protocol error.

Host had RC18 installed and worked without problem, after upgrade to 1.0.1 I got above problems, uninstall and new install solved nothing.

redge · Post by **redge** » 2005-08-16 11:37

possible your vncviewer and winvnc lost the path variable?

for fix it, try this solution below about especially "Start in"
Q: Why do I have to select the plugin every time, isn't there an easier way?"
http://msrc4plugin.home.comcast.net/faq.html#shortcut

Bambid · Post by **Bambid** » 2005-08-16 11:46

redge wrote:possible your vncviewer and winvnc lost the path variable?

for fix it, try this solution below about especially "Start in"
Q: Why do I have to select the plugin every time, isn't there an easier way?"
http://msrc4plugin.home.comcast.net/faq.html#shortcut

Thanks for reply Redge, but this problem is only with one host, I have upgraded several hosts from RC18 to 1.0.1 without problem.

David

redge · Post by **redge** » 2005-08-16 12:49

but this problem is only with one host, I have upgraded several hosts from RC18 to 1.0.1 without problem.

Great,

but what the different between the only one not work to others works ?
OS ?
dsmplugin not same release to all others ?
corrupt file options.vnc, from vncviewer, delete saved settings.

difficult to find some solution without more information.

Bambid · Post by **Bambid** » 2005-08-17 13:56

redge wrote:
but this problem is only with one host, I have upgraded several hosts from RC18 to 1.0.1 without problem.
Great,
but what the different between the only one not work to others works ?
OS ?
dsmplugin not same release to all others ?
corrupt file options.vnc, from vncviewer, delete saved settings.

difficult to find some solution without more information.

Redge, when I don´t use DSM plugin can I connect. I tried both MSRC4Plugin.dsm and AESV2Plugin.dsm, no change.

redge · Post by **redge** » 2005-08-17 14:14

export registry of 1 computer working with dsmplugin

export all branch from this point:
HKLM\SOFTWARE\ORL\WinVNC3
HKCU\SOFTWARE\ORL\WInVNC3

on your computer fail with dsmplugin:
close any winvnc, vncviewer
double click on your imported saved registry keys to add it to your computer failing with dsmplugin

Bambid · Post by **Bambid** » 2005-08-18 13:33

redge wrote:export registry of 1 computer working with dsmplugin

export all branch from this point:
HKLM\SOFTWARE\ORL\WinVNC3
HKCU\SOFTWARE\ORL\WInVNC3

on your computer fail with dsmplugin:
close any winvnc, vncviewer
double click on your imported saved registry keys to add it to your computer failing with dsmplugin

I tried it, but no change Redge, same error Invalid protocol. It´s pain, I need to get this working with encryption, while I access this host through Internet.

scovel · Post by **scovel** » 2005-08-21 15:05

Follow the instructions on my plugin website to generate the logfiles. Send me the UltraVNC and plugin logfiles from both the server and viewer computers. Make sure you are using the latest PRODUCTION plugin before you start. Send them to the address listed on my website.

Sean

redge · Post by **redge** » 2005-08-21 22:52

Bambid,

invalid protocol can meaning:

forgotten to copy 1 or 2 rc4.key to one/two computer(s) to correct folder of viewer or winvnc
or/and
an error of spelling

then you need to close winvnc and restart them for validate the change

and

retry to put VNC password to your winvnc as interactive mode.

Bambid · Post by **Bambid** » 2005-08-22 09:37

redge wrote:Bambid,

invalid protocol can meaning:

forgotten to copy 1 or 2 rc4.key to one/two computer(s) to correct folder of viewer or winvnc
or/and
an error of spelling
then you need to close winvnc and restart them for validate the change

and

retry to put VNC password to your winvnc as interactive mode.

I don´t understand it, but after several attempts I finally got it working. I blindly tried AESplugin V2 plugin and now it´s working.

Thanks for help.

UltraVNC

MSRC4 1.1.8 RC2 aborts connections

MSRC4 1.1.8 RC2 aborts connections

Same problem

Re: Same problem