Small papercut client issue

[WanderingWolf]

Firstly, sorry if this should be in a different area. Just wondering if anyone else has this issue with Papercut, we have it where it runs the pc client at login and runs it directly off our print server, we've not installed it on every machine. Every so often, there's not really a pattern that I can see, the client just stops working, so when you cursor over it in the system tray it disappears. Just wondering if anyone else has had this issue or know of a way of fixing it, short of installing the PC client on every machine. Many thanks in advance :-)

[clareq]

We had it happen on laptops that had lost the wireless connection. We've found the only stable way to make it work is to install the client agent.

[Grey-gear]

We have found that to, what we have done is have a shortcut to the papercut client that is in the startup folder, so if it does not run the users can just click on the desktop icon to make it run. hope that helps. Edited May 2, 2013 by Grey-gear

[Big_Ted]

try running the local cache version - actually i would always suggest to run that version over the other choices

[SovietRussia]

We run it off our print server over the network and it seems to work fine, no issues like you have explained.

 

We are running Version 13 and we run it as a batch script to just start the program at Login

[gds64]

Assuming that you're running the latest version, I'd check that the server IP address is listed in the config.properties file which is located in the same folder as the client executable on the server. You could also enable client logging through the same file, to check what's actually going on.

[Yeo695]

Can't say that I've had that issue but Ive spent hours trying to get hole punching to work through papercut.

But if I had to guess I would agree with gds64

 

Assuming that you're running the latest version, I'd check that the server IP address is listed in the config.properties file which is located in the same folder as the client executable on the server. You could also enable client logging through the same file, to check what's actually going on.

 

Start there.

[Edu-IT]

Ive spent hours trying to get hole punching to work through papercut.

What?!

 

I'd also check config.properties as others have pointed out. We set both values in there to the IP address of the PaperCut server to reduce the need for DNS lookups.

[WanderingWolf]

Thanks all, I will look into some of these and see what I can find out...I'm starting to wonder if it's got something to do with actually how we've got it starting up (We have RES Workspace Manager).