Connecting to a VNC Server
VNC Viewer 4 can therefore be configure to only ever use the original VNC protocol version 3.3, ensuring compatibility even with non-standard VNC Servers. Note that this option may be set as a Default Option, or when making a new connection, but cannot be changed once a connection is active.
If installed by the WinVNC setup package then VNC Viewer isaccessible from the Start Menu.
If downloaded directly, the VNC Viewer can be run either bydouble-clicking on the program icon, or from the command-line.
- Download versions of VNC® Enterprise Edition. This is not our current website. Get the latest VNC software.
- Licensing Terms. There are two licensing options available for TightVNC software:. GNU General Public License version 2 (often abbreviated as GNU GPL). This is the default licensing option. It's completely free but it does not allow integration with closed-source products. Read the complete text of the license here (opens in a new window).
The VNC Viewer will present the Connection Details dialog,allowing the IP address or name of the target VNC Server to bespecified.
If the VNC server's Display Number is non-zero then the displaynumber can be specified by adding a colon to the server's IP address orname, followed by the display number:
If the VNC server is using a non-standard port number to acceptconnections then this is specified by adding two colons to theserver's address or name, followed by the port number:
Once you have selected the VNC server to connect to, you cansimply click Ok or press return to attempt to connect to it. If yourconnection attempt succeeds then the server's details will be added tothe Connection Details drop-down menu, to save you typing next time.
Alternatively, you can select the Options... button, to overridethe default connection configuration, before you connect. See the VNCViewer for Windows Options documentation for more details.
Package Details: realvnc-vnc-viewer 6.21.406-1
Package Actions
- View PKGBUILD / View Changes
| Git Clone URL: | https://aur.archlinux.org/realvnc-vnc-viewer.git (read-only, click to copy) |
|---|---|
| Package Base: | realvnc-vnc-viewer |
| Description: | VNC remote desktop client software by RealVNC |
| Upstream URL: | https://www.realvnc.com/ |
| Keywords: | |
| Licenses: | custom |
| Conflicts: | tigervnc, tightvnc, turbovnc |
| Submitter: | ava1ar |
| Maintainer: | ava1ar (Kewl) |
| Last Packager: | Kewl |
| Votes: | 43 |
| Popularity: | 2.37 |
| First Submitted: | 2017-09-11 23:40 |
| Last Updated: | 2021-05-20 19:26 |
Required by (0)
- https://www.realvnc.com/download/file/viewer.files/VNC-Viewer-6.21.406-Linux-ARM.deb(armv7h)
- https://www.realvnc.com/download/file/viewer.files/VNC-Viewer-6.21.406-Linux-x64.deb(x86_64)
- https://www.realvnc.com/download/file/viewer.files/VNC-Viewer-6.21.406-Linux-x86.deb(i686)
BenTheTechGuy commented on 2021-02-18 22:13
aarch64 can be added as an architecture since RealVNC now has a build that is available in the raspbian-arm64 repos.http://archive.raspberrypi.org/debian/pool/main/r/realvnc-vnc/realvnc-vnc-viewer_6.20.530.42683_arm64.deb
Edit: Due to versioning and upstream conflicts I made my own package.
Kewl commented on 2020-12-17 22:38
@jose1711 binary name is an upstream choice, then this seems like a good idea you can submit to tightvncviewer and/or realvnc. If they are ok with it it's fine, if it's too complicated or causes issues from their point of view it would be good to know. Also if you have examples of official packages changing binary names, I will follow the best practices from TUs.
jose1711 commented on 2020-12-17 21:45
hi, thanks for packaging. could you please consider removing conflicts array b/c the only reason i want to keep realvnc is raspberry pi, but otherwise i am quite happy with tightvncviewer.
the idea is to rename binary in order to avoid conflict:
thank you, j
emmanuelux commented on 2020-02-08 13:57
miss sha1sums_armv7h=('95bc648180924cb7b2105378a3ce7b2c41030e29')
emmanuelux commented on 2020-02-08 11:05
can you add for armv7h :arch=('x86_64' 'i686' 'armv7h')source_armv7h=('https://www.realvnc.com/download/file/viewer.files/VNC-Viewer-${pkgver}-Linux-ARM.deb')sha1sums_armv7h=('95bc648180924cb7b2105378a3ce7b2c41030e29')
tested and working (there is a standalone version too but better this one for icon and launch)
Kewl commented on 2019-08-14 20:15
The binary is not compiled from the source code but extracted from the .deb package provided for Linux installing (Ubuntu 16.04 LTS, 18.04 LTS).
Realvnc Viewer Logs
mb720 commented on 2019-08-14 10:58
Thanks for packaging this! After looking at RealVNC's website and this repo's PKGBUILD, I'm still not sure this VNC viewer is open source.
RealVNC hosts GPL-licensed source code for its Unix server and client here (they call it 'VNC Open Source Code'): https://archive.realvnc.com/download/open/
Is the .deb package offered in this AUR repository compiled from that source code?
Realvnc Viewer Free
Kewl commented on 2018-03-29 19:29
totalsecond commented on 2018-01-14 11:54
6.17.1113 PKGBUILD https://gist.github.com/totalsecond/dd03d4345d92561b39a78882f777f83e
Kewl commented on 2018-01-13 15:55
Realvnc Viewer Portable
@ava1ar: I am happy to push the pkgbuild update if you allow me for co maintenance.