Release 1.3.4.2

Release 1.3.4.2

Postby Rudi De Vos » 2021-10-02 17:44

Hibernation stopping the service have been fixed

https://www.uvnc.com/downloads/ultravnc ... 3-4-2.html
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 6377
Joined: 2004-04-23 10:21

Re: Release 1.3.4.2

Postby CPC » 2021-10-03 21:11

Hello

One minor observation... just regarding file properties. Just pointing out - if there is a need to update this info. I'm looking at 1.3.4.2 32 bit

If you right click on the winvnc.exe and look at the properties...
File version says... "1.3.4.0"
Product versions says... "1.3.4"
and
If you right click on the wvncviewer.exe and look at the properties...
File version says... "1.3.3.0"
Product versions says... "1.3.4.2"

No issues found yet. Testing both viewer and server wrapped in my single click reverse connection app and they seem to be working well.

Thank you for the new version and all those who have contributed to its development.
CPC
CPC
20
20
 
Posts: 52
Joined: 2010-10-08 15:31

Re: Release 1.3.4.2

Postby Rudi De Vos » 2021-10-04 09:39

Thanks,
Gonna update the fileversion, some update software with replace only new set could get in trouble
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 6377
Joined: 2004-04-23 10:21

Re: Release 1.3.4.2

Postby Chesser » 2021-10-11 13:09

Hello!
Another bug found.
If through the "viewer" connect to a PC with a running "server" with the "viewer only" option. Then press the key combination Ctrl+Alt+F3 and go into control mode. Then press again Ctrl+Alt+F3 and switch to the "viewer only" mode. In this case, on the PC with the "server", pressing the button will be simulated Ctrl until either on the PC with the "server" this button is pressed manually, or until the "viewer" closes the viewing window.
Chesser
 
Posts: 7
Joined: 2019-09-13 02:18

Re: Release 1.3.4.2

Postby esc » 2021-10-13 09:48

After updating to 1.3.4.2 - I cannot transfer files. I get an error:
File Transfer permission denied: disabled or unknown user or version incompatibility.
- but it worked fine before the update
- file transfer is enabled
- versions are the same on the client and server

- what is an unknown user? after all vnc has no user login with password
esc
 
Posts: 5
Joined: 2020-12-11 09:26

Re: Release 1.3.4.2

Postby SkyBeam » 2021-10-13 16:07

Chesser wrote:Hello!
If through the "viewer" connect to a PC with a running "server" with the "viewer only" option. Then press the key combination Ctrl+Alt+F3 and go into control mode. Then press again Ctrl+Alt+F3 and switch to the "viewer only" mode. In this case, on the PC with the "server", pressing the button will be simulated Ctrl until either on the PC with the "server" this button is pressed manually, or until the "viewer" closes the viewing window.


I think it's not the first time this gets reported. Actually I believe CTRL+Alt keys are "stuck" after pressing CTRL+Alt+F3 in the viewer. The reason is simple:
  • User pressing CTRL, viewer sends "CTRL down" event to server
  • User pressing Alt, viewer sends "Alt down" event to server
  • User pressing F3, viewer catches key combination and goes into view-only mode
  • User releasing CTRL+Alt+F3 keys, since viewer is in read-only mode it won't send "key up" events to the server

A solution would be that the viewer is releasing all key modifiers right before going into read-only mode.
SkyBeam
40
40
 
Posts: 85
Joined: 2012-12-31 11:01

Re: Release 1.3.4.2

Postby SkyBeam » 2021-10-13 16:09

esc wrote:After updating to 1.3.4.2 - I cannot transfer files. I get an error


I don't have a solution but just tested a server running as service and a viewer both on version 1.3.4.2 and have been able to successfully transfer files.
Perhaps a change inside the auth code might cause the issue for you. Now the new viewer is printing a warning if there is no authentication and you're connecting to unauthenticated server. So you might want to make sure there is proper authentication (at least a password set). I personally use mslogin2 module. No issues with file transfers discovered yet.
SkyBeam
40
40
 
Posts: 85
Joined: 2012-12-31 11:01

Re: Release 1.3.4.2

Postby esc » 2021-10-13 17:35

Yes that's right. I did nothing and now it works ... Strange.

Are there any pluses of mslogin compared to using SecureVNCPlugin64.dsm and a stronger password in it?
esc
 
Posts: 5
Joined: 2020-12-11 09:26

Re: Release 1.3.4.2

Postby SkyBeam » 2021-10-14 06:14

esc wrote:Are there any pluses of mslogin compared to using SecureVNCPlugin64.dsm and a stronger password in it?


Mslogin is rather compared and alternatively used to a plain VNC password. The advantage is that it authenticates against a Windows system or domain user account. So you can manage the user on system or domain level including its password and permissions rather than to have maintaining the UVNC configuration.

SecureVNCPlugin is actually handling the transport encryption. So strictly speaking it's not doing authentication but rather securing the communication channel only. So both are actually independent. You can run with encrypted communication only but not asking the user for any authentication. But this means if VNC server is accepting also unencrypted connections you might be able to connect without any username/password given (no authentiction). If transport encryption is strictly required and involves some shared secret on server and client side, then it might be safe too as both parties need to know the keys. But I would consider this to be more weak than actually enforcing real authentication on top of encrypted communication channel.
SkyBeam
40
40
 
Posts: 85
Joined: 2012-12-31 11:01

Re: Release 1.3.4.2

Postby esc » 2021-10-14 16:41

Yes, I understand. I have been using ultravnc for about 10 years but last year I had a bad case with a password. I used the normal password from the program. I knew it was saved in a file but I didn't know it was that easy to decode. Many people have access to the remote computer, so I thought that if someone changed the password, I would know quickly - because I would not log in. But someone did not change them, but decoded them - and used some time. And here was the problem. The same thing can happen with a windows account - having access to the computer. Someone can create a new account simply. Therefore, it seems to me that in my case the password from SecureVNCPlugin64.dsm will not be so easy or decodable. I hope.
esc
 
Posts: 5
Joined: 2020-12-11 09:26

Re: Release 1.3.4.2

Postby arauser » 2021-10-17 10:31

Please upload msi files. We are deploying UltraVNS in several large organizations. Installation with tsi is very convenient
arauser
 
Posts: 1
Joined: 2021-10-17 10:26

Re: Release 1.3.4.2

Postby Quader » 2021-10-25 07:15

Hopefully the right place to post, if not please move where it belongs.
We are using the latest Version of UVNC.

Hello, i hope someone has experienced the same problem and has an answer.

i have 3 network outposts with 20 "Windows 10" clients in each.
in every network i have a fritzbox 7490 and portforwarding to 3 "clients" with your uvnc server running as a service.

everything runs good since 3 years, until a few weeks ago when we realized it doesn't work anymore, (and i think this is the thing) Windows made updates.

since then it works only inside the network to connect but not from the outside, except for 1 client who
i cut from Windows Updates, it is still on Updates from 08.2021 which work, but every newer Windows
does not connect anymore from the outside.
In the same network 2 other Updated Clients do not work anymore, so i don't think it was a Fritzbox Update.
We also have a Lan-Lan VPN, there it also doesn't work between those two.

The failure is simple, it does not find the Server when coming from outside (Timeout). Same System with internal IP in the same network works.

My Setting is from "Server" to "Client":

"Remote Server" is Windows 10 newest Updates, Solid IP Adress, Windows Firewall has UVNC and Port excluded
-> Fritzbox 7490 (Server Side), Portforwarding to IP and Port of Client, the port is in one case 2020 which is not needed else, i also use the Secure Plugin but have also tested without.
-> Dyndns Service (payed)
-> Fritzbox 7490 (Client Side)
-> Client UVNC with "dyndns-adress::2020" and Secure Plugin enabled

I tried newest builds and older ones to check if it relates on uvnc but it is the same.

Maybe Windows/Microsoft has disabled something so uvnc is now useless.
Before i invest in VPN Routers, to be inside the network where it works,
i thought i write here, maybe someone knows how to fix this.

thank you
Quader
 
Posts: 1
Joined: 2021-10-25 06:42


Return to 1.3.x

Who is online

Users browsing this forum: No registered users and 2 guests