From: noemail@please.net   
      
   On Sun, 23 Oct 2022 17:48:23 -0000 (UTC), Harold Johanssen wrote:   
      
   > On Sat, 22 Oct 2022 16:39:11 -0000 (UTC), Rich wrote:   
   >   
   >> Harold Johanssen  wrote:   
   >>> On Sat, 22 Oct 2022 14:59:23 -0000 (UTC), Harold Johanssen wrote:   
   >>>   
   >>>   
   >>>>       Thanks. I am confused about something here thoug: when I said   
   >>>> above that I can vncviewer into A from B, the ports involved in A are   
   > (I   
   >>>> believe) 5900 and above - in my case, 5901, I think. Are you saying   
   >>>> that, besides this, the X server (TigerVNC, in my case) must be   
   >>>> listening on port 6000 as well for what I am trying to do to succeed?   
   >>>   
   >>>        Actually, that may well be the problem. In B, which is running   
   > Xorg,   
   >>> I get the following (among other stuff irrelevant to our purposes):   
   >>>   
   >>> # ss -nlt State   Recv-Q   Send-Q     Local Address:Port      Peer   
   >>> Address:Port   
   > Process   
   >>> LISTEN  0        32               0.0.0.0:5900   
   > 0.0.0.0:*   
   >>> LISTEN  0        4096             0.0.0.0:6000   
   > 0.0.0.0:*   
   >>> LISTEN  0        32                  [::]:5900   
   > [::]:*   
   >>> LISTEN  0        4096                [::]:6000   
   > [::]:*   
   >>>   
   >>> whereas in A, which is running TigerVNC, this is what I have:   
   >>>   
   >>> State   Recv-Q  Send-Q      Local Address:Port      Peer Address:Port   
   > Process   
   >>> LISTEN  0       5                 0.0.0.0:5901   
   > 0.0.0.0:*   
   >>> LISTEN  0       5                    [::]:5901   
   > [::]:*   
   >>>   
   >>>        Nothing seems to be listening on port 6000.   
   >>   
   >> Then you have found the cause.  TigerVNC is not listening for raw xlib   
   >> TCP connections.  It is only listening for vnc connections.   
   >>   
   >> So, next question, does TigerVNC document an option to cause it to   
   >> listen for raw xlib connections (TCP 6000)?   
   >   
   > 	Apparently not. The documentation does not say anything about it,   
   > but, then again, it seems to be rather terse and incomplete. The Tiger   
   > VNC forum proved to be a bit of a fiasco, with people giving advice that   
   > seems to reveal that they know even less than I do about the subject.   
   >   
   > 	Anybody aware of some other VNC framework supported under 15.0?   
      
   	In case somebody is interested, I got some useful feedback from   
   the TigerVNC in the end. It turns out to be the case that one can build   
   TigerVNC with support to listen on port 6000 - it just so happens that   
   this is disable by default, and the relevant configuration option to   
   enable it is not used in the tigervnc.SlackBuild file found in the extra/   
   source/tigervnc directory shipped with 15.0.   
      
   	I edited this file to add the --enable-listen-tcp option to the   
   big configure invocation in the second half of tigervnc.SlackBuild, and   
   after rebuilding, removing the currently installed version of TigerVNC,   
   and installing the one built as above, the resulting vncserver does   
   listen on port 6000, and I can do what motivated me to post my original   
   question.   
      
   	As an aside, my feeling is that it would have been better to have   
   this built-in and disabled by default, while providing the capability to   
   enable it when launching vncserver.   
      
   	Well, at least it works.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)