A page in your DokuWiki was added or changed. Here are the details:
Date : 2017/01/02 15:47
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483371775
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary:
User : stefanbaur
@@ -300,8 +300,45 @@
* create a symlink with the name ''01-AA-BB-CC-DD-EE-FF'' (note the extra
"01-" at the beginning) pointing to x2go-tce-whatever-name-you-chose.
* After that, your ThinClient should boot the X2Go-TCE image.
* Note that it is possible to use partial matching, so a symlink starting with
"01-AA-BB-CC" would match all ThinClients with a MAC address starting with
"AA-BB-CC" and so on.
* For further matching options (IP-based, for example), please consult the
pxeboot documentation. In short, it
should be possible (i.e. untested by us), but it a) requires you to assign static
DHCP IPs and b) you need to translate the IP to its hexadecimal value and use that
value as the symlink name, so e.g. 192.168.0.1 becomes C0A80001 -> x2go-tce.
+
+ ===== Support Tools available in X2Go-TCE =====
+
+ ==== Remote Access to the ThinClient's local display (before any connection is made) ====
+ X2Go-TCE comes with x11vnc installed.
+ If you want to see what's on the ThinClient's X11 screen, before a server
connection has been established, proceed as follows:
+ * On Linux/macOS/Unix:
+ - spawn a VNC listening //client//, like so: ''xvncviewer -listen''
+ - run ''ssh -R 5500:localhost:5500 root@thinclient 'x11vnc -display :0
-rfbport 0 -coe localhost'''
+ * On Windows:
+ - Start a VNC listening //client//, for example ''vncclient.exe -listen
5500''
+ - Start PuTTY, connect to root@thinclient
+ - Select Connections/SSH/Tunnels in PuTTY
+ - Enter Source Port 5500,
Destination localhost:5500, Remote, Auto, and, very important, hit **Add**
//before// you hit **Apply**, or your changes will **not** be saved
+ - run ''x11vnc -display :0 -rfbport 0 -coe localhost'' in the PuTTY window
+ To see what a user is doing once a connection has been established, connect to the X2GoServer yourself and use X2Go's built-in session shadowing (Install package ''x2godesktopsharing'' on the server, if you haven't done so already) - this will deliver way better performance.
+
+ ==== Determining the ThinClient's IP and/or MAC when there is no network connection ====
+
+ When you are unable to connect to the ThinClient, you might want to ascertain its MAC and/or IP address(es), to make sure you and the user you are trying to support are talking about the same machine. Tell the user to press [Ctrl]+[Alt]+[F1] and to read out
+ * the GREEN text if you want to know the MAC address(es)
+ * the RED text if you want to know the IP address(es) - if there is no
red text, it means that the client was unable to acquire a DHCP lease. Check
cabling.
+ To return to the login screen, have the user press [Ctrl]+[Alt]+[F7]
([Alt]+[F7] should work, too), or, once you've successfully logged in over the
network, issue the ''chvt 7'' command.
+
+
+ ==== Checking the ThinClient's local printer setup (when using the ''tcpprint'' boot parameter) ====
+ There are several ways to check whether a ThinClient has detected any local
printers:
+
+ * Assuming you have remote access to the ThinClient, run ''ls -lah /etc/xinetd.d/jetdirect*'' and examine the files listed there.
+ * When connected remotely, you can also look at the messages printed during
the local printer setup phase, by running ''cat /dev/vcs9'' (you might have to
pipe it through ''less'' to see the entire screen).
+ * If you do not have remote access, tell the user to press
[Ctrl]+[Alt]+[F9] and to read out what's on the screen. To return to the login
screen, have the user press
[Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully
logged in over the network, issue the ''chvt 7'' command.
+
+ ==== Checking the ThinClient's update status (when using local storage) ====
+ There are several ways to check a ThinClient's update status:
+
+ * Assuming you have remote access to the ThinClient, look at the messages printed during the update phase, by running ''cat /dev/vcs10'' (you might have to pipe it through ''less'' to see the entire screen) when connected remotely
+ * If you do not have remote access, tell the user to press
[Ctrl]+[Alt]+[F10] and to read out what's on the screen, preferably starting
with the bottom line and continuing upward. To return to the login screen,
have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once
you've successfully logged in over the network, issue the ''chvt 7'' command.
--------------------------------------------------------
===== List of open ToDos/FIXMEs for this
page =====
@@ -604,38 +641,4 @@
* 1150-openssh-readsshprivatekeys or 1150-x2go-readsshprivatekeys would
probably be the proper names
* Maybe it would be better to split the process into 2 scripts, one that
fetches the keys from local storage/USB media, and one that patches the
sessions file
* 2800-x2go-thinclientconfig would also have to be changed so it uses the
keyfile(s) when in broker mode
- FIXME User Support: Remote Access to the ThinClient's local display (before any connection is made)
- X2Go-TCE comes with x11vnc installed.
- If you want to see what's on the ThinClient's X11 screen, before a server
connection has been established, proceed as follows:
- * On Linux/macOS/Unix:
- - spawn a VNC listening //client//, like so: ''xvncviewer -listen''
- - run ''ssh -R 5500:localhost:5500 root@thinclient 'x11vnc -display :0
-rfbport 0 -coe localhost'''
- * On Windows:
- - Start a VNC listening //client//, for example ''vncclient.exe -listen
5500''
-
- Start PuTTY, connect to root@thinclient
- - Select Connections/SSH/Tunnels in PuTTY
- - Enter Source Port 5500, Destination localhost:5500, Remote, Auto, and,
very important, hit **Add** //before// you hit **Apply**, or your changes will
**not** be saved
- - run ''x11vnc -display :0 -rfbport 0 -coe localhost'' in the PuTTY window
- To see what a user is doing once a connection has been established, connect to the X2GoServer yourself and use X2Go's built-in session shadowing (Install package ''x2godesktopsharing'' on the server, if you haven't done so already) - this will deliver way better performance.
-
- FIXME User Support: Determining the ThinClient's IP and/or MAC via phone
-
- When you are unable to connect to the ThinClient, you might want to ascertain its MAC and/or IP address(es), to make sure you and the user you are trying to support are talking about the same machine. Tell the user to press [Ctrl]+[Alt]+[F1] and to read out
- * the GREEN text if you
want to know the MAC address(es)
- * the RED text if you want to know the IP address(es) - if there is no red
text, it means that the client was unable to acquire a DHCP lease. Check
cabling.
- To return to the login screen, have the user press [Ctrl]+[Alt]+[F7]
([Alt]+[F7] should work, too), or, once you've successfully logged in over the
network, issue the ''chvt 7'' command.
-
-
- FIXME User Support: Checking the ThinClient's local printer setup (when using the ''tcpprint'' boot parameter)
- There are several ways to check whether a ThinClient has detected any local
printers:
-
- * Assuming you have remote access to the ThinClient, run ''ls -lah /etc/xinetd.d/jetdirect*'' and examine the files listed there.
- * When connected remotely, you can also look at the messages printed during
the local printer setup phase, by running ''cat /dev/vcs9'' (you might have to
pipe it through ''less'' to see the entire screen).
- * If you do not have remote access, tell the user to
press [Ctrl]+[Alt]+[F9] and to read out what's on the screen. To return to the
login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work,
too), or, once you've successfully logged in over the network, issue the ''chvt
7'' command.
-
- FIXME User Support: Checking the ThinClient's update status (when using local storage)
- There are several ways to check a ThinClient's update status:
-
- * Assuming you have remote access to the ThinClient, look at the messages printed during the update phase, by running ''cat /dev/vcs10'' (you might have to pipe it through ''less'' to see the entire screen) when connected remotely
- * If you do not have remote access, tell the user to press
[Ctrl]+[Alt]+[F10] and to read out what's on the screen, preferably starting
with the bottom line and continuing upward. To return to the login screen,
have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once
you've successfully logged in over the network, issue the
''chvt 7'' command.
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-commits
