Skip to content

Maintain the Windows VNC server again #1213

@baptx

Description

@baptx

The GitHub project description says "High performance, multi-platform VNC client and server" but the README file says:

WARNING: winvnc is currently unmaintainted and and may not function correctly.
winvnc may not work if the Fast User Switching or Remote Desktop features are in use.

Is there any plan to support the TigerVNC Windows server again or we should use other software like TightVNC? If it is no longer supported, it would not be a multi-platform VNC server anymore and the GitHub description should be changed to avoid confusion.

I use Linux but I think a Windows VNC server can be useful to help a Windows user remotely from a Linux computer, as an open-source alternative to proprietary software like TeamViewer. I think the built-in RDP remote desktop feature on Windows can only work over the Internet when using a VPN or configuring the router of the person that wants to share their screen.
With a VNC server like TightVNC, this is not needed when using the reverse VNC feature "Attach Listening Viewer" as long as the VNC client has a public IP address, for example by configuring the router used for the VNC client or with a dedicated server / Virtual Private Server using SSH remote port forwarding. I also used local port forwarding with PuTTY on Windows to make VNC more secure and connect through the localhost SSH tunnel instead of the public IP address directly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requestedwinvncThis is only relevant for WinVNC

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions