Hello! we are using cups 1.0.4 and samba 2.0.6 here. windows client can print correctly, but they can not see queue status. the print manager of windows allways shows blank. how to solve this problem? Any body got success to let windows client see the queue of the server ?? thanks for help .... Best Regards, Tbsky
On Mon, 10 Jan 2000 tbsky_lee@unicap.com.tw wrote:> > > Hello! > we are using cups 1.0.4 and samba 2.0.6 here. > windows client can print correctly, but they can not see > queue status. > the print manager of windows allways shows blank. > how to solve this problem? > Any body got success to let windows client see the > queue of the server ?? > thanks for help .... > > Best Regards, > Tbsky > >I have no problems in displaying the print queue, apart from the fact, that it displays Samba job IDs (computer_name.job_number). There is nothing unusual in smb.conf. Here are relevant parts: [global] workgroup = FLASH printing = bsd printcap name = /etc/printcap load printers = yes guest account = drukarka lock directory = /var/lock/samba locking = yes strict locking = yes share modes = yes security = share domain master = no local master = no ; this is for OS/2 lm announce = true lm interval = 10 [printers] path = /var/spool/samba/lp browseable = no printable = yes public = yes writable = yes create mode = 0770 lprm command = /usr/bin/lprm -P%p %j print command = lpr -r -h -P %p %s ; rm %s Hope this helps, Michal ------------------------------------------------------------- Linux is like a wigwam - no windows, no gates, apache inside! -------------------------------------------------------------
tbsky_lee@unicap.com.tw wrote:> > Hello! > we are using cups 1.0.4 and samba 2.0.6 here. > windows client can print correctly, but they can not see > queue status. > the print manager of windows allways shows blank. > how to solve this problem? > Any body got success to let windows client see the > queue of the server ?? > thanks for help .... > > Best Regards, > TbskyI had the same problem for some time and finally found a web page that helped me out. Unfortunately I can't remember the URL. What I do have though is my corrected Printcap and how it works. lp|<Printer Alias>|HP LaserJet 4Si:\ :rw:sh:lp=XXX.XXX.XXX.XXX%9100:\ :sd=/var/spool/lpd/<Printer Alias>:\ :ps=status:fx=flpv;\ :if=/etc/magicfilter/ljet4-filter: To see the queue, you must queue the job within the machine and not utilize the printer queue. To accomplish that, you need to send the data to port 9100. I'm assuming you're using a networked printer since I've not seen anybody that has had problems with a printer connected locally. I am still working out one glitch that prevents me from effectively removing a print job. If I attempt to delete a print job in the queue, I get an error. Good luck and I hope this helps, -- David Hamilton Service Manager Business Computer Services Business Administration and Economics (505) 646-5353
> > Hello! > we are using cups 1.0.4 and samba 2.0.6 here. > windows client can print correctly, but they can not see > queue status. > the print manager of windows allways shows blank. > how to solve this problem? > Any body got success to let windows client see the > queue of the server ?? > thanks for help .... > > Best Regards, > Tbsky > >> I have no problems in displaying the print queue, apart from > the fact, that it displays Samba job IDs > (computer_name.job_number). There is nothing unusual in > smb.conf. Here are relevant parts:<skip> do u use cups as ur printing system also ? the configuration seems bsd style... i use "printing=cups" at smb.conf.... cups is really good, but i really have queue problems with samba.... if i can not fix it, i must turn back to use bsd style printing systems :( i have five network printers connect to samba (no local printers) jetdirect X 2 epson n1200c with nic printer server nic X 2 Best Regards, Tbsky
Hello!
we are using cups 1.0.4 and samba 2.0.6 here.
cups is a really good printing system.
(at we use printing = cups at smb.conf)
windows client can print correctly, but they can not see
queue status.
the print manager of windows allways shows blank.
how to solve this problem?
Any body got success to let windows client see the
queue of the server ??
thanks for help ....
PS: our samba server connect 5 printers. all are network printers.
2 jetdirect (use port 9100) 3 lpd network printers (use port 515)
so i don't know if local printers works or not....
i install cups first(with binary) , then samba(rebuild the source
rpm or
compile from souce..)
i think the step is correct...
i turn on the debug level of samba. and i can see some information
like
this : (i print the win95 testprinter page from windows client)
[2000/01/10 13:42:33, 6] printing/printing.c:get_printqueue(1041)
QUEUE2: 1st 50 nobody 12 PrinterTestPage 258048
bytes
so i think samba can find the queue status. but it can not
transfer the status to windows client ....
any solutions ?
Best Regards,
Tbsky
> Tbsky,> What we have experienced here is that IP printing is fast enough that > the job disappears from the print queue and is spooled on the printer > before the print queue command is processed. We have two types of > printers here, IP and Appletalk (please don't ask why), and the jobs on > the Appletalk printers, for which there is a filter which takes much > longer to print, show up in the Windows print manager window. The jobs > on the IP printers don't. mmmm. i think my logic is very simple: what i can see with "lpstat" or "lpq" on samba server, i should also see them at windows client. because samba act this way, am i wrong ? if i have ten jobs waiting for printing on the samba server, i use lpstat can see them, so windows client should see them also. but with cups and samba i can not. in fact, if i use "printing = bsd" and tune the printing parameters instead of "printing = cups". i can see the queue status at windows client but the informations are not all correct (ie. like the job id is wrong).. because samba doesn't understand the cups lpq command output... yes maybe i can use some script to tune the lpq command output to suit samba.. but why do this when we have "printing = cups " ?? Best Regrads, Tbsky
> Tbsky,> What we have experienced here is that IP printing is fast enough that > the job disappears from the print queue and is spooled on the printer > before the print queue command is processed. We have two types of > printers here, IP and Appletalk (please don't ask why), and the jobs on > the Appletalk printers, for which there is a filter which takes much > longer to print, show up in the Windows print manager window. The jobs > on the IP printers don't. > mmmm. i think my logic is very simple: > what i can see with "lpstat" or "lpq" on samba server, > i should also see them at windows client. > because samba act this way, am i wrong ? > if i have ten jobs waiting for printing on the samba server, > i use lpstat can see them, so windows client should see them also. > but with cups and samba i can not. > in fact, if i use "printing = bsd" and tune the printing parameters > instead of "printing = cups". i can see the queue status at windows client > but the informations are not all correct (ie. like the job id is wrong).. > because samba doesn't understand the cups lpq command output... > yes maybe i can use some script to tune the lpq command output > to suit samba.. > but why do this when we have "printing = cups " ?? > Best Regrads, > Tbsky mmmm..i still get no response from samba & cups... so i think if i still want to use cups..better do some scripting now.. anybody know what samba expect for the "lpq" command output ??" i now give samba below : rank job file size owner pri garbage then windows clients can show and delete print queues (but of course the informations are not all correct...) want kind of information should i give samba ??? thanks for help... Best Regards, Tbsky