Jump to content

jasonatpapercut

Members
  • Posts

    14
  • Joined

Reputation

45 Excellent

About jasonatpapercut

Personal Information

  • Location
    Australia
  1. Hi PetBen, PaperCutter here. When deploying a Server based Print Queue with Print Deploy the username/password input to the Print Deploy client does not interfere with the SMB/CIFS/UNC authentication to the server. That is to say, the OS logged in user needs to be able to open \\print1.sls.local\Global Queue. If you're using PaperCut Mobility Print, thats a different matter as we control the authentication stack there. In situations where authentication doesn't/can't work, we do suggest to look at installing PaperCut Mobility Print on the print server and using Print Deploy to push out those queues.
  2. Hey all, another PaperCutter here. This one is strange. At a technical level, the PaperCut User Client uses a lightweight XMLRPC over HTTP (and HTTPS) to communicate with the PaperCut Application Server. The hostname/IP address is configured via the config.properties file. Specifically these three values: server-name=printserver.company.lan server-ip=10.0.0.39 server-port=9191 Something to note here. We have both a server-name and server-ip. The PaperCut User Client will attempt communicate on the server-name where possible, and fall back to the server-ip. You can enable debugging in the PaperCut User Client as described here: https://www.papercut.com/kb/Main/HowToEnableDebugInTheUserClient You'll see something like this for a working server-name: 2020-12-15 10:47:03,171 DEBUG UserClientDispatcher:39 - Creating server connection: 10.0.0.39:9191, timeout: 90s [main] 2020-12-15 10:47:03,406 DEBUG ServerConnection:730 - Client's list of IP addresses is: 10.0.0.61,fe80:0:0:0:2477:fc8:6b35:1857%wlan0. Previously: [main] 2020-12-15 10:47:03,410 DEBUG ServerConnection:139 - Attempting to connect using server's name: http://printserver.company.lan:9191/rpc/clients/xmlrpc [main] 2020-12-15 10:47:03,412 DEBUG ServerConnection:269 - Pinging server [main] 2020-12-15 10:47:03,412 DEBUG ServerConnection:1005 - Calling method: client.ping (parameters suppressed) [main] 2020-12-15 10:47:03,432 DEBUG ServerConnection:1010 - Call to method: client.ping took 20 ms. Result: true [main] 2020-12-15 10:47:03,432 DEBUG ServerConnection:743 - Requesting global config data from server [main] 2020-12-15 10:47:03,432 DEBUG ServerConnection:1005 - Calling method: client.getGlobalConfig (parameters suppressed) [main] When the server-name doesn't work.. you get something like this.. (I've removed some of the log entries and replaced it with -snip-). 2020-12-15 10:49:27,342 DEBUG UserClientDispatcher:39 - Creating server connection: 10.0.0.39:9191, timeout: 90s [main] 2020-12-15 10:49:27,602 DEBUG ServerConnection:730 - Client's list of IP addresses is: 10.0.0.61,fe80:0:0:0:2477:fc8:6b35:1857%wlan0. Previously: [main] 2020-12-15 10:49:27,607 DEBUG ServerConnection:139 - Attempting to connect using server's name: http://printservertypo.company.lan:9191/rpc/clients/xmlrpc [main] 2020-12-15 10:49:27,608 DEBUG ServerConnection:269 - Pinging server [main] 2020-12-15 10:49:27,609 DEBUG ServerConnection:1005 - Calling method: client.ping (parameters suppressed) [main] 2020-12-15 10:49:27,821 DEBUG ServerConnection:143 - Failed to connect to server using server name. Problem communicating with server: printservertypo.company.lan [main] biz.papercut.pcng.client.uit.ServerConnection$ServerConnectionException: Problem communicating with server: printservertypo.company.lan -snip- Caused by: java.net.UnknownHostException: printservertypo.company.lan -snip- ... 4 more 2020-12-15 10:49:27,822 DEBUG ServerConnection:152 - Attempting to connect using server's IP: http://10.0.0.39:9191/rpc/clients/xmlrpc [main] 2020-12-15 10:49:27,823 DEBUG ServerConnection:269 - Pinging server [main]2020-12-15 10:49:27,823 DEBUG ServerConnection:1005 - Calling method: client.ping (parameters suppressed) [main] As you can see, DNS resolution has failed, and it's falling back to using the IP address. If it still fails to connect, you'll see something like this: 2020-12-15 10:50:09,841 DEBUG ServerConnection:156 - Failed to connect to server using ip address. Problem communicating with server: Connection timed out: connect [main] biz.papercut.pcng.client.uit.ServerConnection$ServerConnectionException: Problem communicating with server: Connection timed out: connect -snip- Caused by: java.net.ConnectException: Connection timed out: connect at java.base/java.net.PlainSocketImpl.waitForConnect(Native Method) Or something similar. So.. Whats happening in this exact case? I don't know :-) What I'd suggest doing is enabling debug and then peering at the logs. One thing I will say... We rely on DNS at the operating system working correctly. If the PaperCut User Client requests a hostname->IP lookup, which the OS has cached a bad NXDOMAIN response or has a stale A/AAAA record, then that will be transparent to us. Maybe configuring tighter a TTL on that record could help? Another possibility is with the stale A/AAAA record pointing to an IP that is no longer available on the new access point due to firewall rules or similar? Something that just occurred to me, if server-name is just a hostname, e.g. printserver, then you're not only relying on DNS working, you're relying on search suffixes working (and being in the correct order) and possibly even falling back to NETBIOS/WINS (!) on Windows, and Bonjour/ZeroConf/mDNS on macOS which can be very unreliable. Best to ensure you're using a FQDN there. Edit: Ok. Line endings are hard. I've tried to re-format.
  3. Hey Jobos, PaperCutter here. There are two primary products that PaperCut puts out. PaperCut NG - Tracks printing, has account selections, filters, restrictions etc. If you can print to it, we can track it. PaperCut MF - Tracks printing, has account selections, filters, restrictions etc. It also has copy/scan/fax tracking on copiers and is available through copier vendors and our large reseller network. Speak to your current vendor, they may already be able to supply PaperCut MF. To do "cost codes" on the copiers, you'd have two main ways to do this. 1 - Setup your users into Groups or use the "Department" field in Active Directory and just report on their usage. 2 - Setup "Shared Accounts". These often mirror KLAs such as English, Science, Maths or Junior, Middle, Senior schools. When they print or login they are prompted for a cost centre/KLA/shared account to charge to. This is especially useful for multi-disciplinary staff, e.g. Science/Maths. Reach out to us directly if you have more questions, we have in-time-zone contact details here: https://www.papercut.com/contact/
  4. Hi Fiza, Jason here from PaperCut. Were you able to resolve this with iTS support? Definitely sounds like a config issue somewhere, and best to walk through your configuration with a support person.
  5. Hey MatthewL, PaperCutter here. Advanced Printer Scripting can probably do this: https://www.papercut.com/support/resources/manuals/ng-mf/common/topics/script.html Something like this? function printJobHook(inputs, actions) { if (inputs.job.documentName != "Super Secret") { actions.job.cancelAndLog('Unauthorised Print job.'); actions.log.debug('Job from user "' + inputs.user.username + '" was canceled.'); } } ​
  6. Are memes allowed? Can I meme here? I'm going to meme here. Glad we could help.
  7. Poking our support teams about this.. There's one known incidence of this. Do you use Canon drivers? We have a KB article here: https://www.papercut.com/kb/Main/MobilityPrintCanonSystemUsername#overview Contents are roughly: If so, try: "Canon Driver properties -> Device Settings -> Spooling at Host" to "Disabled" With regards to: When using Print Deploy to deploy a Mobility Queue, you can deploy the native driver instead: https://www.papercut.com/support/resources/manuals/print-deploy/set-up-print-deploy/topics/computers-not-joined-to-local-domain.html Basically, setup a Mobility queue on your reference machine, change the driver at the OS level, then clone the queue. Thats what will be used on the client machines. Users should have access to all of the finishing features that way.
  8. Hey JamboD, If Print Deploy is trying to setup a print queue that points to a print server, e.g. Windows Client to Windows Server and the queue is like \\print-server.company.tld\find-me, then the issue will be that they're not domain joined and thus the SMB/UNC authentication wont work. Print Deploy doesn't take over the SMB protocol. This is where Mobility Print comes into play. Windows, macOS, iOS, Android, and Chrome clients will all print via the Mobility Print server which handles the authentication at the OS level. It sounds like the print jobs may be getting to the server already but are being cancelled for some reason. If you open the PaperCut Admin Console -> Dashboard and scroll to Real Time Activity, you should see the print job and more importantly, what PaperCut "did" with the job and why. Do you see the job there?
  9. Nothing to see here, please move along and enjoy Mobility Print :-)
  10. Great to hear. I'm not supposed to be negative in my posts, but honestly, taking off and nuking it from orbit sometimes really is the only answer :-)
  11. Heyo. Changing driver settings and maintaining compatibility across a range of devices can take a bit. Maybe create a new queue and test the settings there? I'm pretty sure snagrat is talking about the General -> Preferences and Advanced -> Printing Defaults settings.
  12. Hey @kennysarmy Only just saw this thread (been on leave) sorry... If the "available from" hasn't fixed it... Lets dive in. So.. Steps are: 1 - Print to hold/release queue 2 - Go home without picking it up. 3 - Come back next day, nothing is showing on the PC/Laptop 4 - Go to copier, release job. 5 - Nothin' happens at the copier 6 - Go back to PC/Laptop and the PaperCut User Client has popped up since 7 - Do the account selection etc. 8 - Go to copier, release job, receive print out Is that about right? If so, thats pretty exorcist-level strange. What version of PaperCut are you running? Are you using the stand alone release station? Web based release station? If it's the copier embedded, what copier platform? What printer driver are you using? Does it happen to all PC/Laptop/Users? I'll try and reproduce internally, but we do have a seriously large number of customers that have multi-day hold-release queue settings, support would have been hammered if this was a common problem.. That said, the "available from" strikes me as odd... So I asked around. This is something new that happens on some queues that PaperCut manages. This is done to better support some, uh, "high volume environments" that measure paper consumption by the pallet.
  13. Something to check is that the username attached to the job, as the print spooler on the server sees it. See attached: Check the Windows Credential Manager on the affected machine(s). Failing that.. Two KB articles we have that are good to run through: https://www.papercut.com/kb/Main/UserClientPopupAndNotificationIssues https://www.papercut.com/kb/Main/PrintingNotBeingTracked I apologise for the length of those KBs but they do cover off a heap of things to check. Next step is probably to contact PaperCut Support ( http://www.papercut.com/contact/ ) They (I'm in a different area) will likely want debug logs :-) Namely: PaperCut Application Server Debug: https://www.papercut.com/kb/Main/HowToEnableDebugInNG PaperCut Print Provider Debug (this may be on the server only, but may be on client machines): https://www.papercut.com/kb/Main/HowToEnableDebugInThePrintProvider PaperCut User Client Debug: https://www.papercut.com/kb/Main/HowToEnableDebugInTheUserClient The above is a fair whack of work but gives immense detail as to what is happening. You'll want to: 1 - Enable debug in the App Server 2 - Enable debug in the print providers 3 - Enable debug on both user clients 4 - Restart the client machines, make a note of the time/date. 5 - Print a print job that gets the popup on the wrong machine, make a note of the time/date username expected, hostname of the machine. 6 - Bundle all the logs together 7 - Turn off debugging if you wish
  14. Hi Cache, I think what you're looking for is the Environmental Dashboard as documented here: Environmental Dashboard / Windows 8.1 Live Tiles You can simply chuck the logged in username (of your intranet) on the end of the URL, e.g. http://papercut.your.org:9191/environment/dashboard/jason However, you're specifically after organisational wide information.. which is as easy as requesting "all" instead of "jason", e.g. http://papercut.your.org:9191/environment/dashboard/all Further to this, if you like a little json/ajax, then http://papercut.your.org:9191/rpc/api/web/print-stats.json should whet your appetite. If you need something more specific, please let us know. Cheers, Jason PaperCut Technical Support
×
×
  • Create New...