 | Lars Fosdal on Security alarm provider Woonve… |
 | Thomas Mueller on Question got closed in May 202… |
 | Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
Posted by jpluimers on 2025/08/04
Every now and then you make a typo when accessing remote systems through UltraVNC vncviewer.exe (I did the worst: thinking I had hit Enter to select the most recent connection, but typing a password instead).
I could not find settings in the registry, nor a vncviewer.ini file, so I used Process Monitor and filtered all events for the most recently started vncviewer.exe to figure out where it would store configuration files.
Posted in *nix, *nix-tools, Power User, VNC/Virtual_Network_Computing, Windows, Windows 10, Windows 11, Windows 7, Windows 8, Windows 8.1 | Leave a Comment »
Posted by jpluimers on 2025/06/05
For non-Windows systems, I have used TeamViewer in the past and when they started being obnoxious reverted mostly to VNC derived alternatives. For Windows, I’d usually combined VPN with Remote Desktop.
Recently, I found out that during my first rectum cancer year (and for others, the first COVID-19 year), the development of RustDesk – which can be self-hosted – started as an open source project on [Wayback/Archive] GitHub – rustdesk/rustdesk: An open-source remote desktop application designed for self-hosting, as an alternative to TeamViewer. with their first commit being [Wayback/Archive] Initial commit · wabarc/wayback@650ea87 · GitHub.
I got pointed to this in [Wayback/Archive] Your Remote Desktop SUCKS!! Try this instead (FREE + Open Source) – YouTube.
One of the main things to figure out is how reliably RustDesk does firewall hole punching*.
Another personal interest is to learn more about Rust and Dart, the main programming languages in which RustDesk is written.
Here are some links:
Posted in Development, Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Rust, Screen sharing, Software Development, TeamViewer, VNC/Virtual_Network_Computing, Windows | Tagged: 594 | Leave a Comment »
Posted by jpluimers on 2020/05/08
“Unencrypted connection” “This connection is unencrypted. Would you like to continue?”
When you run realVNC to an x11vnc server, even over an ssh tunneled connection, it will produce errors like the screenshots on the right (from an Android device) and below (from a Mac).
Before I had the realVNC client on the Mac, the Android message totally put me on the wrong foot. I tried searching x11vnc encryption, of which almost all results – especially the Google Search abstracts – will talk about ssh tunneling. So tried to setup the client to use the SSH endpoint, but it refused because it doesn’t talk SSH.
So then I installed a desktop realVNC client (in this case on my Mac) and got this message:
“Unencrypted connection” “The connection to this VNC Server will not be encrypted”
Then it occurred to me that maybe the VNC server itself could do encryption as well and would not need an SSH tunnel after all. And it does even in the first hit:
Posted in *nix, *nix-tools, Power User, Screen sharing, VNC/Virtual_Network_Computing, X11 | Leave a Comment »
Posted by jpluimers on 2020/04/06
I totally missed this the last 5 years. Where have I been (:
[WayBack] xrdp: An open source remote desktop protocol(rdp) server.
It runs on top of either Xvnc (which I have used) or X11rdp and should be usable with any RDP client (like the excellent Microsoft RDP for Mac OS X).
Related
Via:
–jeroen
Posted in *nix, *nix-tools, Power User, Remote Desktop Protocol/MSTSC/Terminal Services, VNC/Virtual_Network_Computing, Windows | Leave a Comment »
Posted by jpluimers on 2019/01/18
Two installation options for TigerVNC:
The [WayBack] TigerVNC viewer gives a bit more details on failing VNC connections than the stock OSX Screen Sharing.app does: after performing the logon, the connection would just stall, but TigerVNC would should “write broken pipe (32)” after the logon. Most of the linked search results indicated the VNC server was having a state problem.
So I restarted the VNC server, after which connections could be made again in both tools.
I actually prefer the stock Screen Sharing.app as:
open vnc://192.168.178.55:5900 if your VNC server is listening on 192.168.178.55:5900TIL that Apple’s “Screen Sharing” app is command-line accessible.
ssh username@hostname -L5910:localhost:5900open
vnc://username:password@localhost:5910
–jeroen
Posted in Apple, Mac OS X / OS X / MacOS, Mac OS X 10.4 Tiger, Mac OS X 10.5 Leopard, Mac OS X 10.6 Snow Leopard, Mac OS X 10.7 Lion, macOS 10.12 Sierra, OS X 10.10 Yosemite, OS X 10.11 El Capitan, OS X 10.8 Mountain Lion, OS X 10.9 Mavericks, Power User, VNC/Virtual_Network_Computing | 2 Comments »
Posted by jpluimers on 2018/12/14
For a keyboard-less Raspberry Pi machine that functions as a read-only screen, I needed:
I already had the E20 ([WayBack] Enlightenment) X11 server running as that’s the first image on [WayBack] HCL:Raspberry Pi3 – openSUSE that as a graphical UI that works.
Posted in *nix, *nix-tools, Power User, Screen sharing, VNC/Virtual_Network_Computing, X11, X11vnc | Leave a Comment »
The Wiert Corner - irregular stream of stuff 