Differences

This shows you the differences between two versions of the page.

--- unix:linux:debian:terminalserver [2024/07/22 23:20] – rodolico
+++ unix:linux:debian:terminalserver [2024/07/23 00:59] (current) – rodolico
@@ Line 16: / Line 16: @@
 Install lightdm, xinetd and tigervnc server (may already be installed)
-<code bash>apt install lightdm xinetd tigervnc-standalone-server</code>
+<code bash>apt install lightdm xinetd tigervnc-standalone-server  tigervnc-viewer
+</code>
+During install, it will ask which to use, slim or lightdm. Choose lightdm.
+Also, tigervnc-viewer is not required, but I use it a lot on my terminal servers.
 ==== Configure lightdm and xinetd ====
-Edit the file **/etc/lightdm/lightdm.conf**, setting the following values to enable the XDMCP Server
+Edit the file **/etc/lightdm/lightdm.conf**, setting the following values to enable the XDMCP Server. This entails just removing the leading pound signs from the existing conf and changing //false// to //true//
 <code>
 [XDMCPServer]
@@ Line 55: / Line 60: @@
 </code>
-===== Restart =====
+You can create as many of these stanzas as you like. The main thing is making sure each //service// name is unique, and the port associated is also. Feel free to change //server_args// to match your default, but if you are using the tightvnc viewer to make the connection, you can modify the connection at will.
-service xinetd restart
+Also, I start my ports at some weird number. VNC defaults to 5900, but I'm making the base 5950 in this example. That all but guarantees I will not conflict if I'm using port forwarding on the workstation to get someplace else.
-or
+===== Restart =====
-just reboot the whole machine. Less time and you won't miss anything.
+I'm sure there is some set of steps I can go through to reset slim to lightdm, and I know you can tell xinetd to reset with <code bash>service xinetd reload</code>, but I'm lazy and just reboot the whole machine. Less time and you won't miss anything.
 ===== Test =====
+Make a connection with the command <code bash>vncviewer 192.168.1.1:5950</code>, where 192.168.1.1 is changed to the IP of your server (or the DNS name). Assuming tigervnc is your viewer, you can copy/paste between your workstation and the terminal server, etc...
+===== Going from here =====
+Add users to the terminal server the normal way (adduser as root), then modify /etc/xinetd.d/vnc, adding a new stanza with a new port and service name, then telling the user to use that.
+Also, note that the parameters I documented here are not anywhere near the full range of parameters the server accepts. See [[https://tigervnc.org/doc/Xvnc.html]] for a detailed list of available options, plus a section on how to integrate with inet.d (which I modified to use with xinet.d). The documentation is excellent, albeit a little technical.
+Remember, this is just one way of doing it. You can vary what I've done here by not using the stanza's the way I did, or you can go whole hog and use the real [[https://ltsp.org/|Linux Terminal Service Project]] which will give your users their own copy of a virtual server every time they log in.
+Have fun!