similar to: Trying to print...

This is just an FYI, folks. We've got this large poster printer. We had some, er, environmental issues, let us say, and first I had to recreate the .ppd (HP "doesn't support printing from Linux, and the one a former coworker extracted from the Mac package... was for a 23", not this 44"). Then... I was trying to print from a 6.9 box. I hadn't rebuilt the box as C 7,

Hello, I have configured cups (1.1.18) on a Suse 8.2 Pro Linux server. I have also configured samba (2.2.7a), and joined a domain. I have created printers with cups and declared them to samba with cupsaddsmb command. All seems to be ok. I can print from my Linux server. But, when I want to print from ny windows2000 station: - I can find my linux server - I can find and connect printers

Well, I have a strange one again. Using samba version 2.2.5 and cups version 1.1.15. We have 2 printers over the network, both TCP/IP-based Jetdirect printers. on is on x.x.x.32, the other on x.x.x.38. I can print to the laserjet on IP 32 all day long. However, both on Windows clients, print jobs are not even seen in the que (either windows print que or CUPS web interface). When I try to

OK, I've downloaded and installed the driver (pxljr-1.1-1.i386.rpm), and the ppd file (HP-Color_LaserJet_3550-pxljr.ppd) in /etc/cups/ppd. Now I'm trying to set up the printer, connected to the network via a JetDirect printer server at location 192.168.0.200. Trouble is, I'm really not sure about all the settings in Printer Configuration - specifically, what should the Device URI be -

Hey folks, okay, here's the situation - I have a Centos 4.2 system with cups printing installed printing via postcript (with appropriate PPD file) to a HP LaserJet 1320N printer (via jetdirect socket 9100). Everything seems to work right - except for an unusual 'font'??? problem. Many letters seem to be just slightly garbled. At first I thought this was a mechanical problem at

We're putting together a Linux-cups-samba print server for Windows clients. A dozen print drivers have been loaded and used successfully on the Windows clients from the samba server. But, one particular printer is causing trouble: a Xerox DC 2240. When a windows client tries to open the printer preferences, after connecting to the printer on the samba print server, a popup says

I'm trying to change my Samba setup from LPD to CUPS, with little success. I've followed [and re-followed] the setup documentation from CUPS and I just can't get Samba to recognize my printer. The catch is - it sort of recognizes it :-( First I added these lines to my smb.conf: ========================================= [global] load printers = yes printing = cups printcap name =

Dragan, Andy Thanks for your answsers. Please find hereafter more information and my notes. Nadine ---------------------- R?achemin? par Nadine Vandois/FR/BULL sur 11/08/2003 10:56 --------------------------- "Dragan Krnic" <dkrnic@lycos.com> sur 10/08/2003 09:47:05 Veuillez r?pondre ? dkrnic@lycos.com Pour : nadine.vandois@bull.net cc : samba@lists.samba.org Objet :

Yeah, about that... Back in '12, we got a nice HP poster printer. They don't support Linux, but a co-worker got the .ppd out of the Mac support file. I tried it, then I looked at the file in vi... and found it *only* supported the 24" printer, *not* the 44" printer that we had. Well, we just bought a replacement, since the old printer was EOL'd. This time, I went to hplips,

If you're using LPRng, add :done_jobs=0 to either the .common section or each printer's entry. This will remove the (retained) last job printed, and you won't see it displayed as Paused anymore. It seems that if Samba sees a job in the lpd queue dir that has been printed, but not removed, it shows that job with a status of Paused. LPRng after 3.8.10 defaults to :done_jobs=1, and

On Tue, February 23, 2016 10:13 am, m.roth at 5-cent.us wrote: > Juan De Mola wrote: >>>From: John Hodrien <J.H.Hodrien at leeds.ac.uk> >>>On Tue, 23 Feb 2016, Juan De Mola wrote: >>> >>>> CentOS 6 has problems printing when the Internet goes down. And 7 is >>>> still untested for the software we are running on Linux. >>>

I have had terrible luck trying to find a ppd that works correctly for both win9x clients and winNT/2000/XP at the same time. The CUPS method is to find one ppd that works for all and I have tried several: those at linuxprinting.org, hp's sourceforge site, vendor winNT ppds (docs suggest these), and vendor win98 ppds. I have tried filtering PJL and not filtering PJL. I have the stock

I had a problem with Samba 2.2.5 with the printers being permanantly paused to Windows machines. They could print OK - it was only the status that was wrong. The reason for this was because I had used the word office in the printer name / comment. This was causing the parser which recognises the printer status to find 'off' pausing the printer. A quick fix for this is to replace the

Hi list, I've just figured it out. When we're installing the drivers from adobe there's a part where we must "Select the Printer Model". By default it uses the "Generic Postscript Printer" (it has an associated PPD for that). We must get a PPD for our printer (installed on the linux server) from the www.linuxprinting.org, click the "Browse" button and

We've got this huge HP DesignJet Z9 printer, for printing posters. Except... I got the latest hplips installed, it knows this printer... but there are no poster-sized settings. Now, I've started hacking the .ppd, as I did six year ago for the old poster printer, but it seems, after a good bit of googling, that it would be easier, when I hit print from okular, and get the dialog window, to

Hello, To my great satisfaction I managed to run with a windows program which I use in my company (invoices, supplies etc). The program runs well except printing... When I try to print to my cups printers I get the following infos: fixme:winspool:WINSPOOL_EnumPrinters We don't handle PRINTER_ENUM_CONNECTIONS fixme:winspool:WINSPOOL_EnumPrinters We don't handle PRINTER_ENUM_CONNECTIONS

Hi list I have two very similar printers set up on CUPS and Samba is configured to share the drivers. I had been playing around with setting up a RAW printer queue with native Windows drivers but eventually gave up on that. I deleted all printers and redid them from scratch and now only one of them works. Setup: Ubuntu Karmic 2.6.31-15-server #50-Ubuntu SMP Tue Nov 10 15:50:36 UTC 2009

regarding this old message: > > Am Sam, M?r 20, 2004 at 04:40:10 -0500 schrieb JLB: >> Nopers, and it FREAKS OUT when I go into Printer Setup and select a page >> orientation (e.g. Portrait) > > Hmmm, seems that you first have to learn how to configure printing? Look > in the Documentation section on winehq for that. If you use Cups > everything is done for you

Ah, it appears that I have confused myself... I indeed have ALL of the queues defined as JetDirect with the model specific driver selected in printconf. With this combination I am telling linux to modify the job [via the filter] and then pass it as a RAW [jetdirect] where I SHOULD just have the queue define as JetDirect with a RAW as the driver and let the job go as transmitted by the client

We're using Cups and Samba with Adobe Postscript Drivers to print from XP SP2 machines via our Solaris and Linux Domain Controllers. Everything has been working OK, but when I setup an a new printer (identical ppd file to another one), it doesn't download the drivers on XP when I add the printer. This is happening on two domain controllers in different offices. It gives the error when