Jump to content

Lexmark XS548 printing A4 documents oversized (A3)


Recommended Posts

Posted

Hi,

 

I have a large number of Lexmark XS548 printers here on the network which up until about 6 months ago worked without issue however, since then we've been getting increasing reports of A4 documents printing oversized as if they should be A3.

 

  • Users are not sending these as A3
  • Printer settings are not set to use A3. All printers have cloned local settings
  • We use PaperCut here and this stops any jobs, A3 size, at the workstation so won't even reach the server queue.
  • Default Printer preferences are set to A4 (210 X 297 mm)
  • This happens with the original driver I was using and the latest
  • A user can send to another Lexmark printer and prints fine but another user will experience the same issue on that printer
  • Print preview shows the document normal size.

 

Lexmark support are being about as useful as a chocolate fireman at the moment so hoping someone here has seen a similar issue and have a workaround!?

  • 1 month later...
Posted

Very strange solution for this in the end if anyone's interested!

 

Turns out the printer requires a gdl file to be created in 'C:\ProgramData\Lexmark Universal v2 XL' which is initially generated under the currently logged on user's security context. Default permissions on ProgramData meant that user accounts couldn't create this folder/file combination and so the file was redirected to a writable location within their 'N:\My settings' (RM Network) directory. Looks like this file was not designed/intended to roam with the user and so caused the symptoms described above.

 

The solution was to use a combination of GPP/GPO to create the Lexmark folder and set relevant NTFS permissions on this. Since doing this printing has returned to normal.

 

This is a fairly specific issue and am not surprised that others haven't experienced this problem as would require Lexmark printers (Maybe only this model) running on a CC4 network however, doesn't explain why this wasn't an issue for the years we had these before this became apparent!

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...