[
https://issues.apache.org/jira/browse/GUACAMOLE-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187387#comment-17187387
]
Nick Couchman commented on GUACAMOLE-1165:
------------------------------------------
{quote}
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?)
{quote}
In reading through that page, i do *not* believe that they are suggesting that
your VNC server arbitrarily allocates ports 5900+ to various VNC connections
(=users). In my experience, the purpose of xinetd is to allow multiple end
users to make simultaneous connections to the same port ("multiplexing", if you
like), and xinetd manages those connections. So, what the IBM page is really
suggesting is that you enable XDMCP on your display manager, then create a
xinetd configuration for VNC on port 5900 (or greater), and have VNC query
XDMCP. xinetd should handle multiple sessions coming in, not by incrementing
the VNC port, but simply by multiplexing the incoming connections.
When the page says:
{quote}
VNC uses ports numbered 5900 and up. You can run the server with different
options on different ports. If you do so, you should assign each instance its
own port number.
{quote}
It does not mean that each user connecting to the XDMCP server gets their own
port; rather, it means that if you'd like to change options like screen
resolution, color depth, or even what type of VNC login you're getting (XDMCP,
etc.), you can set up various xinetd services on different ports for these
differing configurations.
Or, when it says:
{quote}
If you’ve configured multiple VNC sessions on different ports, you can specify
the VNC session number by passing it as part of the hostname, as in:
{quote}
It is not saying that your XDMCP server is allocating various ports, it's
saying, as above, that you've configured (for example) port 5900 with a screen
resolution of 1024x768 while 5901 has 1280x1024, 5902 has 1920x1080, and 5903
has a resolution of 1280x800. Presumably all of these could be pointing to
query XDMCP locally.
> 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)
