Why Is My User Client Running Slowly?

KB Home   |   Why Is My User Client Running Slowly?

Main.ClientSlow History

Hide minor edits - Show changes to output

September 12, 2017, at 12:33 AM by peterf - Fixed typo
Changed line 52 from:
If you're still having issues, and you're running PaperCut MF, you can reach out to your PaperCut partner or reseller for assistance; their details can be found under the '''Support''' section of the '''About''' tab of the Admin web interface. If you're running PaperCut NG, touch base with the  [[https://www.papercut.com/contact/|PaperCut Support Team]].
to:
If you're still having issues, and you're running PaperCut MF, you can reach out to your PaperCut partner or reseller for assistance; their details can be found under the '''Support''' section of the '''About''' tab in the Admin web interface. If you're running PaperCut NG, touch base with the  [[https://www.papercut.com/contact/|PaperCut Support Team]].
September 12, 2017, at 12:32 AM by peterf - Updated support contact information
Changed line 52 from:
If you are still having issues, please contact the [[https://www.papercut.com/contact/|PaperCut Support Team]].
to:
If you're still having issues, and you're running PaperCut MF, you can reach out to your PaperCut partner or reseller for assistance; their details can be found under the '''Support''' section of the '''About''' tab of the Admin web interface. If you're running PaperCut NG, touch base with the [[https://www.papercut.com/contact/|PaperCut Support Team]].
September 12, 2017, at 12:25 AM by peterf - Revised content, added new section, and mentioned new feature in 17.3
Changed lines 1-4 from:
(:title Why is my User Client running slowly? :)

The PaperCut [[https://www.papercut.com/products/ng/manual/ch-user-client.html|User Client]] could be running slowly for one of the following reasons.  Please take some time to investigate these issues in order:
to:
(:title Why Is My User Client Running Slowly? :)

The PaperCut NG and PaperCut MF [[https://www.papercut.com/products/ng/manual/ch-user-client.html|'''User Client''']] could be behaving slowly for one of the following reasons.  Please take some time to investigate these issues in order:
Changed lines 7-10 from:
The User client software uses the [@server-name@] first to connect to the main PaperCut application server. If that fails, it then tries to connect using the IP address of the server and this process will appear to slow the client.

The [@server-name@] is defined in the client's [@config.properties@] file (located under [@[app-path]/client/[platform]@]). Please try pinging
the DNS server name as defined in the above [@config.properties@] from your workstation. If this takes a long time to resolve, then there's a good chance you've identified the cause of your troubles.
to:
The '''User Client''' software uses the [@server-name@] first when attempting to connect to the primary '''Application Server'''. If that fails, it then tries to connect using the IP address of the server. This process can result in a perceivable delay when the User Client first starts, as the first connection attempt will need to timeout before the second, successful connection attempt can be made.

The
[@server-name@] is defined in the '''User Client's''' [@config.properties@] file, located under [@[app-path]/client/[platform]@] on the primary '''Application Server''' when running the '''User Client''' directly over the network, or under the '''User Client's''' installation directory when it has been deployed locally to a workstation. Try pinging the DNS server name as defined in the above [@config.properties@] from your workstation; if this ping test takes a long time to resolve, then there's a good chance you've identified the cause of your troubles!
Changed lines 13-16 from:
If DNS resolution is slow, you can override the server-name by supplying an IP address instead. Simply replace the [@server-name@] value with your server's IP address.

If you have done a local install of the client, re-install
the client after editing the file on the server and/or update the local copy of the file on the workstation.
to:
If DNS resolution in your environment is successful, but generally slow enough to still result in a delay for the '''User Client''', you can override the [@server-name@] by supplying an IP address instead. Simply replace the [@server-name@] value with your server's IP address, and restart the '''User Clients'''.

If you have a number of local installs of the '''User Client''', it can be much quicker to rollout this changes by simply reinstalling it on each
workstation after editing the [@config.properties@] file on the '''Application Server''', rather than manually updating the local copy of the [@config.properties@] file on all of those workstations.
Changed lines 19-47 from:
PaperCut uses 9192 as the SSL port. The User client software connects from workstation to server.  Please make sure this port is not blocked by firewall or anti-virus software on the server. If the port is blocked or otherwise unresponsive, it might end up slowing the client software. This can be tested by connecting a browser on the workstation to a URL like: [@https://IP-address-of-server:9192/@]

Note: Please note that the PaperCut User Client will initially use TCP 9191 before bootstraping itself to TCP 9192 where required. If you have Options -> Advanced -> Security
-> "Use HTTPS/SSL if available" enabled, the PaperCut User Client will still need to use port 9191 for this bootsrap process. Do not change the PaperCut User Client to use TCP 9192 initially.

'''Important:''' If you have
enabled [[https://www.papercut.com/products/ng/manual/ch-customization-enable-additional-ports.html|TCP 80 (HTTP)]] for the PaperCut Application Server the User Client will attempt to use TCP 443 (HTTPs) for many tasks and will time out before trying TCP 80 (HTTP) again. It is assumed that if you use TCP 80, you also use TCP 443.

!!Local
- cache version

 
When running [@pc-client.exe@] directly off
the share, it needs to load the entire PaperCut User Client off the share across the network before it starts. This might be the reason why it's taking a long time to load up the client software in your network.

The recommended way to run
the client is to use the local cache version using [@pc-client-local-cache.exe@].
This version of
the User Client will keep it self up-to-date by copying itself from the network share to [@C:\Cache\@] and then running from there. The next time it starts, it will quickly check the version on the local hard drive and only copy from the network if it is an old version. This minimises the amount of network traffic greatly and generally speaking, hard drives are quicker than networks which also helps!

Various ways to run the client software are described in
[@README.txt@] file located under [@[app-path]/client@] directory.

!!Wireless?

The cause could be simple as an intermittent network disconnection.  By their very nature, wireless networks are more prone
to disruption than wired alternatives.  It's worth spending some time ensuring your wireless network is stable - although the most direct method of troubleshooting your network is to simply disable wireless connectivity, plug-in a cable, and see if conditions improve.


!!Sometimes size matters

Client pop-ups should typically display within a few seconds of a print job beginning
.
If a client pop-up needs to display job properties (such as the number of pages, or total cost), the corresponding fields could take a few moments
to populate when printing larger files



If you are still having issues, please contact us at support.
to:
PaperCut NG and PaperCut MF use 9192 as the default port for SSL. The '''User Client''' software connects from workstation to server.  Please make sure this port is not blocked by a firewall, or antivirus software on the '''Application Server'''. If the port is blocked or otherwise unresponsive, it might end up slowing the responsiveness of the '''User Client'''. This can be tested by using a web browser on a workstation to load a URL such as the following, where [@[server-name]@] is the hostname or IP address of your '''Application Server''':

[@https://[server
-name]:9192/@]

Please note that
the '''User Client''' will initially use TCP port 9191 before bootstrapping the connection to TCP port 9192 where required. If you have the [@Options->Advanced->Security->Redirect to HTTPS/SSL if available@] option enabled, the '''User Client''' will still need to utilize port 9191 for this bootstrap process. Do not modify the '''User Client''' to use TCP port 9192 for this initial connection.

'''Important:''' If you have enabled [[https://www
.papercut.com/products/ng/manual/common/topics/customize-enable-additional-ports.html|TCP 80 (HTTP)]] for the '''Application Server''', the '''User Client''' will attempt to use TCP port 443 (HTTPS) for many tasks and will timeout before reverting to trying TCP port 80 (HTTP) again. It is assumed that if you use TCP port 80, you also use TCP port 443.

!!Local Cache Deployment

When running
the [@pc-client@] executable directly off the network share, it needs to download the entire '''User Client''' off the share across the network before it can start. This might be the reason why it's taking a long time to load up the software in your network.

The recommended way to run the client for Windows workstations is to use the local cache
version using the [@pc-client-local-cache@] executable. This version of the '''User Client''' will keep itself up-to-date by copying all relevant files from the network share to a directory under [@C:\Cache@] at startup, and then running from there. The next time it starts, it will quickly check the cached version on the local hard drive, compare it to the version available on the '''Application Server''', and only copy the files over the network again if the local copy is older than the latest available. This minimizes the amount of network traffic greatly, and generally speaking, hard drives are much quicker than networks!

Various ways to run the client software are described in the [@README
.txt@] file located under the [@[app-path]/client@] directory.

!!Wireless Networks

The cause could be simple as an intermittent network disconnection.  By their very nature, wireless networks are more prone
to disruption than wired alternativesIt's worth spending some time ensuring your wireless network is stable; although the most direct method of troubleshooting your network is to simply disable wireless connectivity, plug-in a cable, and see if conditions improve.

!!Sometimes Size Matters

'''User Client''' popups should typically display within a few seconds of a print job beginning.
If a popup needs to display job properties, such as the number of pages or total cost, the corresponding fields could take a few moments to populate when printing larger files. 

!!Slow To Wake Up

The '''User Client''' maintains its connection to the '''Application Server''' by periodically "calling in" to it, reconfirming that the session is still active. In the past, if the '''User Client''' was being run from a laptop and the laptop was closed, the '''User Client''' would not take into account that the machine had gone to sleep. When the laptop was subsequently reopened and the '''User Client''' resumed, it would simply assume that no time had passed at all between the machine first going to sleep, and when it was later reawakened. However, if the laptop was asleep for some time, the '''Application Server''' would have independently decided that the session was no longer active, and the connection would be assumed to be severed.

If the '''User Client''' had just called in to the '''Application Server''' to confirm its session immediately prior to the laptop being closed, when it woke back up it would still be under the impression that it had very recently spoken with the '''Application Server''', and that the connection was still active. But the '''Application Server''' would have long since killed the connection, leaving the '''User Client''' session inactive. Because the '''User Client''' would believe that it had very recently checked in with the '''Application Server''', it would then wait for as long as two minutes before checking in again, at which point it would learn that its connection had been closed, and that reconnection would be required, accordingly. The resulting behavior would be that a user may reopen their laptop only to have the '''User Client''' seemingly be unable or unwilling to connect to the '''Application Server''' for a long time; very frustrating, if you're needing to quickly print a document on the go!

As of version 17.3 of PaperCut NG and PaperCut MF, the '''User Client''' will intelligently detect when its host machine has been sent to sleep, and immediately attempt a reconnection to the '''Application Server''' when it is resumed, eliminating this potential delay. If your users are noting this behavior in your environment, ensure that they are running a version of the '''User Client''' at or greater than 17.3.

If you are still having issues, please contact the [[https://www.papercut.com/contact/|PaperCut Support Team]]
.
Added lines 23-24:
'''Important:''' If you have enabled [[https://www.papercut.com/products/ng/manual/ch-customization-enable-additional-ports.html|TCP 80 (HTTP)]] for the PaperCut Application Server the User Client will attempt to use TCP 443 (HTTPs) for many tasks and will time out before trying TCP 80 (HTTP) again. It is assumed that if you use TCP 80, you also use TCP 443.
Added lines 21-22:
Note: Please note that the PaperCut User Client will initially use TCP 9191 before bootstraping itself to TCP 9192 where required. If you have Options -> Advanced -> Security -> "Use HTTPS/SSL if available" enabled, the PaperCut User Client will still need to use port 9191 for this bootsrap process. Do not change the PaperCut User Client to use TCP 9192 initially.
Changed line 50 from:
[-Keywords: delayed, laggy, lag, time out, timeout, trouble loading client, slow loading, loading, FQDN, slow popup, popup client, slow balance window, print client, authentication, login, account selection -]
to:
[-Keywords: delayed, laggy, lag, time out, timeout, trouble loading client, slow loading, loading, FQDN, slow popup, popup client, slow balance window, print client, authentication, login, account selection -]
Changed lines 39-42 from:
If a client pop-up needs to display job properties (such as the number of pages, or total cost), this could take a few moments to process when printing larger files. 


to:
If a client pop-up needs to display job properties (such as the number of pages, or total cost), the corresponding fields could take a few moments to populate when printing larger files. 


Changed lines 33-35 from:
The cause could be simple as an intermittent network disconnection.  By their very nature, wireless networks are more prone to disruption than wired alternatives.  It's worth spending some time ensuring your wireless network is stable - although the most direct method of troubleshooting your network is to simply disable wireless conectivity, plug-in a cable, and see if conditions improve.

to:
The cause could be simple as an intermittent network disconnection.  By their very nature, wireless networks are more prone to disruption than wired alternatives.  It's worth spending some time ensuring your wireless network is stable - although the most direct method of troubleshooting your network is to simply disable wireless connectivity, plug-in a cable, and see if conditions improve.

Added lines 31-35:
!!Wireless?

The cause could be simple as an intermittent network disconnection.  By their very nature, wireless networks are more prone to disruption than wired alternatives.  It's worth spending some time ensuring your wireless network is stable - although the most direct method of troubleshooting your network is to simply disable wireless conectivity, plug-in a cable, and see if conditions improve.

Changed lines 9-10 from:
The [@server-name@] is defined in the client's [@config.properties@] file (located under [@[app-path]/client/[platform]@]). Please try pinging the DNS server name as defined in the above [@config.properties@] from your workstation. If this takes a long time to resolve, then there's a good chance you've identified cause of your troubles.
to:
The [@server-name@] is defined in the client's [@config.properties@] file (located under [@[app-path]/client/[platform]@]). Please try pinging the DNS server name as defined in the above [@config.properties@] from your workstation. If this takes a long time to resolve, then there's a good chance you've identified the cause of your troubles.
Changed lines 9-10 from:
It uses the [@server-name@] field set in the client's [@config.properties@] file (located under [@[app-path]/client/[platform]@]). Please try pinging the DNS server name as defined in the above [@config.properties@] from the workstation, if this takes a long time to resolve the name then it might be the reason for the slow client software.
to:
The [@server-name@] is defined in the client's [@config.properties@] file (located under [@[app-path]/client/[platform]@]). Please try pinging the DNS server name as defined in the above [@config.properties@] from your workstation. If this takes a long time to resolve, then there's a good chance you've identified cause of your troubles.
Changed lines 13-14 from:
If you have problems with DNS resolution, you can override the server-name by using an IP address. If you have done a local install of the client, re-install the client after editing the file on the server and/or update the local copy of the file on the workstation.
to:
If DNS resolution is slow, you can override the server-name by supplying an IP address instead. Simply replace the [@server-name@] value with your server's IP address.

If you have done a local install of the client, re-install the client after editing the file on the server and/or update the local copy of the file on the workstation.
Added lines 29-35:
!!Sometimes size matters

Client pop-ups should typically display within a few seconds of a print job beginning.
If a client pop-up needs to display job properties (such as the number of pages, or total cost), this could take a few moments to process when printing larger files. 


Changed lines 1-4 from:
(:title Why is my User Client running slow? :)

The PaperCut [[https://www.papercut.com/products/ng/manual/ch-user-client.html|User Client]] could be running slow for one of the following reasons.  Please take some time to investigate these issues in order:
to:
(:title Why is my User Client running slowly? :)

The PaperCut [[https://www.papercut.com/products/ng/manual/ch-user-client.html|User Client]] could be running slowly for one of the following reasons.  Please take some time to investigate these issues in order:
Changed line 34 from:
[-Keywords: delayed, laggy, lag, time out, timeout, trouble loading client, slow loading, loading, FQDN, slow popup, popup client, slow balance window, print client, -]
to:
[-Keywords: delayed, laggy, lag, time out, timeout, trouble loading client, slow loading, loading, FQDN, slow popup, popup client, slow balance window, print client, authentication, login, account selection -]
Changed lines 3-4 from:
The [[https://www.papercut.com/products/ng/manual/ch-user-client.html|User Client]] could be running slow for one of the following reasons:
to:
The PaperCut [[https://www.papercut.com/products/ng/manual/ch-user-client.html|User Client]] could be running slow for one of the following reasons.  Please take some time to investigate these issues in order:
Changed lines 3-4 from:
The User Client could be running slow for one of the following reasons:
to:
The [[https://www.papercut.com/products/ng/manual/ch-user-client.html|User Client]] could be running slow for one of the following reasons:
Changed lines 29-30 from:
If you are still having issues, please email us at support@papercut.com.
to:
If you are still having issues, please contact us at support.
Changed lines 17-18 from:
PaperCut uses 9192 as the SSL port. The User client software connects from workstation to server.  Please make sure this port is not blocked by firewall or anti-virus software on the server. If the port is blocked or otherwise unresponsive, it might end up slowing the client software. This can be tested by connecting a browser to this URL - https://IP-Address:9192/.
to:
PaperCut uses 9192 as the SSL port. The User client software connects from workstation to server.  Please make sure this port is not blocked by firewall or anti-virus software on the server. If the port is blocked or otherwise unresponsive, it might end up slowing the client software. This can be tested by connecting a browser on the workstation to a URL like: [@https://IP-address-of-server:9192/@]
Changed lines 17-18 from:
PaperCut uses 9192 as the SSL port. The User client software connects from workstation to server.  Please make sure this port is not blocked by firewall or anti-virus software on the server. If the port is blocked or otherwise unresponsive, it might end up slowing the client software. You can test by connecting a browser to this URL - https://IP-Address:9192/.
to:
PaperCut uses 9192 as the SSL port. The User client software connects from workstation to server.  Please make sure this port is not blocked by firewall or anti-virus software on the server. If the port is blocked or otherwise unresponsive, it might end up slowing the client software. This can be tested by connecting a browser to this URL - https://IP-Address:9192/.
Changed lines 13-14 from:
If you have problems with DNS resolution, you can override the server-name by using an IP address.
to:
If you have problems with DNS resolution, you can override the server-name by using an IP address. If you have done a local install of the client, re-install the client after editing the file on the server and/or update the local copy of the file on the workstation.
Changed lines 17-18 from:
PaperCut uses 9192 as the SSL port. Please make sure this port is not blocked by firewall or anti-virus software. If the port is blocked or otherwise unresponsive, it might end up slowing the client software.
to:
PaperCut uses 9192 as the SSL port. The User client software connects from workstation to server.  Please make sure this port is not blocked by firewall or anti-virus software on the server. If the port is blocked or otherwise unresponsive, it might end up slowing the client software. You can test by connecting a browser to this URL - https://IP-Address:9192/.
Added lines 11-14:
Attach:client-config.properties.jpg

If you have problems with DNS resolution, you can override the server-name by using an IP address.

Changed lines 1-5 from:
(:title Why is my client running slow? :)

The user client could be running slow for one of the following reasons:

to:
(:title Why is my User Client running slow? :)

The User Client could be running slow for one of the following reasons:
Changed lines 7-8 from:
User client software uses first the server name to connect to the main PaperCut application server. if that fails it tries to connect using the IP address of the server and this process will slow the client. It uses the "server-name" field set in the client's "config.properties" file (located under [app-path]/client/[platform]). Ping the PaperCut server name from the workstation, if it takes a long time to resolve the name then it might be the reason for the slow client software.
to:
The User client software uses the [@server-name@] first to connect to the main PaperCut application server. If that fails, it then tries to connect using the IP address of the server and this process will appear to slow the client.

It uses the [@server-name@] field set in the client's [@config.properties@] file (located under [@[app-path]/client/[platform]@]). Please try pinging the DNS server name as defined in the above [@config.properties@] from the workstation, if this takes a long time to resolve the name then it might be the reason for the slow client software.
Changed lines 13-14 from:
PaperCut uses 9192 as the SSL port. Please make sure this port is not blocked by firewall or anti-virus software. If the port is blocked, it might end up slowing the client software.
to:
PaperCut uses 9192 as the SSL port. Please make sure this port is not blocked by firewall or anti-virus software. If the port is blocked or otherwise unresponsive, it might end up slowing the client software.
Changed lines 18-26 from:
When running "pc-client.exe" off the share, it needs to load everything off the share across the network before it starts. This might be the reason why it's taking a long time to load up the client software in your network.
The recommended way to run the client is to use the local cache version using pc-client-local-
cache.exe.
When it first starts for
the first time it copies the files to the local drive and after that it uses the local copy. This helps in minimizing the network traffic as well as helps to start the client quicker.

Various ways to run the client software are described in @@README.txt@@ file located under @@[app-path]/client@@ directory
.


If you are still having issues,
email us at support@papercut.com.
to:
When running [@pc-client.exe@] directly off the share, it needs to load the entire PaperCut User Client off the share across the network before it starts. This might be the reason why it's taking a long time to load up the client software in your network.

The recommended way to run the client is to use the local
cache version using [@pc-client-local-cache.exe@].
This version of
the User Client will keep it self up-to-date by copying itself from the network share to [@C:\Cache\@] and then running from there. The next time it starts, it will quickly check the version on the local hard drive and only copy from the network if it is an old version. This minimises the amount of network traffic greatly and generally speaking, hard drives are quicker than networks which also helps!

Various ways to run the client software are described in [@README.txt@] file located under [@[app-path]/client@] directory.

If you are still having issues, please
email us at support@papercut.com.
Changed line 30 from:
[-Keywords: -]
to:
[-Keywords: delayed, laggy, lag, time out, timeout, trouble loading client, slow loading, loading, FQDN, slow popup, popup client, slow balance window, print client, -]
Changed lines 8-9 from:
User client software uses first the server name to connect to the main PaperCut application server. if that fails it tries to connect using the IP address of the server and this process will slow the client. It uses the "server-name" field set in the client's "config.properties" file (located under [app-path]/client/platform). Ping the PaperCut server name from the workstation, if it takes a long time to resolve the name then it might be the reason for the slow client software.
to:
User client software uses first the server name to connect to the main PaperCut application server. if that fails it tries to connect using the IP address of the server and this process will slow the client. It uses the "server-name" field set in the client's "config.properties" file (located under [app-path]/client/[platform]). Ping the PaperCut server name from the workstation, if it takes a long time to resolve the name then it might be the reason for the slow client software.
Changed lines 14-15 from:
!!Local-cache version
to:
!!Local - cache version
Changed lines 3-5 from:
The user client could be running slow for a few reasons. They are given below:

to:
The user client could be running slow for one of the following reasons:

Changed lines 8-9 from:
User client software uses the server name to connect to the main PaperCut application server. Try to ping the PaperCut server name from the workstation, if it takes a long time to resolve the name then it might be the reason for the slow client software.  It uses the "server-name" field set in the client's "config.properties" file. PaperCut first tries to connect using the server name field, if that fails it tries to connect using the IP address of the server and this process will slow the client.
to:
User client software uses first the server name to connect to the main PaperCut application server. if that fails it tries to connect using the IP address of the server and this process will slow the client. It uses the "server-name" field set in the client's "config.properties" file (located under [app-path]/client/platform). Ping the PaperCut server name from the workstation, if it takes a long time to resolve the name then it might be the reason for the slow client software.
Changed line 18 from:
The recommended way to run the client is to use the local cache version. (pc-client-local-cache.exe)
to:
The recommended way to run the client is to use the local cache version using pc-client-local-cache.exe.
Changed lines 8-9 from:
 User client software uses the server name to connect to the main PaperCut application server. Try to ping the PaperCut server name from the workstation, if it takes a long time to resolve the name then it might be the reason for the slow client software.  It uses the "server-name" field set in the client's "config.properties" file. PaperCut first tries to connect using the server name field, if that fails it tries to connect using the IP address of the server and this process will slow the client.
to:
User client software uses the server name to connect to the main PaperCut application server. Try to ping the PaperCut server name from the workstation, if it takes a long time to resolve the name then it might be the reason for the slow client software.  It uses the "server-name" field set in the client's "config.properties" file. PaperCut first tries to connect using the server name field, if that fails it tries to connect using the IP address of the server and this process will slow the client.
Changed lines 1-5 from:
(:title Why is my client slow? :)

The user client can be slow for a few reasons. Few main reasons are given below: .

to:
(:title Why is my client running slow? :)

The user client could be running slow for a few reasons. They are given below:

Changed lines 8-9 from:
Try to ping the PaperCut server name, if it takes a long time to resolve the name then it might be the reason for the slow client software. User client software uses the server name to connect to the main PaperCut application server.  It uses the "server-name" field set in the client's "config.properties" file. PaperCut first tries to connect using the server name field, if that fails it tries to connect using the IP address of the server and this process will slow the client.
to:
 User client software uses the server name to connect to the main PaperCut application server. Try to ping the PaperCut server name from the workstation, if it takes a long time to resolve the name then it might be the reason for the slow client software.  It uses the "server-name" field set in the client's "config.properties" file. PaperCut first tries to connect using the server name field, if that fails it tries to connect using the IP address of the server and this process will slow the client.
October 28, 2011, at 02:42 AM by 202.129.124.120 -
Changed lines 21-25 from:
Various ways to run the client software are described in @@README.txt@@ file located under @@[app-path]/client@@ directory


TODO link your page here: https://www
.papercut.com/kb/Main/Miscellaneous
to:
Various ways to run the client software are described in @@README.txt@@ file located under @@[app-path]/client@@ directory.


If you are still having issues, email us at support@papercut
.com.
October 28, 2011, at 02:42 AM by 202.129.124.120 -
Changed lines 6-9 from:
!!DNS settings.

User client software uses the
server name to connect to the main PaperCut application server.  It uses the "server-name" field set in the client's "config.properties" file. PaperCut first tries to connect using the server name field, if that fails it tries to connect using the IP address of the server and this process will slow the client. See if you can ping the PaperCut server name, if it takes a long time to resolve the name then it might be the reason for the slow client software.
to:
!!DNS settings

Try to ping the PaperCut
server name, if it takes a long time to resolve the name then it might be the reason for the slow client software. User client software uses the server name to connect to the main PaperCut application server.  It uses the "server-name" field set in the client's "config.properties" file. PaperCut first tries to connect using the server name field, if that fails it tries to connect using the IP address of the server and this process will slow the client.
October 28, 2011, at 12:07 AM by 202.129.124.120 -
Changed lines 3-5 from:
The user client can be slow for a variety of reasons. Few main reasons for it being slow are: .

to:
The user client can be slow for a few reasons. Few main reasons are given below: .

Changed lines 8-9 from:
To connect to the PaperCut server, client first uses the server name. If it fails to connect using the server name then it tries to connect using the IP address of the server. It uses the "server-name" field set in the client's "config.properties" file. See if you can ping the PaperCut server name, if it takes a long time to resolve the name it will slow up the client software.
to:
User client software uses the server name to connect to the main PaperCut application server.  It uses the "server-name" field set in the client's "config.properties" file. PaperCut first tries to connect using the server name field, if that fails it tries to connect using the IP address of the server and this process will slow the client. See if you can ping the PaperCut server name, if it takes a long time to resolve the name then it might be the reason for the slow client software.
Changed lines 12-15 from:
PaperCut uses 9192 as the SSL port. Please make sure this port is not blocked by firewall or anti-virus software.

!!Local
cache
to:
PaperCut uses 9192 as the SSL port. Please make sure this port is not blocked by firewall or anti-virus software. If the port is blocked, it might end up slowing the client software.

!!Local-
cache version
Changed lines 19-21 from:
When it first starts for the first time it copies the files to the local drive and after that it uses the local copy. This helps in minimizing the network traffic as well as helps to start the client quicker. Moreover, it ensures the client software is automatically updated in conjunction with server updates.

to:
When it first starts for the first time it copies the files to the local drive and after that it uses the local copy. This helps in minimizing the network traffic as well as helps to start the client quicker.

Various ways to run
the client software are described in @@README.txt@@ file located under @@[app-path]/client@@ directory

October 27, 2011, at 11:48 PM by 202.129.124.120 -
October 27, 2011, at 11:48 PM by 202.129.124.120 -
Changed line 27 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: -]
October 27, 2011, at 11:45 PM by 202.129.124.120 -
Added lines 1-27:
(:title Why is my client slow? :)

The user client can be slow for a variety of reasons. Few main reasons for it being slow are: .


!!DNS settings.

To connect to the PaperCut server, client first uses the server name. If it fails to connect using the server name then it tries to connect using the IP address of the server. It uses the "server-name" field set in the client's "config.properties" file. See if you can ping the PaperCut server name, if it takes a long time to resolve the name it will slow up the client software.

!!SSL Port

PaperCut uses 9192 as the SSL port. Please make sure this port is not blocked by firewall or anti-virus software.

!!Local cache

 
When running "pc-client.exe" off the share, it needs to load everything off the share across the network before it starts. This might be the reason why it's taking a long time to load up the client software in your network.
The recommended way to run the client is to use the local cache version. (pc-client-local-cache.exe)
When it first starts for the first time it copies the files to the local drive and after that it uses the local copy. This helps in minimizing the network traffic as well as helps to start the client quicker. Moreover, it ensures the client software is automatically updated in conjunction with server updates.


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

----
''Categories:''[[Category.Troubleshooting|+]], [[Category.UserClientTool|+]]
----
[-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 September 12, 2017, at 12:33 AM
Printable View   |   Article History   |   Edit Article