The following description is from a (slightly edited) Mastodon post:
When I prepared a Raspberry Pi with the latest Raspberry Pi OS (based on Debian Bookworm) as a monitoring and observability display, I noticed the “wayvnc” package during the dist-upgrade.
Turns out this is a pre-installed VNC server package – at least on the Desktop variant.
But how can the VNC Server be configured and started and more importantly, how can I connect using a VNC viewer? Figured it out and wrote about it
Link: How to connect to Raspberry Pi Desktop using wayvnc VNC Server (Claudio Kuenzler)
Also see: Virtual Network Computing (VNC) in the Raspberry Pi Documentation
Hey guys, I thought I would share a short guide I made about configuring x11vnc to automatically launch every time the Pi boots up. I had such a hard time getting it to work and thought I should spread the knowledge. I’m a noob with Linux and the Pi, so I thought this would be really beneficial to any other noobs who are trying to get their Pi to run headless. I am using Raspbian Jessie so I’m not sure how well this will work with other distros.
This short guide assumes you already have a VNC viewer and know how to configure it. These instructions outline how to configure your Raspberry Pi to automatically start the x11vnc server every time it is booted. This way, you will be able to remotely connect to your Pi any time you launch your VNC viewer.
Source: Here is a short guide I made on configuring your RPi to automatically run x11vnc server at startup (Reddit/Raspberry Pi)
Although the Raspberry Pi can be connected to a TV or monitor via HDMI or DVI, there are times when running a Raspberry Pi “headless” (without a monitor) is desirable. In a headless setup, you could connect to your Raspberry via SSH but if you want the full desktop then you will need to connect using a remote desktop protocol. The easiest is to setup VNC on Raspberry Pi. Virtual Network Computing (VNC) is a graphical desktop protocol that allows you to access the full Raspberry Pi desktop from another machine. Typically you would run the VNC client on a PC running Windows, OS X or Linux and access the Pi’s desktop over the network.
Full article here:
Setting up VNC on Raspberry Pi (Make Tech Easier)
VNC Starting Automatically on Raspberry Pi (School Pi Club)
Once you have a fully working Raspberry Pi system, it may not be convenient for you to continue to access Raspberry Pi directly via a keyboard and HDMI/TV cable connector dedicated to Raspberry Pi. Instead, you will want to remote control “headless” Raspberry Pi from another computer.
In this tutorial, I will show you how to remote control your Raspberry Pi in several different ways. Here I assume that you are running Raspbian on your Raspberry Pi. Also, note that you are not required to run desktop on Raspbian when trying any of the methods presented in this tutorial.
Actually that last quoted line does not appear to be quite correct — the first three methods shown don’t require a desktop, but the fourth involves using VNC, which pretty much assumes a desktop will be present. And if were were considering using VNC, we might also want to consider Nomachine NX, which can support multiple simultaneous sessions that each have a separate, independent desktop, and is also faster than VNC in some situations. Although, we’ve never tried installing it on a Raspberry Pi.
Also, some or all of these tips may be useful for controlling Linux remotely regardless of the actual hardware that is in use — in other words, these are by no means exclusive to the Raspberry Pi.
Full article here:
How to remote control Raspberry Pi (Xmodulo)
Here is a small walk through of how to install SSH and VNC on Raspberry Pi…
What is SSH? I really did not know the abbreviation until I googled it. It stands for “Secure Shell”. To be brief, with SSH connection between RPI and another computer, you can access the terminal prompt of RPI from the other computer (say your PC). Thus you will be able to execute commands remotely for the RPi from your PC without the need for a keyboard and mouse.
What is VNC? Virtual Network Computer. It is just like team viewer or any other remote desktop stuff, with which you can see your RPi’s desktop on your PCs screen, enabling GUI based access of RPI.
Assuming that you have an SSH enabled RPI, the tutorial follows.
Full article here:
VNC and SSH on Raspberry Pi Without Display (rajvigneshtn.weebly.com)
VNC, SSH and HDMI: Three Options for Viewing Your Raspberry Pi (MakeUseOf)
I think the title above more accurately describes what is shown in this article than the tile they picked. Just good basic information on how to do this:
Connecting via VNC to Raspberry PI from the Google Nexus 7 (Everyday Linux User)
This article includes a small bit of text that originally appeared on a blog called The Michigan Telephone Blog, which was written by a friend before he decided to stop blogging. It is reposted with his permission.
If you have ever tried to access a Linux system using VNC, and your host computer wasn’t particularly fast, you may have noticed that things slow down considerably – you definitely know you’re accessing the computer remotely, even if the access is via a local network link. And even if you don’t have that issue, you might want to know about this alternative.
You can install the NX Free Edition server and client from Nomachine and it works great! Note that NX does not work in precisely the same way as VNC – while VNC lets you take control of the current desktop on the target machine, NX lets each login have its own session and desktop. So you could be using your Linux box and let another family member come into it via NX, and each of you would have your own desktop and session.
The best reasonably current instructions I have found are in this article:
Remote Linux Desktops with NoMachine NX
Those instructions are somewhat geared toward users of Debian-based distributions such a Ubuntu, Linux Mint, etc. but there are also packages available for systems that utilize RPM or compressed TAR packages rather than DEB. Most experienced Linux users should have no problem figuring out how to adjust the instructions for their particular distribution.