[
https://issues.apache.org/jira/browse/GUACAMOLE-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187356#comment-17187356
]
Braihan Cantera commented on GUACAMOLE-1165:
--------------------------------------------
Hi Mike, my inspiration came from this guide:
[https://developer.ibm.com/tutorials/os-multiuserloginsvnc/]
You will find that when you finish doing all configurations from this guide,
you can make different VNC "sessions" going to different ports, which I suppose
is better to allocate sequentially after port 5900 (5901, 5902... up to 5999?)
I agree with you that it is difficult to figure out which ports are in use by
the server, but the sysadmin that would use a XDMCP enabled server should be
aware of that, so in that case we are in the same situation when using
guacamole and when doing VNC manually.
The idea is to emulate making VNC to different ports manually in guacamole.
Hope that I expressed better.
> Allocate VNC port sequentially for XDMCP
> ----------------------------------------
>
> Key: GUACAMOLE-1165
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1165
> Project: Guacamole
> Issue Type: New Feature
> Components: VNC
> Affects Versions: 1.2.0
> Reporter: Braihan Cantera
> Priority: Trivial
>
> In VNC connections, it would be useful to have a "*XDMCP*" toggle option
> which makes when enabled to automatically allocate VNC port to each new
> connection to XDMCP enabled servers so users can have multi sessions over VNC
> to linux servers.
> Example:
> * XDMCP: on
> * User1 connects to server1 via VNC connection, guacamole connects to
> server1:5900
> * User2 connects to server1 via VNC connection, guacamole connects to
> server1:5901
> * User1 and User2 can now use server1 in parallel leveraging XDMCP
> This would provide real multi session "remote desktop" experience to VNC
> connections in guacamole.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)