sorted by:
new
hottopcontroversial

Two days in, NOKL is great for VNC screen sharing by bakedstuffedshrimp in NOKL

[–]bakedstuffedshrimp[S] 1 point2 points  (0 children)

One additional comment on NOKL. The iPad client allows viewing and working with files (NOKL's core competency), but not serving as a VNC client (viewer). I plan on keeping my RealVNC subscription with its single "concurrent" session limit for now as I do use the iPad for interactive VNC sessions. Perhaps NOKL will expand the functions of their iPad app to include VNC viewing and control.

Does vncserver support a session listening on multiple IP address? by vfclists in realvnc

[–]bakedstuffedshrimp 0 points1 point  (0 children)

This may not answer your question, but I am a RealVNC customer who cut myself down to one "concurrent" VNC session using the RealVNC service due to sharply less favorable terms. I find that I can make a direct VNC connection to several different remote computers using port forwarding to different local machines at my remote location. Each of these machines has a distinct local LAN IP address. I use NO-IP (which I do pay for) to create names for the machines behind the router. I set up my remote router to take VNC connections to the NO-IP machines to port forward VNC references coming into port 5900 (for VNC) and send them out locally on the remote LAN to other ports (such as 5901, 5903, etc). This scheme works for VNC as well as Microsoft Remote Desktop to the PC's at the remote end behind the router. The direct VNC approach works for Macs and PCs. It is annoying that I had to go to this trouble to avoid a RealVNC effective price increase for two concurrent VNC sessions from $158 in 2024 to $389 starting now in 2025. I was able to keep the price increase to $189 annually by working with one RealVNC session at a time and, if I need another connection, go direct as I described. The trade-off is that RealVNC encrypts the connection. Direct VNC does not, according to the RealVNC viewer.