User Tools

Site Tools


wiki:advanced:multi-node:x2goserver-printing

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:advanced:multi-node:x2goserver-printing [2011/11/12 14:44]
sunweaver [Sites where X2Go Printing does not Make Sense]
wiki:advanced:multi-node:x2goserver-printing [2016/09/23 09:41] (current)
ionic Typo and headling capitalization fixes.
Line 1: Line 1:
 ====== Printing Revisited ====== ====== Printing Revisited ======
  
-===== Sites where X2Go Printing ​does not Make Sense =====+===== Sites Where X2Go Printing ​Does Not Make Sense =====
  
 If all your X2Go servers, X2Go clients and the available network printers are all on the same site (i.e. in the same office) and you neither intend to provide mobile or home office desktop environments,​ then you will __not__ need X2Go printing. ​ If all your X2Go servers, X2Go clients and the available network printers are all on the same site (i.e. in the same office) and you neither intend to provide mobile or home office desktop environments,​ then you will __not__ need X2Go printing. ​
Line 7: Line 7:
 Connect all your office printers directly to the network (IPP, LPD, AppJetDirect printing). Configure your central print server (mostly CUPS, Common Unix Printing System) to print directly to your networked office printers. Also make sure that your office printers are available to users that logon to your X2Go server(s). Connect all your office printers directly to the network (IPP, LPD, AppJetDirect printing). Configure your central print server (mostly CUPS, Common Unix Printing System) to print directly to your networked office printers. Also make sure that your office printers are available to users that logon to your X2Go server(s).
  
-Setting up CUPS printers is not an issue of X2go, please consult the CUPS howtos available on the internet.+Setting up CUPS and CUPS printers is not an explicit X2Go issue, please consult the CUPS howtos available on the internet.
  
 ===== Using X2Go Printing on a Centralized CUPS Server ===== ===== Using X2Go Printing on a Centralized CUPS Server =====
 +
 +<​note>​
 +X2Go Printing is intended for 
 +   * use on low bandwidth networks – like internet connections or GSM connections
 +   * use of printers that are directly connected to X2Go (thin-)clients
 +For other scenarios, please use a central CUPS server (see multi-node printing below) without the X2Go printing feature installed.
 +</​note>​
 +
 +:!: **Before you begin!**
 +> Please make sure that you are familiar with basic X2Go printing setups as described [[doc:​installation:​printing|here]]. Only if you have successfully set up a single-node printing X2Go site go deeper and try out the multi-node setup.
  
 If you would like to run your X2Go server and the CUPS service on different machines (such a scenario is very common if you run more than one X2Go server on your network), you'll have to do things: If you would like to run your X2Go server and the CUPS service on different machines (such a scenario is very common if you run more than one X2Go server on your network), you'll have to do things:
  
-  - generate a pair of SSH keys to faciliate ​communication between ​those two machines +  ​- if running more than one X2Go server: setup up X2Go servers with [[wiki:​advanced:​multi-node:​x2goserver-pgsql|PostgreSQL as X2Go session database backend]] 
-  - add a line to the /​etc/​sudoers file on every X2go server that shall be able to accept print jobs from the central CUPS server+  ​- generate a pair of SSH keys on the CUPS server ​to facilitate ​communication between ​CUPS server and X2Go server(s) 
 +  - add a line to the /​etc/​sudoers file on every X2Go server that enables the X2Go Server (script: ''​x2goprint''​) ​to accept print jobs from the central CUPS server ​(pushed there via SCP) 
 + 
 +Please make sure that you are logged as a user on CUPS and X2Go server(s) that can become the super-user by running the ''​sudo''​ command.
   ​   ​
-Please make sure that you are logged in as user ''​root''​ on the system running the CUPS service and add the following folders:+As first step: install ​the X2Go server printing ​add-on to your (every) X2Go server:
  
 +<​code>​
 +$ sudo aptitude install x2goserver-printing
 +</​code>​
 +  ​
 +Next, install the CUPS X2Go backend on the CUPS server:
 +
 +<​code>​
 +$ sudo aptitude install cups-x2go
 +</​code>​
 +  ​
 +On the CUPS server create ''​root'''​s SSH configuration directory:
 +  ​
 <​code>​ <​code>​
 $ mkdir -p /root/.ssh/ $ mkdir -p /root/.ssh/
 </​code>​ </​code>​
  
-Now you can generate ​the keys (on each X2go server that shall have access ​to the CUPS service):+Now you can generate ​an SSH public/​private key. This key is used to allow passwordless logons from ''​root@cupsserver''​ to ''​x2goprint@x2goserverX''​.
  
 <​code>​ <​code>​
Line 28: Line 53:
 </​code>​ </​code>​
  
-The public part of the key (''/​root/​.ssh/​id_dsa-x2goprint.pub''​) needs to be added to the ''​x2goprint''​ user's ''​authorized_keys''​ file on each of your X2go servers. You can use the ''​ssh-copy-id''​ command for that:+The public part of the key (''/​root/​.ssh/​id_dsa-x2goprint.pub''​) needs to be added to the ''​x2goprint''​ user's ''​authorized_keys''​ file on each of your X2Go servers. You can use the ''​ssh-copy-id''​ command for that:
  
 <​code>​ <​code>​
-root@cupsserver:​~$ ssh-copy-id /​root.ssh/​id_dsa-x2goprint x2goprint@x2goserver1 +root@cupsserver:​~$ ssh-copy-id /​root.ssh/​id_dsa-x2goprint x2goprint@x2goserver1.your.domain 
-root@cupsserver:​~$ ssh-copy-id /​root.ssh/​id_dsa-x2goprint x2goprint@x2goserver2 +root@cupsserver:​~$ ssh-copy-id /​root.ssh/​id_dsa-x2goprint x2goprint@x2goserver2.your.domain 
-etc.+etc.
 </​code>​ </​code>​
  
-Every X2Go server that uses X2Go printing needs to be known by the CUPS server. Regarding your name resolution type, you'll need to add the host names for example to the local /etc/hosts file (your even better: use your local DNS server!!!). Please test if you are able to build up SSH connections from your CUPS server to your X2go servers by entering the following command:+Every X2Go server that uses X2Go printing needs to be known by the CUPS server. Regarding your name resolution type, you'll need to add the host names for example to the local /etc/hosts file (your even better: use your local DNS server!!!). Please test if you are able to build up SSH connections from your CUPS server to your X2Go servers by entering the following command.
  
 <​code>​ <​code>​
-root@cupsserver:​~$ ssh -i  /​root/​.ssh/​id_dsa-x2goprint x2goprint@x2goserver1 +root@cupsserver:​~$ ssh -i  /​root/​.ssh/​id_dsa-x2goprint x2goprint@x2goserver1.your.domain 
-root@cupsserver:​~$ ssh -i  /​root/​.ssh/​id_dsa-x2goprint x2goprint@x2goserver2 +root@cupsserver:​~$ ssh -i  /​root/​.ssh/​id_dsa-x2goprint x2goprint@x2goserver2.your.domain 
-etc.+etc.
 </​code>​ </​code>​
 +
 +If this is your first login from ''​root@x2goserverX.your.domain''​ to ''​x2goprint@x2goserverX.your.domain''​ the SSH command will ask you to accept the host key of the X2Go server(s). Please accept the displayed host keys.
 +
  
 At last, you have to add the following line to your /​etc/​sudoers file. Normally the command ''​visudo''​ is highly recommended for editing the sudoers file, as it performs sanity checks on the sudoers file and reports if you made a mistake while editing the file. At last, you have to add the following line to your /​etc/​sudoers file. Normally the command ''​visudo''​ is highly recommended for editing the sudoers file, as it performs sanity checks on the sudoers file and reports if you made a mistake while editing the file.
wiki/advanced/multi-node/x2goserver-printing.1321109082.txt.gz · Last modified: 2013/03/08 13:31 (external edit)