similar to: Samba printing and CUPS

The Adobe drivers (on request of the printer PPD associated with them) often put a PJL header in front of the main PostScript part of the print file. Thus, the printfile starts with <1B >%-12345X or <escape>%-12345X instead of %!PS). This leads to the CUPS daemon auto-typing the incoming file as a print-ready file, not initiating a pass through the pstops filter (to speak more

I am setting up printing services on a Suse 10.1 server useing Samba 3.0.22 I can create a printer on an XP client and connect to the Samba printer share. I can the print a test page from XP. The print file gets to the server (see logs below), but nothing prints I can print files from Linux to the printer OK Any suggestions will be appreciated ++++++++++ smb.conf ++++++++++ [global] workgroup

I am setting up printing services on a Suse 10.1 server useing Samba 3.0.22 I can create a printer on an XP client and connect to the Samba printer share. I can the print a test page from XP. The print file gets to the server (see logs below), but nothing prints I can print files from Linux to the printer OK Any suggestions will be appreciated ++++++++++ smb.conf ++++++++++ [global] workgroup

I've about run out of ideas and need some help. I have an HP OfficeJet 7110 installed on my Fedora Core 3 box. From Linux, it prints perfectly, the Test Page works, I can print from Mozilla/Thunderbird/Firefox, KDE applications, and even Emacs, all without any issues whatsoever. The problem is I can't seem to get it to work when I share the printer to Windows. I've shared it to

The Highlights: -CentOS 4.4 & CUPS -HPLIP Installed -Running as server, no GUI. -Can print from command-line no problem. -Printing from Windows XP via Samba puts job in the correct queue, job is processed but not parsed or rendered. The job is removed from the queue, but never prints. (I've RTFM and google'd it, no avail...) Help?? When printing from commandline (eg. cat file

Hi I've recently upgraded to 3.0.2 from 2.2.8 on Redhat 9. We have 2 Linux servers and a number of windows XP machines. The primary domain controller has a printer which is shared and to which all the computers have access. Since upgrading, the other Linux server cannot print to shared printers on the primary linux controller or on windows machines and cannot install new shared printers from

Hi I've recently upgraded to 3.0.2 from 2.2.8 on Redhat 9. We have 2 Linux servers and a number of windows XP machines. The primary domain controller has a printer which is shared and to which all the computers have access. Since upgrading, the other Linux server cannot print to shared printers on the primary linux controller or on windows machines and cannot install new shared printers from

Good afternoon, This is my first post, so please be gentle ;) Anyway, here's my question....I've recently put together a Linux Server for our company, replacing an old Novel server. I have the box set up with Samba, as a PDC on our network. So far, just about everything is working correctly. One issue I'm coming up against, though, is printing from DOS. I have Samba

Good day everyone, Just a quick question. When using Samba 2.2.7a and Cups 1.17 or 1.18, is it good or bad to use "Use client driver" as a share setting on the Printers share? I used it with LPD, but I'm not real sure it's necessary with cups. Thanks in advance Darin Bawden TeamDME! Technical Support (615) 333-1900 dbawden@teamdme.com

Hi everyone, I have a question about the logon script command. I've read and read and read the man page for smb.conf. In essence, I've duplicated the settings on the PDC how-to document to create a PDC with a logon script. However, when I log in, the scrips doesn't run. The only thing I don't have enabled, like the how-to, is roaming profiles. I'll include my smb.conf for

Hi everyone, I have a question about the logon script command. I've read and read and read the man page for smb.conf. In essence, I've duplicated the settings on the PDC how-to document to create a PDC with a logon script. However, when I log in, the scrips doesn't run. The only thing I don't have enabled, like the how-to, is roaming profiles. I'll include my smb.conf for

Hi I am currently using Samba 3.0.11 and Cups 1.1.23 with Windows PostScript drivers and manufacturer PPDs on WinXP clients. When I print multiples copies of a document from a Windows XP box, the number of copies appearing in the Cups "page_log" file always takes the "1" value but the printer prints the correct number of copies. When I do the same on Linux (with the lpr

I've been running RedHat 5.0 and Samba flawlessly for over 6 months now. I had to reboot the server and now I can't seem to print. When I use the "Printtool" to send a test text or postscript job to the printer, I get the following error: Unable to print to HP4000 Error Message: lpr: connect: no such file or directory jobs queued, but cannot start daemon The printer is set up

hey, i use http://mir.aculo.us/articles/2005/10/03/ruby-on-rails-i18n-revisited then i have nl_BE.rb, de_DE.rb, en_US.rb as translation files. this works all fine when i have normal characters, but i have one problem when i have wierd characters like ? ? ? (mostly in french), then i get japanese charachters on my site i use utf8 for my database and i set this for each def in my controllers,

Dears All, I have used rsync on Cygwin for a long time to backup data on my WinXP laptop to a NAS server. Several days ago I had a problem with my user account on the Laptop and I needed to create a new account and delete the old one. Fortunately my data were on a separate partition (fat32) so I did not lose anything. Now when I try to use rsync again on the same data I always get the

Hello everyone, I have a redhat 9 server running with Samba 3.0. It's a bit different than the previous version, but I'm finally getting used to it. Here's my biggest issue: This is a server for approx. 15 clients, all but one running WinXP. Previously, we were running 2.2.8 w/ Win2K clients. In the past, we were able to log into the local computers, even when we didn't have a

I think this isn't plj output. Please take a look : document printed from Foxit Reader(PDF), all works fine: LINK: http://img526.imageshack.us/my.php?image=digitalizar10001rw2.jpg error_log output using Foxit Reader: D [18/May/2007:13:27:58 -0300] cupsdAcceptClient: 9 from localhost:631 (IPv4) D [18/May/2007:13:27:58 -0300] cupsdReadClient: 9 POST /printers/teste_ HTTP/1.1 D

I waited three days to post this while googling, reading, testing. I can't figure this out, so am hoping someone here has had a similar problem and can recommend a solution. System and versions: Kernel 2.6.17.13 Slackware-11 Sambe 3.0.23c CUPS 1.2.4 Printer HP Photosmart 7550 on usb. Samba guest account=ftp (I read that the account nobody can cause trouble). $ lpstat -s system default

I had been running Samba to share my HP printer among my Windows XP clients. When I upgraded to 3.0.4, I can no longer print. When I start the print job in Windows XP, the printer lights blinks for a few seconds, and then stops. No pages come out. The print job is shown as complete in the CUPS web intrface. Printing from the Linux box works just fine. I read the Samba pages concerning

Is there any work going on for Samba 2.0.6 in the way of making passwords expire ? Or does anyone know how to do it ? Thanks. Alan.