Jump to content

Recommended Posts

Posted

Hello Everyone,

 

I don't know where to begin with this problem or if anyone else may have experienced this and has a solution to it.

 

One of my members of staff whenever they attempt to print to our network printers, no matter what machine they are on, seems to make the software they are trying to print from stop responding. This could be a brand new document that they just created or an existing document that other users can print fine. Everyone else who uses the computer are able to print just fine and get the papercut pop up except for this one user. It isnt isolated to her classroom computer either, it happens on a fresh VM and other computers in the network. The user has all the exact same permissions as all of the other members of staff in her department who can all print just fine so im not sure that it could be a permission issue

 

Does anyone have any ideas?

 

Thanks

Posted

What type of profiles are you using?

 

Do you require the Papercut client to send a job to the printer (e.g. account codes) or is it just used to notify the user it's in a queue?

 

How is the Papercut client installed/running? Installed locally, running from a share in standard/cached mode etc.?

 

How is the printer mapped? script/GPO/Papercut Print Deploy etc.?

 

Assuming it's a virtual queue, can they print directly to the printer via it's IP?

 

Could try running ProcMon when they try to print and see what's happening.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...