GNU/Linux Desktop Survival Guide by Graham Williams
Desktop Survival Project Home Preface Advocacy History Distributions Installing GNU/Linux Basic Survival Wajig Applications AI, Machine Learning, Data Science Android - GNU/Linux Devices Audio Backup Booting CD Chinese ChRoot Clock Command Line Databases DIA Directories Disks EcoSysL Emacs Email Evolution Files File Systems Firewalls Floppy Disks FreedomBox Glade GNOME Graphics, Images, Photos Hardware Initialisations on Booting Installation Examples Internet IOT Java KDE Kernels Keyboard Konqueror KVM Switch LATEX Log System Login Magellan MATE Mathematics Memory Modems Mounting Devices MS/Windows Music MySQL Nautilus Networks Nextcloud Network File System NFS NT File System Oracle Packages Partitions Passwords PDF Power Management PPP Presentations Printing Python R Remote Desktops Rsync Samba Scanning Science Screens Security Spreadsheet SSH Swap Teradata Data Warehouse Themes TV Unity USB Version Control Video Virtualization Voice over IP WebCam WordPress Web Sites Word Processing and Printing X XML Troubleshooting Index

CLICK HERE TO VISIT THE UPDATED SURVIVAL GUIDE

Cannot Connect to Server

If we get an error indicating that we can not connect to the server, then the likely cause is that the server is behind a firewall that is not allowing connections to the VNC port. This is most likely the case for home based systems with a modem/router. We can modify the router settings to redirect the port connection to the specific host. For example, one router (a Belkin) was configured locally as IP 10.1.1.1 (but had a different ISP provided IP address that was used on the Internet to connect to it) and the computer was configured on the local network with an IP address of 10.1.1.2. The router was configured to redirect requests to connect to port 5900 to 10.1.1.2. Once the router was rebooted the connections via VNC worked just fine.