How the RFB Protocol Works, From Banner to Pixels
How RFB takes a VNC session from the version banner to pixel rectangles, and which security types, ports and tunnels decide who gets in.
Protocol
Practical guides for running remote desktops, protocol explainers for understanding what happens on the wire, and coverage of the VNC ecosystem.
VNC vs SSH: Shell for Most Jobs, Desktop When You Need One
SSH for shell work, VNC when the job needs a desktop, X11 forwarding for one GUI app, and VNC tunnelled over SSH on any network you don't control.
VNC Port Numbers: 5900 Plus the Display, and How to Check Yours
VNC listens on TCP 5900 for display :0 and 5900 plus N for :N, so :1 is 5901. Check the real listener with ss, then open that port or tunnel it over SSH.
VNC vs VPN: One Gives You a Screen, the Other a Route
VNC gives you one machine's desktop; a VPN gives you a route into a network. Use VNC for GUI work, a VPN for services, and bind VNC to the tunnel address when you need both.
What a VNC server does and how to run one
A VNC server hands a desktop to viewers over RFB on port 5900 plus the display number. Two settings decide which desktop it serves and who can reach it.
VNC vs SPICE: Picking the Console for Your VMs
Pick SPICE for desktop VMs that need audio, USB redirection or a shared clipboard. Pick VNC for everything else, including every VM on RHEL 9 and RHEL 10 hosts.
How Does VNC Work? A Viewer, a Server and One TCP Connection
How VNC works: one TCP connection carries RFB screen updates one way and your input the other, and the listener binding decides whether you connect directly or over SSH.
Join the community to ask a follow-up or share what worked.
Can't find the guide you need? Request it in Feature ideas & feedback.