Possible BUG for server version 1.0.8.2 + repeater

[Feri]

Hello,
Last few weeks I wanted to implement Ultravnc 1.0.8.2 with a repeater (linux).
The problem that appeared from the start was that at the beginning, when I started the ultravnc service on the server, I could connect/reconnect to it, but as time past (minutes/hours) it was more difficult to connect (a lot off error messages). I use repeater mod 2 and the autoreconnect option:
service_commandline=-autoreconnect ID:100 -connect remote::xxxx

In the logfiles on the server side I found nothing, but in the repeater I saw that after I started the sever, it autoreconnects every few seconds. This interval seems to get bigger and bigger, so after 8-10 hours we have ~15 minutes between the autoreconnects. I tried Windows repeater and it has the same result. So it's not the repeater.
Yesterday, I installed server version 1.0.8.0 on one of the computers and it seems that after 12 hours it still reconnects after a few seconds (using the same linux repeater, and without touching the server):
With 1.0.8.0 server and linux repeater - after 12 hours (notice the time difference):
UltraVnc Sat May 15 09:13:51 2010 > acceptConnection(): Server sent code 110
UltraVnc Sat May 15 09:14:26 2010 > acceptConnection(): Server sent code 110
UltraVnc Sat May 15 09:14:31 2010 > acceptConnection(): Server sent code 110
UltraVnc Sat May 15 09:15:06 2010 > acceptConnection(): Server sent code 110
UltraVnc Sat May 15 09:15:40 2010 > acceptConnection(): Server sent code 110

With 1.0.8.2 server and linux repeater - after 8 hours (notice the time difference between the "start" and end):
UltraVnc Fri May 14 20:07:06 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 20:08:50 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 20:10:44 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 20:12:18 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 20:14:34 2010 > acceptConnection(): Server sent code 119
.....
.....
.....
UltraVnc Fri May 14 22:06:09 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 22:12:23 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 22:19:18 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 22:25:53 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 22:33:09 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 22:40:33 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 22:47:38 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 22:55:24 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 23:02:50 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 23:10:54 2010 > acceptConnection(): Server sent code 119
UltraVnc Fri May 14 23:19:08 2010 > acceptConnection(): Server sent code 119
......
.....
.....
UltraVnc Sat May 15 04:11:26 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 04:24:34 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 04:37:26 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 04:50:53 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 05:03:59 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 05:17:48 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 05:31:18 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 05:45:29 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 05:59:19 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 06:13:49 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 06:28:00 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 06:42:49 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 06:57:18 2010 > acceptConnection(): Server sent code 119
UltraVnc Sat May 15 07:12:27 2010 > acceptConnection(): Server sent code 119



I think there is a bug in the 1.0.8.2 server version at the autoreconnect part.... some variable is increasing....


Any ideeas? It would be nice to have a fix for this.
Until then I will go on with the tests on version 1.0.8.0

Have a nice day!

[supercoe]

Thanks for the info Feri, I didn't realize this wasn't a problem with 1.0.8.0

I've been experiencing this issue as well and would love if it could be fixed.

I too have tested with multiple repeaters on Windows and Linux with the exact same result.

This bug is confirmed as far as I'm concerned, we need a fix!

[B]

Funny, YY had just mentioned a similar workaround (reverting to 1.0.8.0) at [topic=17903][/topic]

I'm looking forward to testing that! (Although YY had led me to think I might get away with using the newer server with the old repeater, Feri's summary confirms our other testing placing the blame on the UltraVNC server.)

With Feri's details perhaps someone can ferret out the problem (and the difference in behavior between versions).

The changelog for 1.0.8.2 as per FileHippo:

server
- <b>deadlock fixes</b>
- win2003, xp ( all pre vista) fast user and RDP fix
- color error when using the driver in 16bit color mode.
- added multiple monitors for non driver mode
- corrected mouse behaviour with multiple displays
- mirror driver was used on vista>= and color was 8/grey/b&w crash fix

* viewer
- <b>listen and add new client fail to connect fixed</b>
- skewed viewer in 254 color mode fixed
- scrollbar and resize fix
- auto mode set to fix color to prevent crash
- write exact error" replaced by "server closed connection
- <b>cancel force socket close</b>
- viewer -listen also remember command lines

* installer
- download files uncheck fix

Possible suspects highlighted, although none seem apropos.

[B]

Okay, I grabbed 1.0.8.0, took JUST the winvnc.exe out of the ZIP archive, and used it in place of my existing InstantSupportVNC.exe in ChunkVNC's service directory.

Viewer end is unchanged, and this single-file drop-in actually worked, and connected right to the repeater I've been testing. Now to wait a few hours and see if 1.0.8.0 works for me where 1.0.8.2 locked up.

(If it does work, I would suggest that SCPrompt, ChunkVNC, and other derivatives bundle 1.0.8.0 until the issue is resolved, but that's getting ahead of things. I will let you know how it goes later today.)

Hey, even better, early results shows that the "Select Full Desktop / Switch Monitor" function works a LOT better in this older version too! That feature was approaching non-functional for me in Chunk/1.0.8.2.

One interesting thing, though not entirely apples to apples, is I note the file from the 1.0.8.0 distribution is 1,545 KB while the one Chunk is using was 960 KB, and the one in the 1.0.8.2 zip is 1,533 KB. That's a big difference -- was there a significant rewrite or other explanation for this <i>relative</i> "bloat" between point versions?

Edit: Fixed order of sizes

[supercoe]

Thanks for testing this B I'm letting it idle as well.

Single file drop in is why I designed it this way, it's really easy to change versions of AutoIT and UltraVNC by overwriting.

I haven't tried with multi monitor yet, interesting as the changelog shows that 1.0.8.2 was the one where they "fixed/added" multi monitor.

Keep us posted.

EDIT: The 1.0.8.0 bins zip shows me a 1545kb winvnc.exe, the 960kb exe is from pgmoney (the stock ChunkVNC exe), smaller icons.

[B]

No problem.

EDIT: The 1.0.8.0 bins zip shows me a 1545kb winvnc.exe, the 960kb exe is from pgmoney (the stock ChunkVNC exe), smaller icons.

Oh you're right -- I just recapped them wrong. Correcting it above...


Also, I wonder if I should test with a drop-in of 1.0.8.2 too then? It's certainly possible that my issues stem from the pgmoney version alone...

[supercoe]

Worth a try, the stock exe from pgmoney AFAIK is based on 1.0.8.2 with the "don't close the viewer when UAC prompts" fix.


BTW: 1.0.8.0 is working really well for me so far!

[supercoe]

I just noticed in the first post that the versions are flip flopped, the top example (after 12hrs) is from 1.0.8.0 working correctly not 1.0.8.2 as stated.

My testing so far has confirmed this bug, 1.0.8.2 after many hours will take exponentially more time to connect back to the repeater and 1.0.8.0 connects every 30 seconds.

[B]

Great news, then, if you can call a fallback to prior version "great". I am still waiting a bit longer before retrying the viewer... let's see, the last time I tries was about 3-4 hours ago. I think I'll wait another hour before I touch it; I want the test as comparable as possible to prior ones.

Meanwhile, were there any show-stopping problems with 1.0.8.0? Was Win7 compatibility functional?

[Feri]

Thanks for the info
I corrected the post.

the 1.0.8.0 i working very well for mee too!! I've tested it on windows XP, Vista, W7, 2008 all 32bit, and it is working corectly! (W7 and 2008 with UAC enabled)

BUT I have an other problem with this 1.0.8.0 version. Even if i set in the ultravnc.ini AllowShutdown=0 and AllowProperties=0, user still can stop or uninstall the service if he right clicks on the uvnc icon in the tray.
"Stop service" and "Uninstall Service" are not grayed out in the right click menu.
Is there a workaround for this problem?

Thanks

[B]

I don't know, but would that actually accomplish anything?

Regardless of options grayed out, if you're remotely controlling a user who has administrative rights, you could always navigate to his Control Panel, Services and kill the service there anyway, couldn't you?

[B]

Well, I couldn't wait any longer, and I tried my "localchunkviewer" again -- it works! Fired right up through the repeater and the server responded.

1.0.8.0 is a major "win" for me here. supercoe, please think about using that in the next ChunkVNC. (Or maybe someone can figure out a quick patch to 1.0.8.2.)

And the switch-monitor feature continues to work light-years better for me than 1.0.8.2 did. This is interesting, since the VIEWER side has remained the same and is still the 1.0.8.2 code; only the server has changed in my test.

If Rudi is listening I would politely ask that he please take a fresh look at these two issues (repeater and switch monitor code) and reconsider what changed in 1.0.8.2.

For me speed is still slow and autoscaling is very inconsistent in both versions.

[supercoe]

The new plan is to take Rat's code add some mods and release a 3.2 with our recent revelation.

This has been working great in my tests and relieves many large headaches for me and others.

The only problem I've had so far (using the Perl repeater) was connecting a viewer before a computer completely rebooted, the repeater didn't see the server disconnect when the machine rebooted.
No biggie tho just "server running as app" error, perfect on second connect.

[B]

More hours later and it's still connecting like a champ for me.

Very slow screen draws, perhaps because my test repeater's distant.

But the switch-monitor function still works MUCH better than the 1.0.8.2 did for me.

[Feri]

Regarding the "Stop service" and "Uninstall Service" are not grayed out in the right click menu:

Yes, a user with admin rights could go in control panel services and stop the service, but he couldn't easly uninstall it. He should know some commands to do that.
With the uninstall option in the right click menu, the user (with admin rights) could uninstall the vnc service even by mistake...

Does anyone know how could I recompile VNC Server so it will have an other name/ID? I would like to do this so I could install my Custom uVNC Server and Ultravnc or Tightvnc on the same machine?
I would need this to be able to install my uVnc on computers already running tightvnc or uVNC.

Thanks.

[supercoe]

More hours later and it's still connecting like a champ for me.

Very slow screen draws, perhaps because my test repeater's distant.

But the switch-monitor function still works MUCH better than the 1.0.8.2 did for me.

Still working great for me as well after 10 hours of idle reconnecting!!!

Performance is spot on for me compared to 1.0.8.2, my local repeater seems a little faster than the vps if that's what your talking about B.