Bug under VNC 1.2.0.1 + repeater 1200

[dgoiko]

Hello.
I first posted this on UVNC 1.2.0.1 forum (https://forum.ultravnc.net/viewtopic.php?f=70&t=31061), but then I thought it may be caused by DSM plugin rather than UVNC:
If I try to connect directly to a server using DSM plugin it works fine, checks pkey, asks for password and lets me control the server.
However, when using repeater I get error reading protocol message regarding DSM issues (forgot DSM, not compatible DSM,plugin missconfigured,wrong password, someone else using DSM). Client and server are both the same, nothing changed. It only gives error when using repeater 1200

May it be the plugin being confused by the keep-alive messages? If so, are there any chances for the problem being considerated for a fix?

Thank you so much, and sorry for double posting.

[Rudi De Vos]

First test seems to work.
*Both server (add new client) and viewer make an outgoing connection
*Using SecureVNCPlugin.dsm with standard vnc passwd
server 1201 + viewer 1201 + repeater 1200
Tested again with dsm and predefined key and all seems to work.

keepalive messages are unencrypted ( this are some dummy messages send before rfb version is exchanged) . Encryption is activated after rfb protocol exchange and before you enter the password.

Is it working with the older repeater ?
Please verify if the server is 1201... older server doesn't work with the new repeater.
The first keepalive message is only send after a minute...to test you always need to have the server connected for a few minutes
before trying to connect the viewer. If you connect the viewer just after the server, the new repeater behave the same as the old
( keepalive is never sended)

[dgoiko]

Hello.
with predefined keys you mean keys created by yourself or some kind of default key the program automatically generates if no key is found?
I've tested again removing every key from my uvnc folder, and then it is working. However, if I create keys it doesnt work.
It happens on both windows XP and 7SP1-64 bits.
Server and client are 1201, repeater is 1200
[EDIT]
By the way, when it fails it doesnt even asks for the password.

[Rudi De Vos]

retested
1° key generation
dsmplugin config (20140915_Server_ClientAuth.pubkey,20140915_Viewer_ClientAuth.pkey)
Instead of a local bouncer i now use a repeater i started on support1.uvnc.com ( that's 300km away)
copy pkey to viewer
I still works.., normal as the encryption is activated after the viewer connect.

Are you using 64bit plugins for 64bit exe ?

You can use our repeater for testing

[dgoiko]

Yes, I'm using 64 bit pluginms for 64 bit system. Like you, i'm connecting to a remote network (60-80 kms from my testing "lab")
Today I could connect without problems to that computer, I changed absolutly nothing since it started to fail...
It may have been an error on my network or on the destiny network I'm using to test repeater 2014...

Anyway, thanks for the attention. I'll let you know if something like this happens again during my testing phase.
Would you recommend me to update 100~ clients to version 2014 after testing? or shall I wait for an stable version?

[dgoiko]

And here it comes again. After a day of succesfull testing, I came across the strange bug again:
If somehow the connection is unexpectecly closed (by server as far as I've tested), the client is not able to connect to ANY server again.

This gave me something to think about: maybe the problem wasn't on the end, but in the middle:
I restarted the repeater and then the problem was gone. Two remote servers which dissapeared for a couple of days appeared aswell.

If you tell me how to enable some kind of debug level in the repeater I'll try to reproduce the bug and send you the logs.

[Rudi De Vos]

If the webgui still can be accessed , the log could show something.
In the past we had trouble with the webgui, if installed on port 80 some scanner caused the webgui to crash and use 100%cpu.
Please verify if the webgui is still working and repeater is not eating cpu.

[dgoiko]

I'll try to reproduce the error and pass you the new logs. However, I know for sure webgui was still working while I couldn't connect to servers. The servers connected normally to the repeater.
The webgui is installed on port 81.
There's a 2013 repeater running on same computer, different ports.

[Rudi De Vos]

Could you still see new viewer ?

Internal
webgui thread
server wait thread
viewer wait thread
seperate thread for each waiting server.

If no new viewer showup, viewer waiting is locked.... this could already eliminate a big part of the code.

Only change between 2013 and 2014 is the waiting server thread.