Body
ThinLinc Client Installation
Before you begin: When using a computer off-campus, you may first need to connect to Purdue's Virtual Private Network. Remember, your Purdue Login 2FA (formerly BoilerKey) is REQUIRED to access this service. For VPN, use your Purdue username and add comma-'push' after your password (e.g., password,push).
ThinLinc clients for PC and MacOS are available from: https://www.cendio.com/thinlinc/download
Client install details: https://ploneeng.ecn.purdue.edu/ECN/Support/KB/Docs/ECEThinlinc
ThinLinc stuck session clearing
If your ThinLinc session is stuck, you may use the lab ThinLinc clients or the clients installed from the URL above, and use the "Advanced" tab to choose the option of "Close all sessions before logging off." This option is not available from the web client.
ThinLinc Troubleshooting Guide
-
Use the correct hostname in the client or via the web:
Client:
desktop.ececomp.ecn.purdue.edu
desktop.eceprog.ecn.purdue.edu
Web browser:
https://desktop.ececomp.ecn.purdue.edu
https://desktop.eceprog.ecn.purdue.edu
-
Use the right server for the right task:
ececomp - CentOS 7, for use with software that requires CentOS, like Cadence and Synopsys.
eceprog - Ubuntu 22.04, for programming type classes (AI, ML, etc...)
-
Must be an ECE student or taking an ECE class to use the ECE Thinlinc servers.
-
If the MFA push in Duo is not popping up when trying to login, force close Duo on your mobile device and restart the app. (Power off the device and on again if unsure how to force close an app.)
-
Check which network you are on when connecting to the server. If on campus, make sure you are on PAL or using a wired connection. If off campus, make sure you connect to the Purdue VPN first.
-
When connecting to the VPN, be sure to check DUO for the push notification.
-
While connecting to the Thinlinc server, be sure to check DUO for the push notification by keeping the app open on your phone.
-
When logging into the Thinlinc server via the web or client, be sure to append,push after the password, so DUO will generate a notification to acknowledge the request.
-
If you have or had more than ONE device setup with DUO and push is failing, try ,push2 or ,push3.
Internal Purdue IT Staff notes:
If Purdue IT Staff have to manually kill a session in the absence of the user experiencing the problems, Purdue IT Staff will have to use the second method of manually logging in to each ThinLinc host (ececomp1 through comp4), search for all the users processes, 'ps -u <login name> -f' and if found then killing these off by using 'pkill -u <login name>' and checking again to make sure all stale processes have been removed.
One way of doing this is to run
pkill -9 -u <login>;ps -u <login> -f
until the only job showing is the actual grep
If this does not fix the problem, but users can get past the login screen, then it is most likely a problem with one of the dot files for the GUI. Have them try a different GUI, ie, if they are using BASH, have them try KDE. If that fixes the problems, then remove the dot files for the offending shell and have them try it again.
If all steps above have been done, but users still cannot get past the login screen, then it could be a runaway process; Purdue IT Staff should contact Andy S.