similar to: Mdk 9.1, samba-LDAP 2.2.8a/3.0b3 (LDAP) can't print toz53

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.

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

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

Primarily because I've never gotten it to work despite frequent efforts. Offeding printer is a Lexmark Z53 (supposedly fully supported) and when ever I try to add it to an XP box I get "Server doesn't have the right driver, do you wish to upload the driver?" then when I do it says "Cannot connect to the printer. Contact your network administrator yatta yatta

http://www.linuxprinting.org/foomatic2.9/show_printer.cgi?recnum=328553 Laura West wrote on Samba-Digest: > Date: Sat, 08 Mar 2003 17:36:11 -0800 > From: Laura West <lwest54@mindspring.com> > To: samba@lists.samba.org > Subject: [Samba] Samba config for Windows XP Printer > Message: 27 > > Hello, > My Samba installation seems to be going pretty smoothly thanks to

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

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

Cups admin manual says it is just to have smb.conf to include printing = cups printcap name = cups I have tried to get a print out from a windows client to the linux hosted server for weeks now... Printer: Lexmark-z53 on usb Linux distr: Suse 9.0 Kernel: 2.4.21-166 Samba: 2.2.8a-139 Cups: 1.1.19-85 Windows XP client. cups error_log never gets the print command. Cups works fine when printing

Hi folks, This is probably a stupidly simple question, but its got me stumped. I just installed the latest MDK package for wine (wine-20031118-mdk.i586) to update the one that shipped with MDK 9.2 (wine-20030813-1mdk.i586). Now, when I try and run wine I get wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory libwine.so.1 is in

James, I have sent this to you directly and cc:ed the list for reasons that should become apparent below. THE SITUATION OS: mdk 7.2, 2.2.19 kernel - basically bone stock Latest addtions: samba 3.0.7-1 compiled from source (working fine); cups-1.1.18-1 from mdk rpm Reasons for additions: XP SP2 fun and games THE MYSTERY As any normal person does, I use

Hello, I am trying to compile Speex on RealView Compiler and a lot of errors are indicated by compiler: libspeex\bits.c(48): error: #77-D: this declaration has no storage class or type specifier libspeex\bits.c(48): error: #65: expected a ";" libspeex\bits.c(139): warning: #12-D: parsing restarts here after previous syntax error libspeex\bits.c(141): error: #77-D: this declaration

Mates, In following chapter 35 "How to Compile Samba" I have looked at ./configure --help and I have a few questions. Originally I installed 2.0.9 via RPM, and of course there are no longer RPMs for mdk 7.2. On 7.2, smbd and nmbd are installed in /usr/sbin. The docs are in /usr/share/doc/samba-2.0.9. I don't know where the rest of the pieces of the puzzle were scattered by

Mates, I am at the point that I will have to update my trusty samba 2.0.9 to 3.0.6 or 2.2.11. (damn SP2) Problem is that my production machine is still running Mandrake 7.2 and, of course, there aren't any RPMs for the old distro. So, I guess my option is to install from source. Do I need to rpm -e the 2.0.9 before attempting to compile and install 2.2.11 or 3.0.6? My server is a simple

A new company, Typekit, is a font service provider. Your Web pages need not be drab anymore -- and its compatible with major browsers. http://www.linux-mag.com/id/7501 Martin

Here is my smb.conf. Maybe someone can tell me what I'm doing wrong. [global] workgroup = HOMEGROUP log level = 8 path = /var/spool/lpd/HPDESKJET default service = global writable = yes printer = HPDESKJET remote announce = 192.168.x.x/HOMEGROUP print command = lpr -l -P%p %s printing = bsd load printers = yes dns proxy = No lprm command = lprm public = yes printcap name =

Mike Watson wrote: > I don't have an explicit print command in my smb.conf. Is that required? All > the examples I have do not have an explicit command. Since I'm use lpr, I'll add > that to my config and see how it works. > > BTW. The Linux printer is an HP Deskjet 600. Old but it still works---crispier > than my wife's laser printer. > > Thanks! >

On 02/10/2018 18:46, Larry Martell wrote: > I got 2 years of work solving the year 2000 issue. I don't think I've ever said this but I am very envious of all these people who had loads of work due to Y2K or were paid obscene amounts of money to tend systems over new year's eve/day. I was working for an ISP at the time and got none of this. Nothing happened. I don't even recall

Hi all, Situation: We use smbtar for backups, incrementals done using -N <last date file>, and this has worked well with samba 2.2.x After upgrading to 3.0b3, using the -N (newer) option to smbtar causes a bad interaction with smbclient. Eg,: # smbtar -s PC -x Share -u User -p Pwd -d / -t - -N last-backup -v gives (if you print out the eval at the end of smbtar script): eval

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