10961 Beta

[Rudi De Vos]

Updated bins can be found at
http://www.uvnc.eu/download/10961

Please test bins and confirme if fix works.
Sometimes fixing A breaks B....

published: OK== bins are in download folder
source fix: OK==source code has been fix (internal use)




server
*crash chat x64
status
-confirmed
-source fix: OK
-published: OK

*AuthRequired=0, passwd=NULL: Warning message block service
status:
-confirmed
-source fix: OK
-published: OK

*About x64 say win32
-confirmed
-source fix: OK
-published: OK

*viewer 1082 and server 1096 with localcursor ( no connect, 100% cpu)
-confirmed
-source fix: OK
-published: OK

*serversite scaling and multiple viewers, framebuffer size get overwritten
-confirmed
-source fix: OK
(Scale is now lock when multiple viewers are connected to avoid a
framebuffer change, first connected viewer set scale. Site effect is that
the viewer report the unused, incorrect scale, but at least it doesn't crash anymore)
-published: OK

*-connect ip, passed to winvnc running as service is not remembered for
autoreconnect.
-confirmed
-source fix: OK
-published: OK

*-stopreconnect
stop the autoreconnect function of the server.
-source fix: OK
-published: OK


*server mouse moves jump on viewer when screen is idle.
corrected
-confirmed
-source fix: OK
-published: OK

*old_plugin crash ( zlib/ultra)
-source fix : OK
-published: OK






viewer
*plugin (SecureVNCPlugin) used by viewer
server without plugin
give incorrect viewer message. And doesn't ask to reject the connection.
-confirmed
-source fix: OK
-published: OK



*monitor value is saved, but vncviewer read it as bool (true/false)
Only 0/1 are correct imported
-confirmed
-source fix : OK
-published: OK

*old plugins fail when zrle encoding is used
-confirmed
-source fix : OK
-published: OK

*old plugins give incorrect info in statusbox
-confirmed
-source fix : OK
-published: OK

*-autoreconnect timeout, -reconnectcounter number
(available from gui and commandline)
-confirmed
-source fix : OK
-published: OK
-autoreconnect timeout was incorrect, updated

*old_plugin detction was incorrect
-source fix : OK
-published: OK

06/05/

SERVER
-autoreconnect was indeed invers, corrected again
-All Messagebox() replaced by a function that put it on the visable desktop ( done for all messageboxes)
-Auth Message dll not found, name corrected and refuse access.
-if all groups are empty check also admin.
-if OS_SHUTDOWN initiated ingore all lock functions.

bins uploaded

[redge]

service_commandline=-autoreconnect id:1234 -connect repeaterhost
vncviewer connect to server with correct dsmplugin and password

1st win7 direct connect vncviewer (22 April) to winvnc (18 April) vista
2nd connect vncviewer via repeater id:1234

securevncplugin 2.3.0.0 OK, can connect next one immediately.(multi-connexion allowed)

msrc4plugin 1.2.4.0 (only single connection allowed) known limit.
stand 5 min on negociate protocol then crash after error message instead just show error message.

winvnc on vista crash with msrc4 1.2.4.0

Problem signature:
Problem Event Name: APPCRASH
Application Name: winvnc.exe
Application Version: 1.0.9.6
Application Timestamp: 4dac94fa
Fault Module Name: MSRC4Plugin.dsm
Fault Module Version: 1.2.4.0
Fault Module Timestamp: 4a523f89
Exception Code: c0000005
Exception Offset: 00002eb5
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 4108
Additional Information 1: 15b3
Additional Information 2: e3f1e64ceb03dbfad76292d2400b254c
Additional Information 3: 9572
Additional Information 4: 0ca54170f48010df6859cbb7c3945c82

[Rudi De Vos]

Old plugins are not multi threaded.
msrc4plugin use a trick to multiply himself, by changing his name for the second instance.
Old/New plugins are detected by name -> this will not work.

Multiple connections -> use securevncplugin

securevncplugin
- multithreaded
- >8 char passwd
- selectedable encryption

Possible we drop complete the msrc4plugin support in the next version.
The 2 different engines are just a hell to maintain, and almost all bugs are related to this.

[redge]

vncviewer 28 April to 2 May Ultra2 encoding GUI checkbox issue
and use the key arrow down unable to select u2 except with mouse pointer.
(delete saved setting already applied and restarted vncviewer)

cause:
the fix of detect old msrc4 plugin name like msrc4plugin1240.dsm and autoreconnect and reconnectcounter behavior GUI

Ultra2 encoding of vncviewer GUI NOK (there double selection
Ultra2 encoding of vncviewer CLI OK
double clic host.vnc OK
tested w/wo plugins by host.vnc OK

[YY]

Rudi,

Please take a look on B's post [BUG] Some Serious Bugs

Looks like some are still existing in 10961 (at least I think No.2 & No.8 are not fixed yet)

[B]

Thanks for finding that, YY. I forgot I put all those in one place.

[Rudi De Vos]

-autoreconnect was indeed invers, corrected again ( bug YY)
-All Messagebox() replaced by a function that put it on the visable desktop "done for all messageboxes" ( bug YY)
-Auth Message dll not found, name corrected and refuse access. ( bug YY)
-if all groups are empty check also admin. (bug 8 B list)
-if OS_SHUTDOWN initiated ingore all lock functions. (bug 2 B list)

Any confirmation on fixed or not ?

I realy want to release an 10961 update...

[YY]

Have verified ....

>>>> -autoreconnect was indeed invers, corrected again ( bug YY)
Working Great Now !!! Please see the Bug: Autoreconnect function broken on 1.0.9.6


>>>> -All Messagebox() replaced by a function that put it on the visable desktop "done for all messageboxes" ( bug YY)
For those Error/Warning message box that I have reported, they are now visible and properly displayed.


>>>> -Auth Message dll not found, name corrected and refuse access. ( bug YY)
OK now.


>>>> -if all groups are empty check also admin. (bug 8 B list)
I tested this too. Now working properly.

[redge]

Any confirmation on fixed or not ?

I realy want to release an 10961 update...

please wait test of YY about vncviewer so we don't have "stupid" bugs come back

[Rudi De Vos]

2 new fixes.

javaviewer
While waiting for the new Javaviewer i did a little trick.... add 2 javaviewers
One with and one without mslogon, if the server use mslogon browser download javaviewer(mslogon)
Live swicthing between mslogon and vncpasswd is not supported, files are loaded on vnc startup.

Signed java using an official certificat ( same cert as for winvnc.exe seems to work for java)

lock keyboard/mouse
viewer icon now proper indicate if keyboard is locked this is not to screen blanking state....
If not running as service, system security settings often give permission denied when you try to lock the keyboard,
now the icon displayed on the viewer use this permission info to show lock icon or not.
Permission to lock keyboard and blank screen seems to be independed...icon only indocate keyboard locking.

Blank monitor
works but is limited in usage.
win7 with aero, only monitor power functions can be used (limited, permission)
win7 without aero support the background image ( prefered method)
The lock icon give the keyboard state, not the blank monitor state. If you use the "non aero" alpha blending method, you
also can check if the top cover window is running.

file updated

To test:
JavaViewer with and without mslogon / filetransfer

lock keymouse/blank screen

[v]Enable Blank monitor on viewer request
[ ] Disable, Only Inputs on...
( monitor +keyb lock)
[v]Enable Blank monitor on viewer request
[ v] Disable, Only Inputs on...
(keyboard lock)

[davidgrudek]

Will this new java viewer support one port for both it and the viewer?

[Rudi De Vos]

You mean, same port for java download and rfb.
This require a special server build, it has nothing todo with the java viewer.
Only it isn't very stable

Special build added to download

The webviewer use the rfbport (default 5900)
If you set it to 80, you only need port 80 to to use the viewer.

http://www.uvnc.eu/download/10961

winvnc_SINGLE_PORT_JAVA.zip

[davidgrudek]

what is unstable about it?

[Rudi De Vos]

You use the same port for java download an rfb.
On connection, winvnc need to detect if it's a webbrowser requesting for data or a vncviewer that only want rfb data.

When i'm correct the problem was.
The detection has trouble with non webbrowser or rfb packets that arrive on port 80, sometimes you need to connect
multiple times before the connection engine get back in sync.

We also use a new encryption engine, don't know if a special version with single http port
still can be used for normal connection and encryption.

No time to test it proper--> unstable.

[nelsonk]

Any confirmation on fixed or not ?

I realy want to release an 10961 update...

please wait test of YY about vncviewer so we don't have "stupid" bugs come back

Viewer x64 1.0.9.6.1 (Built May 2) shows Win32 in the Connection and About dialogs.

>>>> -All Messagebox() replaced by a function that put it on the visable desktop "done for all messageboxes" ( bug YY)
For those Error/Warning message box that I have reported, they are now visible and properly displayed.

Add the DS_CENTER property to the About and Connection Options dialogs and let Windows take care of centering of this dialogs in the active display.

Thank you all.

[ghost_zero]

Since the new website I can't download the 1.0.9.6.1 files anymore.
I can open the folders and see the files, e.g. winvnc.zip but once I click on one of the files I get back to the main page.

However, it works if I copy the URL and then enter it into the address bar of the browser directly.

[Rudi De Vos]

Thanks for the info, wil be fixed this evening...
I need to modify the trusted sites list...

[Rudi De Vos]

access back ok

[davidgrudek]

This version looks pretty good. When do you think it will get released? Probably the most stable build yet.

[Rudi De Vos]

weekend 4june

[Pow]

Too late to get the fix Tom Goodman (bz922x) posted about to resolve the Java viewer scrollbars in Firefox?
http://forum.ultravnc.info/viewtopic.php?f=34&t=14561

[redge]

yes, too late
there others known issue with java and single port
until prompt authentication OK
after vnc authentication, network error, NOK
i think is old java problem and not rfb.
other known issue
FT if vncviewer running from protected folder %programfiles%\UltraVNC
unlucky for fix FT, i will list soon all known limit of uvnc 1.0.9.6.1

[Cheval]

Did the 10961 get released? Got a minor issue with 1096 where if the network DHCP host gets reset while connected to another machine server, the Win7 32 client blue screens.

[Rudi De Vos]

No, we had web server issue's this weekend.
I will try to make the builds this evevning.

[Scanweb]

In this versjon i get "ERROR: Media not present in the local drive " ?

Perhas I should reinstall a more stable version, worked before I uppdated.

Best regards.

[Rudi De Vos]

Did you use the same Filetransfer settings
impersonate []

ON= run as desktop user, only access to folders that the desktop user can access, access to mapped folders.
OFF= run as system, access to all local files, no access to mapped folders.

This version has been testdrived for several months, if there was a general problem with the FT
it would have been noticed at least be one beta tester.

[NoFastidies]

hello everyone!

I've noticed that the latest winvnc.exe 1.0.9.6.1 doesn't allow me anymore to have 8greycolors mode, wich is really needed for performance issues. it always shows a mode that seems to be the 256 colors.

partial command line of viewer, that worked on latest 2010 version, was:
vncviewer.exe ... -noauto -8greycolors -encoding tight -compresslevel 9 -quality 0 -disablesponsor -shared

and

[jellysandwich]

Hey guys,

I installed the latest 10961 on June 24th. I don't know why, but I keep getting remote connection errors in the notification bar. I'm not quite sure what is causing these errors...

The ip addresses given seem to be random; The last one I checked ended up as a San Fransisco address (I live in NYC).

http://i54.tinypic.com/1555ctc.jpg

[B]

jellysandwich, I've seen people mention this issue before. The big question is whether these connections are inbound or outbound.

If they're inbound, then the natural interpretation is that your router is forwarding the port properly, and that random drive-by scanning malware is probing your open VNC connection (and, luckily for you, failing to authenticate). Simple solution: pick an obscure non-standard listening port other than the default 5900. Also make sure you have a solid password.

If they're outbound connections, then your PC is trying to initiate connections, and we'd have to question (a) whether you got a clean copy of UVNC, and from where, and (b) if your machine is infected with some kind of trojan. No simple solution!

[flutista82]

Hey all!

NoFastidies--I was having the same problem. 256 colors is the only option I see with 10961.

Thanks!