UltraVNC 1.0.2 + Fix Test 1 and Test 2 online for testing

[UltraSam]

Available here:

http://sc.uvnc.com/UltraVNC-1.0.2-WinVNC-Fix-test-1.zip

http://sc.uvnc.com/UltraVNC-1.0.2-WinVNC-Fix-test-2.zip

They only contain the Winvnc.exe 1.0.2+fix file with modifications
that aim to prevent reported unstability of the ultravnc server since a few weeks.

This unstability may be caused by some port scanners over standard VNC port 5900, but we are also digging in others directions like bad thread/socket cleaning during client disconnetion and big first buffer bad handling.

- This test1 patch should help us to confirm if the unstability is caused by ports scanners or not.

- The test2 patch focuses on various sockets options changes.

If you want to help, please make a backup of your current unstable winvnc.exe file, replace the file with the one of this archive in your UltraVNC directory, and restart Winvnc.

If test1 does not solve the problem for you, please try test2

We continue research on our side.

Thank you !

[roytam1]

As usual please commit the fixes to the cvs and/or svn. Thanks.

[UltraSam]

Of course... but that's not yet fixes, only fix attempts, that need to be confirmed.

Unfortunatly I don't have a lot of feedback on them so far

[roytam1]

Of course... but that's not yet fixes, only fix attempts, that need to be confirmed.

Unfortunatly I don't have a lot of feedback on them so far

Thats why I hope you can commit them so that people can check the code.

[bschuler]

I get following error:
error: framebuffer update rectangle too large vnc
I've tried both fixes and the error doesn't disappear.
Rgds
Bernhard

[GhaladReam]

I've been using UltraVNC 1.0.2 + Test1 for about 2 days now, and I can report that UVNC server has NOT crashed on me yet. It used to give me an error several times a day that told me that I couldn't connect to my server for one reason or another, and that I need to use the DSM plugin, even though I didn't have it set up to use it. It has been rock solid for the past 2 days on Test1.

Just so everyone knows, I've re-installed, refomatted, just about everything to try and get this working, so it wasn't something I was doing wrong. I'm simply reporting that Test1 is working for meso far.

If anything happens, or it crashes again, I will reply to this thread.

[tedrock]

test 1 fixed my "Framebuffer update rectangle too large" issue.

[UltraSam]

Thanks for the feedback !

Glad to see that Test1 improves things for some of you.

For those having connection stability problems (especially over DSL) like conection dropped after a while when connected with the viewer then unability to reconnect to the server, I'd like them to give a try the Test2 patch and see if it's better or not.

Thanks again for your help.

[UltraSam]

I get following error:
error: framebuffer update rectangle too large vnc
I've tried both fixes and the error doesn't disappear.
Rgds
Bernhard

So you are using the Javaviewer, right ?

Do you have stability/connection problems with vncviewer.exe as well ?

[tedrock]

I spoke to soon. Ii getting on today and got the same framebuffer error as before. It was to good to be true
Guess I'll try test 2.

[UltraSam]

I spoke to soon. Ii getting on today and got the same framebuffer error as before. It was to good to be true
Guess I'll try test 2.

You use the JavaViewer ?

[tedrock]

that would be correct. i only use the java viewer. i connect via safari on an emac running 10.4.8 as well as a imac with the same setup.
it did work yesterday all day so i'm thinking it might be my pc. i'll try test two on sunday night

[GhaladReam]

Test 1 is still running rock solid with no hiccups for me. I posted in this thread a couple of days ago and just want to keep everyone posted. I used to get a similar problem where the vncserver.exe process would lock up and I'd have to kill the process and restart it in order to be able to access my server again, however it's been very stable for the last 3-4 days. Before, this problem would occur 2-3 times per day. Also worthy of note is I'm running Windows Server 2003.

[tedrock]

test 2 seems to have fixed my "Framebuffer update rectangle too large" issue. But I said that about test 1 too. I'll wait a few days and see how it goes.

[UltraSam]

Ok... so we are waiting... it would be a good news if confirmed

[tedrock]

Bad news... Framebuffer update rectangle too large with test 2 now.
It's the same thing as test 1, test 2 worked for like a day. I restarted a few times last night and then tried from work today. I still think it could be something on my system... so now what?

[wiesl]

Available here:

http://sc.uvnc.com/UltraVNC-1.0.2-WinVNC-Fix-test-1.zip

http://sc.uvnc.com/UltraVNC-1.0.2-WinVNC-Fix-test-2.zip

They only contain the Winvnc.exe 1.0.2+fix file with modifications
that aim to prevent reported unstability of the ultravnc server since a few weeks.

This unstability may be caused by some port scanners over standard VNC port 5900, but we are also digging in others directions like bad thread/socket cleaning during client disconnetion and big first buffer bad handling.

- This test1 patch should help us to confirm if the unstability is caused by ports scanners or not.

- The test2 patch focuses on various sockets options changes.

If you want to help, please make a backup of your current unstable winvnc.exe file, replace the file with the one of this archive in your UltraVNC directory, and restart Winvnc.

If test1 does not solve the problem for you, please try test2

We continue research on our side.

Thank you !

Test2 doesn't fix the following AES Plugin Problem:
[post=32374][/post]

Instruction 0x7c94426d, Read Memory 0xffffffff

Hope it helps

Wiesl

[tedrock]

well i restarted ultravnc and test 2 has been running solid for a a day or so. i still think it's something system related.

[wiesl]

well i restarted ultravnc and test 2 has been running solid for a a day or so. i still think it's something system related.

Do you run the AES V1.00 plugin, too?

Wiesl

[tedrock]

what is that? never even heard of it.

[wiesl]

what is that? never even heard of it.

It is an Encryption Plugin.

Wiesl

[GhaladReam]

I am posting a 3rd time to report that Test 1 has solved my issue completely. VNC Server used to crash several times a day so I couldn't connect to my server. It has been over a week now and it has not crashed a single time. Whatever was done in Test 1, it has completely solved my problem. Keep up the good work!!!

If you want info on what my problem was, read further up this thread.

[gigatain]

Unfortunately rather Fix 1 nor 2 helped me to solve my problem.
I'm running the UltraVNC Server on a Windows Server 2003 Enterprise Edition.
If i now try to connect via the JavaViewer i get the following error msg:
Framebuffer update rectangle too large: 0x0 at (63972,1730)
what does that mean???
And if i try to connect via the VNC Viewer i only see a black screen.

Every help is welcome!

[tedrock]

i found something strange. if i simply close the vnc application and then reopen it it gets rid of the frame buffer error i've been getting...

[wiesl]

Available here:

http://sc.uvnc.com/UltraVNC-1.0.2-WinVNC-Fix-test-1.zip

http://sc.uvnc.com/UltraVNC-1.0.2-WinVNC-Fix-test-2.zip

They only contain the Winvnc.exe 1.0.2+fix file with modifications
that aim to prevent reported unstability of the ultravnc server since a few weeks.

This unstability may be caused by some port scanners over standard VNC port 5900, but we are also digging in others directions like bad thread/socket cleaning during client disconnetion and big first buffer bad handling.

- This test1 patch should help us to confirm if the unstability is caused by ports scanners or not.

- The test2 patch focuses on various sockets options changes.

If you want to help, please make a backup of your current unstable winvnc.exe file, replace the file with the one of this archive in your UltraVNC directory, and restart Winvnc.

If test1 does not solve the problem for you, please try test2

We continue research on our side.

Thank you !

Test2 doesn't fix the following AES Plugin Problem:
[post=32374][/post]

Instruction 0x7c94426d, Read Memory 0xffffffff

Hope it helps

Wiesl

Maybe try to restart the computer, let it run as service, and just try to login remotly to reproduce the problem (It is always reproduceable for me after a reboot).

After a manual restart of UltraVNC it works well, but sometimes after some runtime (disconnect/reconnect) it happens again.

Hope it helps.

Wiesl

[UltraSam]

i found something strange. if i simply close the vnc application and then reopen it it gets rid of the frame buffer error i've been getting...

Has you rebooted after having replaced the winvnc.exe file ?
Are you running winvnc as a service ?

[tedrock]

Has you rebooted after having replaced the winvnc.exe file ?
Are you running winvnc as a service ?

i don't think i've rebooted after replacing, i just restarted vnc. I think that's all the readme said to do.
i don't think i am running it as a service. I just go to the startmenu and select UltraVNC Server from there. I don't see UltraVNC in my services list but i do see VNC server there and it's set to auto.

[superpollo65]

I tried both test1 and test2 and I have the same problems : black screen on viewer side in all XP Home with IE7. Viewer hang if I try to close it (I need to kill application).
I disable all firewall.

Is there any solution ?
I'm new of ultravnc, I saw FAQ, but I'm not able to make it works. Please help

[Arnie_75]

Does 'Google Earth' run through the viewer with Test 1 or Test 2? The latest stable v1.02 does not run Google Earth with the hook driver.

[OfficialGuest]

Available here:
http://sc.uvnc.com/UltraVNC-1.0.2-WinVNC-Fix-test-1.zip

This test doesn't solve connectivity problems.