Multiple Site locations and the PaperCut Client

KB Home   |   Multiple Site locations and the PaperCut Client

Main.MultipleSiteUserClient History

Hide minor edits - Show changes to output

Changed line 12 from:
to:
 
Changed lines 6-7 from:
This solution is recommended and is great for people who work on more than two PaperCut implemented sites that require the PaperCut User Client. By having DNS redirect for a specific name, you can have @@PAPERCUT-SERVER@@ in the config.properties file that will connect on all sites. On each site, the network administrator would set a redirection when users access @@PAPERCUT-SERVER@@, where it would redirect to their local PaperCut server such as @@PAPERCUT-SERVER-MEL@@.
to:
This solution is recommended and is great for people who work on more than two PaperCut implemented sites that require the PaperCut User Client. By having DNS redirect for a specific name, you can have @@PAPERCUT-SERVER@@ in the config.properties file that will connect on all sites. On each site, the network administrator would set a redirection when users access @@PAPERCUT-SERVER@@, where it would redirect to their local PaperCut server such as @@PAPERCUT-SERVER-MEL@@.

This will require that your DNS Search Suffix is in a working state. This means that @@PAPERCUT-SERVER@@ resolves to a Fully-Qualified-Domain-Name on both sites, e.g. @@PAPERCUT-SERVER.SCHOOL.EDU@@ is a CNAME to @@APP-`SERVER01.SCHOOL.EDU@@ on site 1, @@PAPERCUT-SERVER.COLLEGE.EDU@@ is a CNAME to @@PRINTER.SCHOOL.EDU@@ on site 2.

July 29, 2014, at 12:19 AM by 203.222.91.204 -
Changed lines 19-20 from:
We're essentially giving the PaperCut client two sets of information to check. The one downside to this is that if DNS were ever unavailable on the @@PSERVER@@ site, we will not be able to connect to that server directly. We recommend using the above DNS redirection recommendation.
to:
We're essentially giving the PaperCut client two sets of information to check. The one downside to this is that if DNS were ever unavailable on the @@PSERVER@@ site, we will not be able to connect to that server directly. We recommend using the above DNS redirection steps.
July 29, 2014, at 12:19 AM by 203.222.91.204 -
Changed lines 19-20 from:
We're essentially giving the PaperCut client two sets of information to check. The one downside to this is that if DNS were ever unavailable on the @@PSERVER@@ site, we will not be able to connect to that server directly. We recommend using the below DNS redirection recommendation.
to:
We're essentially giving the PaperCut client two sets of information to check. The one downside to this is that if DNS were ever unavailable on the @@PSERVER@@ site, we will not be able to connect to that server directly. We recommend using the above DNS redirection recommendation.
Changed lines 3-4 from:
PaperCut support is seeing more and more requests around the ability for people to move around multiple PaperCut implemented sites without having to install multiple User Clients. There are a few ways around this which we will explain here.
to:
PaperCut support is seeing more and more requests around the ability for people to move around multiple PaperCut implemented sites without having to install multiple User Clients. There are a few ways you can configure the PaperCut Client to connect to multiple sites, which is described here.
Changed lines 1-2 from:
(:title Multiple Sites and the PaperCut Client:)
to:
(:title Multiple Site locations and the PaperCut Client:)
Added lines 5-7:
!!DNS Redirections
This solution is recommended and is great for people who work on more than two PaperCut implemented sites that require the PaperCut User Client. By having DNS redirect for a specific name, you can have @@PAPERCUT-SERVER@@ in the config.properties file that will connect on all sites. On each site, the network administrator would set a redirection when users access @@PAPERCUT-SERVER@@, where it would redirect to their local PaperCut server such as @@PAPERCUT-SERVER-MEL@@.

Changed lines 9-16 from:
We've seen people also configure the @@config.properties@@ file to connect to either DNS or IP address. An example would be:

Site 1 has a PaperCut server name of "SERVER1" and an IP address of "10.1.1.1"
Site 2 has a PaperCut
server name of "PSERVER" and an IP address of "126.2.2.1"

The @@config.properties@@ file would be configured as below
:
@@server-ip=10.1.1.1@@
@@server-port=9191@@
to:
We've seen people also configure the ''config.properties'' file to connect to either DNS or IP address - whichever is available onsite. The reason this can be done is because we check the @@server-name@@ before the @@server-ip@@. If DNS is not available, we will use the server's IP address as an alternative. An example would be:

Site 1 has a PaperCut server name of @@SERVER1@@ and an IP address of @@10.1.1.1@@ \\
Site 2 has a PaperCut server name of @@PSERVER@@ and an IP address of @@126.2.2.1@@

The ''config.properties'' file would be configured as below: \\
@@server-ip=10.1.1.1@@ \\
@@server-port=9191@@ \\
Changed lines 19-38 from:
We're essentially giving the PaperCut client two sets of information to check. The one downside to this is that if DNS were ever unavailable on the PSERVER site, we will not be able to connect to that server directly. We recommend using the below DNS redirection recommendation.

!!DNS Redirections
This solution is recommended for people who work on more than two PaperCut implemented sites that require the PaperCut User Client. By having DNS redirect for a specific name, you can have "PAPERCUT-SERVER" in the config.properties file that will connect on all sites. On each site, the network administrator would set a redirection when users access "PAPERCUT-SERVER", where it would redirect to their local PaperCut server.

An example would be a user on site A accesses http://papercut-server:9191/client. The DNS redirection would then redirect the user to the locally named server, being http://papercut-server-mel:9191/client










!!Subheading

TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous

to:
We're essentially giving the PaperCut client two sets of information to check. The one downside to this is that if DNS were ever unavailable on the @@PSERVER@@ site, we will not be able to connect to that server directly. We recommend using the below DNS redirection recommendation.
Changed line 22 from:
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
to:
''Categories:'' [[Category.TipsAndTricks|+]], [[Category.UserClientTool|+]]
Changed line 24 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: multi-site, reflector-]
Added lines 1-39:
(:title Multiple Sites and the PaperCut Client:)

PaperCut support is seeing more and more requests around the ability for people to move around multiple PaperCut implemented sites without having to install multiple User Clients. There are a few ways around this which we will explain here.

!!Configuring two sites in config.properties
We've seen people also configure the @@config.properties@@ file to connect to either DNS or IP address. An example would be:

Site 1 has a PaperCut server name of "SERVER1" and an IP address of "10.1.1.1"
Site 2 has a PaperCut server name of "PSERVER" and an IP address of "126.2.2.1"

The @@config.properties@@ file would be configured as below:
@@server-ip=10.1.1.1@@
@@server-port=9191@@
@@server-name=PSERVER@@

We're essentially giving the PaperCut client two sets of information to check. The one downside to this is that if DNS were ever unavailable on the PSERVER site, we will not be able to connect to that server directly. We recommend using the below DNS redirection recommendation.

!!DNS Redirections
This solution is recommended for people who work on more than two PaperCut implemented sites that require the PaperCut User Client. By having DNS redirect for a specific name, you can have "PAPERCUT-SERVER" in the config.properties file that will connect on all sites. On each site, the network administrator would set a redirection when users access "PAPERCUT-SERVER", where it would redirect to their local PaperCut server.

An example would be a user on site A accesses http://papercut-server:9191/client. The DNS redirection would then redirect the user to the locally named server, being http://papercut-server-mel:9191/client










!!Subheading

TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous

----
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
----
[-Keywords: TODO keywords here if needed-]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on December 04, 2014, at 11:10 PM
Printable View   |   Article History   |   Edit Article