From: rich@example.invalid   
      
   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)?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)