similar to: I've always HATED printing with Samba

I've not been able to get Samba to print to a Lexmark Z53. If I call it a Z52, the driver uploads (to where, I have no idea so I can't check it) but I still can't get anything out of the printer.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 | [root@enigma 0 3]$ rpcclient enigma -U 'root%XXXXXXXXXX' -c 'enumdrivers' | | [Windows NT x86] | Printer Driver Info 1: | Driver Name: [Lexmark Z53 Color Jetprinter] | | | [Windows NT x86] | Printer Driver Info 1: | Driver Name: [Lexmark Z53 Color Jetprinter] | | [root@enigma 0 3]$ rpcclient enigma -U

I made some comments. Maybe the solution is easy. > ##PRINTTOOL3## LOCAL > lexmarkz53:\ <---THIS AND LP BELOW SEEM TO BE DUPLICATES. > :sd=/var/spool/lpd/lexmarkz53:\ > :mx#0:\ > :sh:\ > :lp=/dev/lp0:\ > :if=/usr/local/lexmark/z53/z53.sh: > > ##PRINTTOOL3## LOCAL > z53-outfiles:\ <----THIS IS THE RAW SPOOL YOU'LL WANT YOUR

Hi, i have the lexmark Z22 printer. If I print a test page through RedHat's printtool in .ps format it works fine, but not ascii. So, i'm wondering how I can change samba so it prints it in a .ps format through the share, I assume that's probably the problem. THX

Hi, Well, my previous attempt to get info on that matter was lame and therefore no one replied. Here is a second attempt. I need info about how to configure samba server and the windows (2000) client to use a printer on the samba server machine. I read the article: http://de.samba.org/samba/ftp/docs/htmldocs/Samba-HOWTO-Collection.html#AEN833 but all I got from it was confusion. I need a

I have set up samba 2.2.2 (debian package 2.2.2-2, actually). Files are shared out (though Win98 doesnt like my valid users lines, a task for another day). However, it hits the fan when I try to share out my printer to my win2000 system (note: I can print from the server). Ive been through DIAGNOSIS.txt and the HOWTO collection, which didnt help, unless I missed something. Here are some relevant

Hi, I installed the smbclient package in debian... I can connect to shared filesystems on the win98 box //LARRY. Such as smbclient //LARRY/AU. and the also the printer //LARRY/ML1210 (my samsung printer.) But when connected to the printer if I say print. It says the following: oube@debian:~$ smbclient //LARRY/ML1210 added interface ip=10.169.17.94 bcast=10.169.17.95 nmask=255.255.255.248 Got

Hi Kurt, I've read the new document. It's a very fine piece of technical documentation. However, it doesn't help me in the present predicament. Going now by this book I'm only getting more frustrated. What are your versions of Samba, CUPS(?), OS, and Printer again? 2.2.8a, 1.1.18, SuSE 8.2 w/2.4.20-62, Lexmark C720 I'm stuck! I would

I have a lexmark Z53 attached to a linux samba server. My native windows clients and my linux clients (thanks to linux support from lexmark) can print to it with no problem. However, when I use windows over win4lin, the drivers don't install. They always fail with a spool32 error. This happens with the lexmark z32 also. I have no trouble installing other printers from the large list that comes

Does anyone have any hints or suggestions on getting some JetDirect-based printers set up for bidirectional printing in Samba? We're using LPRng 3.8.0, ifhp 3.4.7, and samba 2.2.2 From the LPRng standpoint, the printers seem to be set up for bidirectional communication fine.. but how do we get Samba to allow bidirectional communication? Thanks in advance! Glenn --- Glenn E. Sieb,

Is there one can give me some information on how to setup printer in Samba so windows can print to it. My file sharing works fine. In winows can't see the printer. Thanks Matthew Wu School Loans Corp. 10780 Santa Monica Blvd, Ste 225 Los Angeles, ca 90025 Tel. 310-474-7456 ext.235 Email mwu@higheredloans.com

>On Mon, 28 Jul 2003, Jim C wrote: > >> I've not been able to get Samba to print to a >> Lexmark Z53. If I call it a Z52, the driver uploads >> (to where, I have no idea so I can't check it) but >> I still can't get anything out of the printer. >You seem to be going through a big pain barrier! > >You have CUPS installed? If so, then why are

I am looking at buying a new home office printer and wondered what you all might suggest. My current printer is a very inexpensive Canon BubbleJet, and I find it clogs frequently, has very small ink tanks, and the Maintenance functions from my XP clients does not work with samba, requiring I switch the printer cable to an XP machine for maintenance. My config is this: - XP Professional

Is there a way foe me to get the print job name to be something other than "remote downlevel job"? All my jobs are now printing flawless except for this. I would like to be able to get a file name or program at least. Thanks Tony McGrew www.multicam.com

A couple of days ago I set up my printer on my FreeBSD server and set it up so I could print from my FreeBSD client. This all works very well, printing from botht the server and the FBSD client. However, I also have samba set up for file serving with an XP box. I have been trying for quite some time now to set samba up to enable me to print from the XP client. My situation at the moment is that

Dear all I am currently setting up a Samba server and am experiencing a bit of a problem with printing: I have a Canon LBP-1000 connected to the Samba server via the parallel port. Printing directly from the machine works fine. Printing to the printer directly attached to my W2K client works fine, too. When I try to print from the W2K client to the printer connected to the Samba server, however,

Purpose: Create a File Server that can replace our windows file server. System Details: RedHat 8 Kernel 2.4.18-18 SGI XFS 1.2.0 2 disks 1 for the filesystem ext3 1 for the shares using xfs Most of the threads and articles I read about doing this told me that I had to recompile the kernel for acl support. Then I found a post that mention that XFS has built in ACL support. Which

We are planning to replace a quite big domain running W2K with Samba ( at the very least, the DC ). Though i'd love to have the extra security capabilities of W2K ( Kerberos ) as a DC, Samba/NT4 as PDC/BDC with ldapsam will more than suffice for now. The show-stopper right now is this: we need to be able to assign "real" Full Control permissions: a user who has "Full

Hello, I have installed cups on a linux server (running with RH 9.0). When executing "cupsaddsmb -a -v", I get an error: NT_STATUS_UNSUCCESSFULL, when attemping to execute adddriver". Can someone help on the meaning of this error, and on its reason (cause) ? Please find hereafter a file with result (and the error) of this commmand "cupsaddsmb", for a printer:

Wow! I simply copied the Free Agents folder from Windows to Linux, and it worked flawlessly. Only if *all* Windows programs work this well on WINE-Linux, who needs Windows?