UltraVNC 1.2.3.0 preview 1 - Download links

[stefanorossetti]

in the options when I connect with vnc viewer I can't find u2 protocol, which is better to use?
I seemed to remember that with the previous version the u2 protocol was optimized for windows 10
But perhaps I remember correctly

[Rudi De Vos]

u2 is a modified mjpeg encoder, mjpeg is often used for fast video encoding -> changed u2 to Video

session take long to restart, still need to test this.

[Rudi De Vos]

How do you test the reverse connection ?

I'm doing following test:
winvnc -autoreconnect ID:123456 -connect support2.uvnc.com -run
vncviewer connect using ID 123456 support2.uvnc.com:5901
using latest dsmplugin
Repeater is open for testing: support2.uvnc.com

I don't get a delay
winvnc is running as application

[stefanorossetti]

the delay is not in the connection is when you close the viewer it takes much longer than the vncserver returns on the repeater
using the previous version it returns to the repeater much earlier. This occurs both in application mode and in service mode.

[Rudi De Vos]

Sorry, i just can't repeat it.
This is how i do my tests

server.bat
winvnc -autoreconnect ID:123456 -connect support2.uvnc.com -run
viewer.bat
vncviewer -dsmplugin SecureVNCPlugin.dsm -proxy support2.uvnc.com:5901 id:123456

Close viewer using X and rerun viewer.bat

ultravnc.ini ( passwd removed)

Code: Select all

[Permissions]
[admin]
FileTransferEnabled=1
FTUserImpersonation=1
BlankMonitorEnabled=1
BlankInputsOnly=0
DefaultScale=1
UseDSMPlugin=1
DSMPlugin=SecureVNCPlugin.dsm
primary=1
secondary=0
SocketConnect=1
HTTPConnect=1
AutoPortSelect=1
InputsEnabled=1
LocalInputsDisabled=0
IdleTimeout=0
EnableJapInput=0
EnableUnicodeInput=0
EnableWin8Helper=0
QuerySetting=2
QueryTimeout=10
QueryDisableTime=0
QueryAccept=0
LockSetting=0
RemoveWallpaper=0
RemoveEffects=0
RemoveFontSmoothing=0
RemoveAero=0
DebugMode=0
Avilog=0
path=C:\Users\rudi\Desktop\x86
DebugLevel=0
AllowLoopback=1
LoopbackOnly=0
AllowShutdown=1
AllowProperties=1
AllowInjection=0
AllowEditClients=1
FileTransferTimeout=30
KeepAliveInterval=5
IdleInputTimeout=0
DisableTrayIcon=0
rdpmode=0
noscreensaver=0
Secure=0
MSLogonRequired=0
NewMSLogon=0
ConnectPriority=0
[UltraVNC]
passwd=
passwd2=

[stefanorossetti]

if I use your repeater there are no problems,
if I use my repeater it presents the problem.
I am using the last one available on the site.
if I replace the winvnc.exe files and the plugin with the old ones in the pc to be checked, my repeater also works correctly.
Do I have to make any changes to the reperater?
I also noticed that with your if I close and reopen vncviewer I can connect immediately while with mine it takes several seconds before being able to reconnect.

[Rudi De Vos]

OK, so we need to find the difference...

repeater version i use:
1.4.0.0
12/17/2017
158k
settings
Keepalive require winvnc >=1201 : [v]
Mode : I[ ] II [v]

[stefanorossetti]

I checked my repeater and all the data is the same.
I did another test and noticed that in service mode, your repeater also has the problem of delay. When the service is installed and you come off it takes over 45 seconds to be able to reconnect. Yesterday when I tried I had used application mode and reconnection was almost immediate.
So even with your repeater it has this delay. With the previous version 20 seconds

[Rudi De Vos]

I will check this,
Same parameters but as service_commandline

[Rudi De Vos]

Firsts test as service
open dekstop and run the service with the commandline to autoreconnect to the repeater
-I'm running the viewer on the same desktop
A) I close viewer
As soon as you disconnect you see the icon yellow->green and server is back visable on the repaeter. Viewer has no delay to reconnect

B) Now i want to simulate the lock screen on exit.
In that case winvnc need to restart on the logon desktop.
Starting winvnc by the service in another desktop takes 20 sec.

**What server settings are you using, please pm ultravnc.ini without ip and passwd so i can use exact the same
You compare with an older version, what's the version nummer so i can diff the old src with the new one.

[stefanorossetti]

the previous version that works well is: 1.2.2.4


if you want to enter also on this computer which is a virtual machine I can send you the vnc password and the windows password
(not on the forum but to your email)

the computer is connected to your repeater and the service is installed

[Rudi De Vos]

First test
rdpmode =1
Generate a list of all connected console and rdp users and the connection happen in 2 steps
1) you get a preconnect window with all possible connections and make your selection
2) The server restart in the selected session

Even when you only have a console, rdpmode = 1 add extra checks and timeouts. ( 10-15s)

Is rdpmode also 1 for the 1.2.2.4 test ?

[stefanorossetti]

yes I have always left this value active.
to try :
I just have to replace the winvnc.exe and dsmplugin64.dsm file on the computer that is connected to your repeater and the recontruction times are reduced. As I pressed you with version 1.2.2.4 at the latest after 20 seconds I reconnected while at least 40 seconds passed with the new version. I can't tell you what it might be because the configuration file is the same.

[Rudi De Vos]

I automated the testing
Single folder and just replaced the winvnc.exe and restarted the service, same config and other files.

Start viewer.bat

Code: Select all

start vncviewer -password xxx -dsmplugin SecureVNCPlugin.dsm -proxy support2.uvnc.com:5901 id:38080
timeout 15
taskkill /f /im "vncviewer.exe"
timeout 5
start vncviewer -password xxx -dsmplugin SecureVNCPlugin.dsm -proxy support2.uvnc.com:5901 id:38080

And added some start end connected timer to vncviewer.exe to know how long it wait.

Code: Select all

1224
6/10/2019 14:31 1   start
6/10/2019 14:31 6   connected
6/10/2019 14:31 21   start
6/10/2019 14:31 43   connected

1224, x86 trayicon invisable

Code: Select all

1230
6/10/2019 14:53 10   start
6/10/2019 14:53 15   connected
6/10/2019 14:53 30   start
6/10/2019 14:53 52   connected

1230, x86 trayicon invisable

The second connect is the reconnect +- 22s in all cases

WIth rdpmode =0

Code: Select all

6/10/2019 15:13 46   start
6/10/2019 15:13 51   connected
6/10/2019 15:14 6   start
6/10/2019 15:14 11   connected

First connect or reconnect take 5 seconds.

Used winvnc from latest forum download and the zip 1224 from the website.
Both use the newest plugin

Just saw that you are using X64, going to redo the test for X64

Code: Select all

6/10/2019 15:26 41   start
6/10/2019 15:26 51   connected
6/10/2019 15:27 1   start
6/10/2019 15:27 22   connected

1230 X64,trayicon visable 21s

Code: Select all

6/10/2019 15:30 11   start
6/10/2019 15:30 17   connected
6/10/2019 15:30 31   start
6/10/2019 15:30 56   connected

1230 X64,trayicon Invisable 25s

I don't know what i can test more, same config, and reused it for both tests.

If you don't need rdpmode tray it with rdpmode off, possible the reconnect is also only a few seconds
with the latest version.

[stefanorossetti]

ok
I try to test all rdpmode = 0
thanks

[Lucent]

Hello,
- There are some computers where the desktop wallpaper is not removed.
- In the viewer, I have to double click on the connect button, the first time it does nothing.

[Rudi De Vos]

updated server
rdpmode =1 is only activate when an active rdp session is found.
Unless an active rdp session is found, there is no extra timout.

Downloads
SETUP
https://www.uvnc.eu/download/1230/Ultra ... _Setup.exe
https://www.uvnc.eu/download/1230/Ultra ... _Setup.exe
BINZIP
https://www.uvnc.eu/download/1230/UltraVNC_1_2_30.zip
IPV6
https://www.uvnc.eu/download/1230/Ultra ... 0_IPv6.zip

[Chrispy]

Hi Rudi,

Currently in win 10 as service, winvnc is doing a check for UAC (registry SoftwareSASGeneration) which it not present, but the Service still Shows Login page and I can log in no Problem.
- First Problem, Server brings a Dialog on Screen that no Body can see, and doesn't do anything more.
- Second: If I do see this Dialog and say no, then Login works as planned
- Third: EnableLAU is set, so maybe we don't need UAC (or wrong test in win 10 for UAC, because I am pretty sure it is turned on)

In General, bringing dialogs to the Screen and the server stopping is bad practice anyways. I can't get to the Server to see this Dialog.
An idea, at the Client, have a "Status" window that shows these Messages.

Please check to see if on win 10 UAC is set over SoftwareSASGeneration, I don't think you Need it.

REgards,
Chris

[Rudi De Vos]

When i'm correct SAS works like this for vnc running as service
last time tested with win7 , MS could have changed the behaviour again.

SoftwareSASGeneration = 1 when UAC is enabled
SoftwareSASGeneration must be deleted when UAC is off

Al OS's seems to behave a little different, when time i need to review it.

First Problem, Server brings a Dialog:
MessageBoxSecure is shown on the active desktop ( default/logon) windows 10 behaviour could have changed.
But with new security it's a real bad idea that a service interact with a desktop.

Fast checked: The whole code part is bad, should be in a proper class

[Chrispy]

Does winvnc require that the computer has a monitor?

I have tried, but without a monitor the latest winvnc and 1.2.2.4 show only black under win 10.

[Rudi De Vos]

VNC require aan active video framebuffer.
If the OS in combination with the video card doesn't write to the frame buffer when no monitos is connected it fail.

-Some video card allow you te oeverwrite the detection.
-verify if it isn't a ddengine issue, thi require wdm 1.2 >= video drivers

[Chrispy]

Do you have a recent debug version I can use and see what is happening?

[Rudi De Vos]

Rechecked the "SoftwareSASGeneration"

The whole check run in a seperate thread,it's save.
This is done in vncserver, not the vncservice. The desktop part is allow to interact with the desktop.
SoftwareSASGeneration is needed to be able to use SendSas () ms function.
If you need cntrl-alt-del, SoftwareSASGeneration need to be set and UAC need to be ON.

[Chrispy]

ok, thanks, but my biggest problem right now is the black screen when no monitor is attached by win 10.

These are the same computers, just running win 10 now, and it worked with win 7.

This is really important, without it, we can't use winvnc.

Can you provide a debug ddengine dll so we can see if it is the win 10 driver or the dll? (the debug dlls in svn are from 5.8.2018)

Thanks,
Chris

[Rudi De Vos]

The ddengine is only used when selected.
properties
[v]Desktop Duplication
You can easy disable it.

pixel: slow video memory-> system memory, 5-10 year old video cards
blit: works with all video drivers
ddegine: need al least a wdm 1.2 video driver

What video driver/card are you using ?

https://www.uvnc.eu/download/1230/ddengine_test.zip
Run ConsoleApplication1.exe

[Chrispy]

Hi Rudi,

After making a closer review, I find that in Image ‚Windows 10 LTSB 2016‘ (based on Windows 10 Enterprise 1607) winvnc works without a monitor, but in 'Long Term Servicing Channel‘-Version ‚Windows 10 LTSC 2019‘ (based on Windows Enterprise 1809) winvnc does not work any longer without a monitor.

By "not working", I mean the client gets a black screen.

The files from testing w/wo monitor and the above tool (ConsoleApplication1.exe) are here:
http://www.wowbms.com/ultra/ddengine64test.zip

I tried turning off ddengine64 by INI and it works, but much too slow for our purposes.

Graphic card: NVIDIA NVS 310

Would really appreciate a quick fix, when you have some time.

I can test or get a log for you any time, especially if you don't have the hardware.

Thanks,
Chris

[Rudi De Vos]

Looks like a quick fix wil not be quick.

All vnc version and Temviewer seems to have the same issue.
Graphic card fail to initialize directx when no monitor is connected.
no directX -> ddengine fail to crate directx surface
On some systems running Windows 10 >= v1803

Someone solved it by disabling fast boot in the Bios.
https://answers.microsoft.com/en-us/win ... 0101d6492c

Still searching the net, but if directx fail, ddengine is no option.

[Nanobot]

Perhaps a dummy monitor plug ( display emulator ) is the easiest solution ?

[Chrispy]

Thanks Nanobot for the suggestion.

Rudi, can you then at least switch over to polling if directx fails?

[Chrispy]

We found that going back to an older display driver fixes it sometimes.