In all 1.3.9 was a code error in winvnc.exe
1) running as administrator was not dedected -> service fail
2) temp folder was inproper set: saving settings in program files failed
Both are fixed and are posisble the cause of all strange behaviours.
Certificat updated, now valid till 2025
Download
https://www.uvnc.eu/download/1390/UltraVNC_139_dev4.zip
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
UltraVNC 1.3.9-dev4 - Download links
- Rudi De Vos
- Admin & Developer
- Posts: 6839
- Joined: 2004-04-23 10:21
- Contact:
Re: 1.3.9 dev 4
still no luck to successful connect
1. when i connect to user now after about 15-20 seconds on my computer i have prompt to enter domain user and password (in version 1.3.8.1 windows to enter domain user and password was appear immediate - we are on the same network)
2. after i entering my credentials which are definitely correct it`s show authentication reject so for strange reason it does not accept my password
3. on second computer no query appears at all but this is probably ok because my password is considered as incorrect
i think from logs that long waiting and reject authentication is associated with wrong path ? m_ms_logon set to trueC:\Users\rudi\Desktop\
i enable logs on client computer so maybe it will help you but strange is that in logs i don't have client path but C:\Users\rudi\Desktop\
![Embarassed :oops:](./images/smilies/_icon_redface.gif)
1. when i connect to user now after about 15-20 seconds on my computer i have prompt to enter domain user and password (in version 1.3.8.1 windows to enter domain user and password was appear immediate - we are on the same network)
2. after i entering my credentials which are definitely correct it`s show authentication reject so for strange reason it does not accept my password
3. on second computer no query appears at all but this is probably ok because my password is considered as incorrect
i think from logs that long waiting and reject authentication is associated with wrong path ? m_ms_logon set to trueC:\Users\rudi\Desktop\
i enable logs on client computer so maybe it will help you but strange is that in logs i don't have client path but C:\Users\rudi\Desktop\
Mon Sep 26 12:00:54 2022
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : WinVNCAPPMain-----Application started
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : server created ok
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : OpenInputdesktop OK
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : SelectHDESK to Default (2a8) from c4
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : Username SYSTEM
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncmenu.cpp : vncmenu(server)
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : SockConnect 0
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : SockConnect 1
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : trying port number 5900
Mon Sep 26 12:00:56 2022
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vsocket.cpp : closing socket
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : SockConnect Done 1
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : SockConnect 1
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : SockConnect 1
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncsockconnect.cpp : started socket connection thread
Mon Sep 26 12:01:21 2022
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncmenu.cpp : vncMenu::Shutdown: Close menu - Disconnect all - Shutdown server
--Nieprawidłowe dojście.
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\HideDesktop.cpp : Restorewallpaper 0
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncmenu.cpp : Reset 0
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncmenu.cpp : vncMenu WM_CLOSE call - All cleanup done
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncmenu.cpp : quitting from WM_DESTROY
--Nieokreślony błąd.
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : KillAuthClients() done
--Nieprawidłowe dojście okna.
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncmenu.cpp : vncmenu killed
--Nieprawidłowe dojście okna.
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\HideDesktop.cpp : Restorewallpaper 0
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncmenu.cpp : Reset 0
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : ################## Closing Imp Thread
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : ################## SHUTING DOWN SERVER ####################
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : shutting down server object2
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vsocket.cpp : shutdown socket
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vsocket.cpp : closing socket
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncsockconnect.cpp : quitting socket connection thread
--Operacja blokująca została przerwana przez wywołanie funkcji WSACancelBlockingCall.
Mon Sep 26 12:01:23 2022
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vsocket.cpp : closing socket
--Nie można nawiązać połączenia, ponieważ komputer docelowy aktywnie go odmawia.
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : KillAuthClients() done
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : KillUnauthClients() done
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : ShutdownServer m_pDSMPlugin = NULL
Mon Sep 26 12:01:36 2022
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : WinVNCAPPMain-----Application started
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : server created ok
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : OpenInputdesktop OK
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : SelectHDESK to Default (2a4) from c4
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\winvnc.cpp : Username SYSTEM
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncmenu.cpp : vncmenu(server)
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : SockConnect 0
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : SockConnect 1
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : trying port number 5900
Mon Sep 26 12:01:38 2022
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vsocket.cpp : closing socket
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : SockConnect Done 1
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : SockConnect 1
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : SockConnect 1
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncsockconnect.cpp : started socket connection thread
Mon Sep 26 12:01:52 2022
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncsockconnect.cpp : accepted connection from 192.168.5.43
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : AddClient() started
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncclient.cpp : vncClient() executing...
Mon Sep 26 12:01:57 2022
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : AddClient() done
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncclient.cpp : client connected : 192.168.5.43 (1)
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncclient.cpp : DSMPlugin Pointer to socket OK
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncclient.cpp : Send protocolMsg
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncclient.cpp : Send_OK
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncclient.cpp : m_ms_logon set to trueC:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncclient.cpp : negotiated version
Entered InitAuthenticate
Mon Sep 26 12:02:02 2022
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : client 192.168.5.43 verifiedHost 0 prior to adjustment
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : client 192.168.5.43 verifiedHost 1 after adjustment
Mon Sep 26 12:02:14 2022
After DH: g=856964393, m=1692488153, i=548541292, key=1460788376
Mon Sep 26 12:02:16 2022
CheckUserGroupPasswordUni result=0
--Nie można utworzyć pliku, który już istnieje.
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncclient.cpp : authentication failed
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : removing unauthorised client
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncserver.cpp : RemoveClient() done
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncclient.cpp : ~vncClient() executing...
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncmenu.cpp : Reset 0
--Nieprawidłowe dojście.
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vncclient.cpp : deleting socket
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\vsocket.cpp : closing socket
Mon Sep 26 12:02:18 2022
C:\Users\rudi\Desktop\git_ultravnc\winvnc\winvnc\HideDesktop.cpp : Restorewallpaper 0
Re: 1.3.9 dev 4
I just did some tests.
Edit: Perhaps some issues are related to the SecureVNCPlugin64.dsm Plugin as I see many crashes regarding this module reported in event log.
- I could not run it as service. Winvnc.exe processes (2x) are running but no tray icon shown. Therefore no possibility to initiate cloud connect.
- Running as service does actually work (despite the missing tray icon). But due to the missing icon I could not open the cloud connect dialog. Also running "winvnc.exe -cloudserver cloud.uvnc.com" did not open any dialog while the service was running.
- Manual run (non-service) is working. Tray icon allowing to open cloud connect dialog.
- Connection from my client did work but it's not really clear what "red", "yellow" and "green" status is and also not clear if it is still trying to connect or in what state it is. Some status bar info would be handy.
- Server-Side catalog improvement suggestion: Move "start" button below server name as usually you would work your way from top to bottom. e.g. entering server hostname and then click start to see the ID displayed.
- connection message from client was not displayed or shown in notification.
Edit: Perhaps some issues are related to the SecureVNCPlugin64.dsm Plugin as I see many crashes regarding this module reported in event log.
- Rudi De Vos
- Admin & Developer
- Posts: 6839
- Joined: 2004-04-23 10:21
- Contact:
Re: 1.3.9 dev 4
No icon: found and fixed
red: server not found ( connect server)
yellow: connect to connect server
green: connect to connect server and viewer/server with same id is also conncted
Normal a permanent https connection is needed to keep the connections in sync, now we just know when viewer/server connect but it take way to long before the server can detect it's gone.
The whole cloud is work in progress
Thanks for the feedback and suggestions
red: server not found ( connect server)
yellow: connect to connect server
green: connect to connect server and viewer/server with same id is also conncted
Normal a permanent https connection is needed to keep the connections in sync, now we just know when viewer/server connect but it take way to long before the server can detect it's gone.
The whole cloud is work in progress
Thanks for the feedback and suggestions
- Rudi De Vos
- Admin & Developer
- Posts: 6839
- Joined: 2004-04-23 10:21
- Contact:
Re: 1.3.9 dev 4
Seems only loopback was working.
Some mistake in the settings manager
Some mistake in the settings manager