Client-GUI separation
The content on this page was translated automatically.
If port 515 is already in use (under Windows by the "TCP/IP print server" service, under Linux e.g. by lp or cups), the following solutions are possible - these steps, which are quite close to the system, should only be carried out by experienced system administrators.
Change the port used by the QPilot client service:
This should be done in the configuration file gui-service.txt of the client service in the line
xprintserver.client-port=515
. Corresponding changes are then required in the firewall.
This method has not been tested.
If you have configured this successfully, please let us know and we will add it here!- Relocation
of the QPilot client service to another system:
In addition to the problem with the port 515 already in use, another reason for this could be to relieve the local system from spooling the print jobs.General description:
Install the complete package on the system on which the users are working and deactivate the client service.
In the configuration file of the client GUI (gui-config.txt), enter the IP address of the server in the line
guiservice.host=127.0.0.1
instead of the localhost address 127.0.0.1, enter the IP address of the server on which the client service is to run - referred to below as the print server - for example
guiservice.host=141.51.abc.uvw
Copy the directory with the program files to the server and set up the client service as a service there.
This IP must also be entered in the printer queues set up during the installation of the QPilot client.Windows Server 2003:
Prerequisite:
The "TCP/IP print server" service must not be running on the print server, as both "listen" on TCP port 515.
The following steps are necessary:
1. Install the client on the terminal server on which the users are working:
a) Install the client.
b) In order to avoid conflicts with the "TCP/IP print server" service that may be running. running "TCP/IP print server" service, then remove the local QPilot client service:
sc stop QPilot client service
sc delete QPilot client service
c) The IP of the print server must be entered in two places in the client GUI configuration:
- in C:\Program Files\Schomaecker\QPilot-Client\Client-GUI\gui-config.txt behind
guiservice.host=127.0.0.1
instead of 127.0.0.1,
- in one of the "QPilot printer" queues, click on "Configure" in the "Ports" tab, then in the "Printer name or IP address" field - the other queue uses the same "Port".
d) Restart the terminal server.
2. Installing the client service on the print server
a) Stop the "TCP/IP print server" service - if it is present and running - and set it to "Disabled" - on the command line:
sc stop lpdsvc
sc config lpdsvc start= disabled
b) There may be problems installing the client service on a drive other than C:. So on the command line:
C:
mkdir \Programme\Schomaecker\QPilot-Client
Copy the complete "Client-Service" folder (e.g. simply from the installation on the terminal server)
and place it on the print server under C:\Programme\Schomaecker\QPilot-Client.
c) If the spool directory should not be in this directory, the desired directory must be entered in the service-config.txt file after
lprserver.job_dir=jobs
instead of the subfolder "jobs", e.g.:
lprserver.job_dir=E:\spool
d) Install the service:
C:\Program Files\Schomaecker\QPilot-Client\Client-Service\install-service.bat
sc create QPilot-Client-Service binpath= "C:\Programme\Schomaecker\QPilot-Client\Client-Service\QPilot-Client-Service-Service.exe"
Pay attention to the exact path, and there must be a space after "binpath=". Then:
sc description QPilot-Client-Service "QPilot-Client-Service Schomaecker GmbH"
Then set the service to automatic start and then start it:
sc config QPilot-Client-Service start= auto
sc start QPilot-Client-Service
This should install the Follow-Me-Printing function.
3. subsequent uninstallation on the print server is done quickly on the command line:
sc stop QPilot client service
sc delete QPilot client service
Then delete the directory C:\Program Files\Schomaecker\QPilot client.Linux:
Works in the same way as under Windows.