Learn Remote Desktop - Clipboard, File Transfer & Peripherals

#Introduction

So far you've learned to create a VNC server, connect with a viewer, and manage services. Episode 11 raises a side that's often underestimated but hugely affects productivity: comfort. Copying and pasting text between machines, sending files, and making sure the keyboard and mouse work correctly are what separate an enjoyable remote session from a frustrating one.

This episode covers four things: VNC clipboard sharing, limitations in view-only connections, file transfer via TightVNC or scp/rsync, and peripheral settings such as keyboard layout (XKB), mouse acceleration, and multi-monitor support.

#VNC Clipboard Sharing

#How the VNC Clipboard Works

The RFB protocol has an extension for sharing the clipboard: when you copy text on one side, the viewer sends the clipboard contents to the server, and vice versa. On the Linux server side, a process called vncconfig bridges the X11 clipboard with the VNC clipboard.

On many setups, vncconfig needs to be run explicitly inside the session. Add it to ~/.vnc/xstartup before launching the desktop environment:

vncconfig -nowin &

The vncconfig -nowin & command runs vncconfig without a window and connects X11 text selections with the VNC clipboard. Without this process, copy-paste between machines often doesn't work.

#Testing the Clipboard

The fastest way to verify: copy text on the client, then paste it on the server. If it doesn't work, check in this order:

• Is vncconfig running in the server session? Check with pgrep vncconfig.
• Does the viewer have the clipboard option enabled? In TigerVNC, this option is on by default.
• Is the connection in view-only mode? The clipboard can be restricted on the server side.

pgrep -a vncconfig

#View-Only Limitations

#Clipboard and Input in View-Only Mode

When a connection is granted view-only rights, the viewer can only see the screen without sending input. In x11vnc, this limitation can be combined with clipboard restrictions: the server uses a separate password for view-only connections and can disable clipboard delivery for those connections.

x11vnc -display :0 -rfbauth /etc/x11vnc.pass -viewpasswd /etc/x11vnc-view.pass

The x11vnc -display :0 -rfbauth /etc/x11vnc.pass -viewpasswd /etc/x11vnc-view.pass command creates two connection classes: the main password grants full control, the second password only views the screen. The security details of view-only will be covered more deeply in episode 12.

#File Transfer

#TightVNC File Transfer on Windows

In episode 9 you already met the file transfer feature of the TightVNC Viewer Windows. This feature copies files through the TightVNC protocol extension without opening a separate connection:

toolbar  ->  Transfer files  ->  pick file  ->  send to remote

Its limitations are clear: this feature is only available between TightVNC components and doesn't handle large directories well. For more serious work, you need a more capable transfer path.

#Alternatives: scp and rsync

For Linux servers, the most reliable way to send files is over SSH — the same path used for tunnels in episode 14. scp for a one-off transfer, rsync for repeated synchronization:

scp laporan.pdf arman@192.168.1.20:/home/arman/
rsync -av --progress /home/arman/proyek/ arman@192.168.1.20:/home/arman/proyek/

The scp laporan.pdf arman@192.168.1.20:/home/arman/ command sends a single file with full encryption, while rsync -av --progress copies a directory and only sends the parts that changed. Both are far safer than VNC transfer because the data goes through SSH.

#Peripheral Settings

#Keyboard Layout (XKB)

Keyboard layout differences between countries are the most common source of errors in remote sessions. If keys don't produce the right characters, set the layout inside the session with XKB:

setxkbmap -layout de
setxkbmap -layout us -variant dvorak

The setxkbmap -layout de command switches the X11 session's keyboard layout to German. Make sure the viewer sets the same layout too, because key events are sent as keycodes that get re-interpreted on the server side.

#Mouse Acceleration and Sensitivity

A mouse that feels slow or jumpy can be fixed from the server side with xset. Acceleration and threshold options:

xset m 1.5 3

xset m 1.5 3 sets pointer acceleration to 1.5 with a threshold of 3 pixels. Tune these values to taste; on slow WAN connections, lower acceleration often feels more precise.

#Multi-Monitor Support

Multi-monitor support in VNC depends on both the viewer and the server. On TigerVNC 1.16 and later, the viewer on Windows can choose which monitor to display when connecting to a host with multiple displays:

viewer  ->  Display settings  ->  choose monitor 1 / 2 / all

For a Linux server with virtual displays, you still set one large resolution per session via -geometry — for example 1920x1080 for a single monitor. Splitting displays per monitor is more naturally done by running several VNC sessions (episode 7).

#Conclusion

Episode 11 touched on remote session comfort: enabling clipboard sharing with vncconfig -nowin, understanding view-only limitations, choosing the right file transfer method between TightVNC and scp/rsync, and setting up keyboard, mouse, and multi-monitor.

Key takeaways:

• vncconfig -nowin bridges the X11 clipboard with the VNC clipboard.
• View-only connections restrict input and clipboard from the server side.
• TightVNC file transfer is only for single files on Windows.
• scp and rsync are safer and more reliable for transfers to Linux.
• setxkbmap sets the keyboard layout; xset m sets mouse acceleration.
• Multi-monitor is supported by the TigerVNC 1.16+ viewer on Windows.

In the next episode, episode 12, we move into basic VNC security — the 8-character password limitation, view-only passwords, access restrictions with -localhost, and firewall configuration that only allows specific client IPs. Get your server ready, because we're starting to lock it down!