Hi.
Samba 2.2.8. I have installed the drivers on the print$ share. The smb.conf
looks like this:
[printers]
print ok = yes
guest ok = yes
printcap name = /etc/printcap
print command = /usr/bin/lpr -P%p -r %s
lpq command = /usr/bin/lpq -P%p
lprm command = /usr/bin/lprm -P%p %j
lppause command = /usr/sbin/lpc hold %p %j
lpresume command = /usr/sbin/lpc release %p %j
queuepause command = /usr/sbin/lpc stop %p
queueresume command = /usr/sbin/lpc start %p
[IBM Infoprint 1222]
comment = IBM Infoprint 1222
path = /var/spool/lpd/samba/2ndflbw
printable = yes
browseable = yes
writable = no
printer = IBM Infoprint 1222
>From the samba server:
[root@ka W32X86]# rpcclient ka -U root -c "enumprinters"
Password:
cmd = enumprinters
flags:[0x800000]
name:[\\ka\IBM Infoprint 1222]
description:[\\ka\IBM Infoprint 1222,,IBM Infoprint 1222]
comment:[IBM Infoprint 1222]
[root@ka W32X86]# rpcclient ka -U root -c "enumdrivers"
Password:
cmd = enumdrivers
[Windows NT x86]
Printer Driver Info 1:
Driver Name: [AGFA-AccuSet v52.3]
Printer Driver Info 1:
Driver Name: [IBM Infoprint 1222]
Yet if I click "connect" for that printer in a XP SP1 WS (that belongs
to
that domain) I get the well known error "The server for the printer does
not
have the correct printer driver installed..."
Any hints?
> flags:[0x800000] > name:[\\ka\IBM Infoprint 1222] > description:[\\ka\IBM Infoprint 1222,,IBM Infoprint 1222] > comment:[IBM Infoprint 1222]> [Windows NT x86] > Printer Driver Info 1: > Driver Name: [AGFA-AccuSet v52.3] > > Printer Driver Info 1: > Driver Name: [IBM Infoprint 1222] > > Yet if I click "connect" for that printer in a XP SP1 WS > (that belongs to > that domain) I get the well known error "The server for the > printer does not > have the correct printer driver installed..."How did you upload the drivers? Did you get any errors toward the end of this process? Did you use drivers for IBM Infoprint 1222 that came with windows or some other source? Some manufacturer provided drivers do not behave when remote uploaded to samba. I'm not sure if it's ever been tracked down to anything specific. But I've ended up in a situation (with KM KX drivers) where the print share is associated with the correct printer model, but got your error that no driver was installed. And an rpcclient deldriver did not work, because it was associated with the print share (had to setdriver it to something else or remove that print share first). Sorry can't be of more help, but I'd try a different driver if there are any available, and contact any support/help email address or list associated with the IBM Infoprint drivers and let them know it isn't behaving with samba. ~ Daniel ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
> > > flags:[0x800000] > > name:[\\ka\IBM Infoprint 1222] > > description:[\\ka\IBM Infoprint 1222,,IBM Infoprint 1222] > > comment:[IBM Infoprint 1222] > > > [Windows NT x86] > > Printer Driver Info 1: > > Driver Name: [AGFA-AccuSet v52.3] > > > > Printer Driver Info 1: > > Driver Name: [IBM Infoprint 1222] > > > > Yet if I click "connect" for that printer in a XP SP1 WS (that > > belongs to that domain) I get the well known error "The server for > > the printer does not > > have the correct printer driver installed..." > > How did you upload the drivers? Did you get any errors > toward the end of this process?Yes. If you follow the tutorial on the samba site you're lost! :-E I've spent a whole day figuring why on earth I was getting errors and guess what? You don't have to use the APW! At least not from the beginning; God I wish I had some good doc! Samba docs are not what they used to be; it looks like the Zope way of doing docs is spreading... Anyway, the idea is that the standard APW from XP attempts to do TWO things at a time: put the drivers on the server (so the server know what to give when asked) AND install the printer locally! This is wrong if you don't have the "add printer command" in smb.conf. If any of those parts fails you're confused because the APW DOES NOT TELL YOU WHICH PART FAILED! Fortunately you notice that the drivers are placed on the server print$ but you still get an error, don't you? Well the error is because samba does not know what drivers to serve for that particular printer share at the "add printer to the local machine" stage of the APW from client! You have to define the share and then from the "printers and faxes" share (that you'll see on the server) you right click on that particular printer; ignore the error and voila there is a "Sharing" tab where (in XP in the lower right) you see an "Additional Drivers" button! That is the way to install drivers on the server! After that, the key is in the rpcclient: You list the drivers and printers on that server (with the commands that you saw in my previous message) and then you "connect" them to the defined printer shares!!!! Damn, If only someone would have told me... #rpcclient servername -U root rpcclient> setdriver "the name of the printer share" "the name of the driver as reported by rpcclient enumdrivers" In may case it was rpcclient> setdriver "2nd floor ugly IBMInfop1222" "IBM Infoprint 1222" ... And for clarity, I do have a [2nd floor ugly IBMInfop1222] in smb.conf.> Did you use drivers for IBM > Infoprint 1222 that came with windows or some other source?The ones that are on the printer's CD are just fine! The PCL ones do work great; XP will ask for location will take them from CD and copy them on the server. After this, one can eventually make a script that would be declared in smb.conf as "add printer command"; it should modify the smb.conf, create the spool dir *AND* register the drivers with rpcclient so you'll be able to use the download drivers feature on the server. Either I'm really missing something or the printer_driver2.html from the samba site is BADLY incomplete to say at least... :-| Bottom line, if it's an IBM network printer and you set a raw spool on the samba machine it should work with the drivers served from the server.
Hi List, I am trying to recompile the Samba Server Suite for my RedHat 7.2 system. RedHat 7.2. has been installed as is with the shipping samba-2.2.1a.rpms. Is there a command to find out how and with which options and setup the people at redhat compiled it?! or can anyone help with the ./configure settings for this environment?! my first attempt with configuring the options for my system according to ./configure --help information did deathly FAIL! Any Help will be appreciated, thanks in advance kind regardez Florian Stahl (fstahl@xantury.com
Vizitiu, Ciprian CVizitiu at gbif.org wrote on Samba-Digest: [....]>>From the samba server: > > [root at ka W32X86]# rpcclient ka -U root -c "enumprinters" > Password: > cmd = enumprinters > flags:[0x800000] > name:[\\ka\IBM Infoprint 1222] > description:[\\ka\IBM Infoprint 1222,,IBM Infoprint 1222] > comment:[IBM Infoprint 1222] > > [root at ka W32X86]# rpcclient ka -U root -c "enumdrivers" > Password: > cmd = enumdrivers > > [Windows NT x86] > Printer Driver Info 1: > Driver Name: [AGFA-AccuSet v52.3] > > Printer Driver Info 1: > Driver Name: [IBM Infoprint 1222] > > Yet if I click "connect" for that printer in a XP SP1 WS (that belongs to > that domain) I get the well known error "The server for the printer does not > have the correct printer driver installed..." > > Any hints?At that very moment, under which user's account are you connected in Samba's point of view? Check by using "smbstatus"... Is it an account priviledged enough to administer printers and write to the [print$] share? Cheers, Kurt