Problem Logging In

[Lorick]

I am hoping to use ThinLinc to connect to a Linux Mint computer that is offsite.

I have run into 2 problems.
1: When I try to login from a Windows PC on the same network as the
Linux Mint PC I get the “Welcome” screen, when I click OK it
terminates my connection.
2: When I try to login from a PC outside the network that the Linux
Mint PC is on I get a “Connection to server timed out” message without
a connection.

I would really appreciate any assistance you could give me on these issues.

Below is my xinit.log:
xauth: file /var/opt/thinlinc/sessions/lorick/10/Xauthority does not exist
tl-xinit: Waiting for Xserver to accept connections…

Xvnc ThinLinc release 4.13.0 build 2253 - built Aug 24 2021 10:46:24
Copyright (C) 1999-2021 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12001000, The X.Org Foundation

(II) Initializing extension VNC-EXTENSION

Wed Oct 6 08:30:13 2021
vncext: VNC extension running!
vncext: Listening for VNC connections on local interface(s), port 5910
vncext: created VNC server for screen 0
(II) Initializing extension Generic Event Extension
(II) Initializing extension SHAPE
(II) Initializing extension MIT-SHM
(II) Initializing extension XInputExtension
(II) Initializing extension XTEST
(II) Initializing extension BIG-REQUESTS
(II) Initializing extension SYNC
(II) Initializing extension XKEYBOARD
(II) Initializing extension XC-MISC
(II) Initializing extension XFIXES
(II) Initializing extension RENDER
(II) Initializing extension RANDR
(II) Initializing extension COMPOSITE
(II) Initializing extension DAMAGE
(II) Initializing extension MIT-SCREEN-SAVER
(II) Initializing extension DOUBLE-BUFFER
(II) Initializing extension RECORD
(II) Initializing extension DPMS
(II) Initializing extension Present
(II) Initializing extension DRI3
(II) Initializing extension X-Resource
(II) Initializing extension XVideo
(II) Initializing extension XVideo-MotionCompensation
(II) Initializing extension GLX
(II) IGLX: Loaded and initialized swrast
(II) GLX: Initialized DRISWRAST GL provider for screen 0
The XKEYBOARD keymap compiler (xkbcomp) reports:

Warning: Unsupported high keycode 372 for name ignored
X11 cannot support keycodes above 255.
This warning only shows for the first high keycode.
Errors from xkbcomp are not fatal to the X server
Connections: accepted: 127.0.0.1::57234
VNCSConnST: closing 127.0.0.1::57234: Clean disconnection
EncodeManager: Framebuffer updates: 0
EncodeManager: Total: 0 rects, 0 pixels
EncodeManager: 0 B (1:-nan ratio)
TcpSocket: unable to get peer name for socket
Connections: closed: ::0
ComparingUpdateTracker: 0 pixels in / 0 pixels out
ComparingUpdateTracker: (1:-nan ratio)
tl-xinit: Xserver ready for clients.
— System information —
ThinLinc 4.13.0
Linux lorick-Satellite-P875 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Linux Mint 20.2 Uma \n \l

No LSB modules are available.
— End system information —
Cannot find xsri. Background image support not available.
Running /opt/thinlinc/etc/xstartup.d/01-tl-kinit.sh (Obtaining Kerberos ticket)
Running /opt/thinlinc/etc/xstartup.d/02-tl-dbus-launch.sh (Starting session D-Bus server)
Existing session D-Bus server found.
Setting initial D-Bus and systemd environment…
Running /opt/thinlinc/etc/xstartup.d/11-tl-set-title (Setting client window title)
Running /opt/thinlinc/etc/xstartup.d/12-tl-default-keyboard (Configuring default keyboard layout)
Setting default keyboard layout to “us”
The XKEYBOARD keymap compiler (xkbcomp) reports:

Warning: Unsupported high keycode 372 for name ignored
X11 cannot support keycodes above 255.
This warning only shows for the first high keycode.
Errors from xkbcomp are not fatal to the X server
Running /opt/thinlinc/etc/xstartup.d/15-tl-shadow-notify (Enabling notifications when the session is shadowed)
Running /opt/thinlinc/etc/xstartup.d/20-tl-select-profile.sh (Choosing a profile)

Wed Oct 6 08:30:28 2021
Connections: accepted: 127.0.0.1::57378
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)
VNCSConnST: Replacing existing connection
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888
Running /opt/thinlinc/etc/xstartup.d/30-tl-xdg-user-dirs (Translating standard folders)
Running /opt/thinlinc/etc/xstartup.d/40-tl-mount-localdrives (Mounting local drives)
Running /opt/thinlinc/etc/xstartup.d/41-tl-lp-redir-launch (Setting up printer port redirection)
Running /opt/thinlinc/etc/xstartup.d/43-tl-pulseaudio-launch.sh (Starting session PulseAudio server)
W: [pulseaudio] main.c: Couldn’t canonicalize binary path, cannot self execute.
Session PulseAudio server started. Redirecting applications…
Running /opt/thinlinc/etc/xstartup.d/50-tl-wait-smartcard (Waiting for smart card connection)
Client has no smartcard capability
Stopping initial window manager…
Done.
Executing profile: cinnamon
Using XDG session: cinnamon
Updating D-Bus and systemd environment…
Executing XDG session command: cinnamon-session-cinnamon
Profile command exited with exit code 0
Running /opt/thinlinc/etc/xlogout.d/tl-kdestroy.sh
Running /opt/thinlinc/etc/xlogout.d/tl-umount-localdrives
tl-xinit: client terminated and returned 0
tl-xinit: Terminating X server…
X I/O error
tl-while-x11: lost Xserver connection, terminating child 6149 …
tl-while-x11: lost Xserver connection, terminating child 6162 …

Wed Oct 6 08:30:33 2021
VNCSConnST: closing 127.0.0.1::57378: Server shutdown
EncodeManager: Framebuffer updates: 134
EncodeManager: Tight:
EncodeManager: Solid: 62 rects, 1.48983 Mpixels
EncodeManager: 992 B (1:6008.12 ratio)
EncodeManager: Bitmap RLE: 30 rects, 10.22 kpixels
EncodeManager: 929 B (1:44.3918 ratio)
EncodeManager: Indexed RLE: 19 rects, 49.804 kpixels
EncodeManager: 5.36523 KiB (1:36.3021 ratio)
EncodeManager: Tight (JPEG):
EncodeManager: Full Colour: 150 rects, 573.74 kpixels
EncodeManager: 367.246 KiB (1:6.10743 ratio)
EncodeManager: Total: 261 rects, 2.12359 Mpixels
EncodeManager: 374.487 KiB (1:22.1592 ratio)
ComparingUpdateTracker: 1.62286 Mpixels in / 712.446 kpixels out
ComparingUpdateTracker: (1:2.27788 ratio)
tl-xinit: X server has terminated
tl-xinit: deleting …/10.1633526866.ended
tl-xinit: Session terminated. Exiting.

[martin]

Hello @Lorick

1. Make sure that the user you are trying to login as with ThinLinc is not already logged in locally on your Mint server. If it is, you’d have to logout that local graphical session first. Many modern Linux distributions does not work well with multiple sessions for same account.

2. I’m missing information about your setup, is this at home? If it is, there are some configuration that has to be made to be able to reach your Mint server if it’s located on the LAN. Port forward has to be setup in your router/firewall and SSH tunnel needs to be created. This has been resolved in other posts on the community, please see

My personal ThinLinc use case and some performance comparison

Hi there! My name is Andre, I’m undergraduate in Mathematics/Teaching, working as a Computer Technician at Universidade de São Paulo - Brazil and I’m here to share my Thinlinc personal use case. Since the start of COVID-19 pandemic in 2020, I have started working from home most of the time. My wife is also working and studying from home and our nephew, who lives here with us, is also taking classes and doing all his homework using our computers. We had only 2 notebooks that we had to share, on…

New user: what ports to open in router?

Hello @Crispin The port you need to open in your router to allow external connections to Thinlinc is port 22 (SSH). Regarding the message " Connection to server:“192.168.1.6” timed out. Check your settings." is due to fact that Thinlinc VSMServer will instruct your Thinlinc client to make a second SSH connection to the ipaddress of your server, which is 192.168.1.6. Your client machine must have some way to directly make a connection to this address, and since it’s an internal address, we can…

Best regards,
Martin

[Lorick]

I added the LOCAL Host information in the registry. I am now able to connect when on the LAN that the Thinlinc server is on. I am still unable to connect to the Thinlinc server from outside the LAN. Connection times out.

[martin]

Hello @Lorick

If I’m not misunderstanding things here, you were already able to connect to your ThinLinc server from LAN in your first post? But got disconnected? Did you verify / test my suggested solution? Im not following what you mean by

I added the LOCAL Host information in the registry.

Regarding not being able to connect from outside, it usually involves setting up port forwarding in your router, and also setting up an SSH tunnel on the client before connecting to ThinLinc, as per mentioned in the other forum posts I provided links for.

Best regards,
Martin

[VirusABC]

Does your Mint machine have a valid IP Address? How would you connect to it using SSH? Can you connect to it using SSH?

If your machine is under NAT and you’re using something like SSH Tunnel to reach your machine, you should configure the HOST_ALIASES parameter on your client computer just like me (and Martin mentioned the topic My personal ThinLinc use case and some performance comparison)

Another option would be to setup split DNS on the network where your machine is located. I think that setting up HOST_ALIASES on your client machine is way easier.