LÉVAI Dániel
2008-Oct-13 07:33 UTC
[Samba] samba+cups failure - no printers in the share list
Hi! It seems my samba and cups won't communicate with each other. I've configured samba to load the printers from cups: load printers = yes printing = cups printcap name = cups [printers] comment = All Printers path = /var/spool/samba printable = yes public = no read only = yes create mode = 0700 valid users = @digiszfv printer admin = daniell # lpstat -t scheduler is running no system default destination device for hp_lj_p2015n: socket://192.168.1.66 hp_lj_p2015n accepting requests since 2008. okt. 10., p?ek, 08.49.44 CEST printer hp_lj_p2015n is idle. enabled since 2008. okt. 10., p?ek, 08.49.44 CEST Despite all this, samba fails to advertise the printer: # smbclient -U daniell -L FILESERVER Enter daniell's password: Domain=[DIGISZFV] OS=[Unix] Server=[Samba 3.2.3] Sharename Type Comment --------- ---- ------- print$ Disk Printer Drivers ugyfelszolgalat Disk Ugyf?lszolg?lat adminisztrator Disk Adminisztr?torok optikus Disk Szem?szet IPC$ IPC IPC Service (Samba (fileserver)) daniell Disk Home Directories Domain=[DIGISZFV] OS=[Unix] Server=[Samba 3.2.3] What am I missing? Any help would be appreciated. Thanks! Daniel -- LEVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1
LÉVAI Dániel
2008-Oct-13 10:31 UTC
[Samba] samba+cups failure - no printers in the share list
L?VAI D?niel wrote:> Hi! > > It seems my samba and cups won't communicate with each other. I've > configured samba to load the printers from cups: > load printers = yes > printing = cups > printcap name = cups > > [printers] > comment = All Printers > path = /var/spool/samba > printable = yes > public = no > read only = yes > create mode = 0700 > valid users = @digiszfv > printer admin = daniell > > # lpstat -t > scheduler is running > no system default destination > device for hp_lj_p2015n: socket://192.168.1.66 > hp_lj_p2015n accepting requests since 2008. okt. 10., p?ek, 08.49.44 CEST > printer hp_lj_p2015n is idle. enabled since 2008. okt. 10., p?ek, > 08.49.44 CEST > > Despite all this, samba fails to advertise the printer: > # smbclient -U daniell -L FILESERVER > Enter daniell's password: > Domain=[DIGISZFV] OS=[Unix] Server=[Samba 3.2.3] > > Sharename Type Comment > --------- ---- ------- > print$ Disk Printer Drivers > ugyfelszolgalat Disk Ugyf?lszolg?lat > adminisztrator Disk Adminisztr?torok > optikus Disk Szem?szet > IPC$ IPC IPC Service (Samba (fileserver)) > daniell Disk Home Directories > Domain=[DIGISZFV] OS=[Unix] Server=[Samba 3.2.3] > > What am I missing? Any help would be appreciated.What this post is missing is some more info I think. Samba is 3.2.3 Cups is 1.3.8 OS is a Debian testing Kernel is linux kernel 2.6.24 The printers doesn't show on Linux nor on Win. On the Cups www admin page, I can print out a test page, so the printer is usable. The problem is with the link between cups and samba. Can't seem to figure or find out what is it, though. Thanks in advance! Daniel -- LEVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1
Jeremy Allison
2008-Oct-14 16:39 UTC
[Samba] samba+cups failure - no printers in the share list
On Tue, Oct 14, 2008 at 10:11:34AM +0200, L?VAI D?niel wrote:> Martin Zielinski wrote: >> Hi! >> >> Self compiled Samba? >> Does "ldd smbd" has a link to libcups? >> If you have a smbd that is linked to libcups and cups is running, it >> will work! >> >> Only reason why it wouldn't could be access rights in your cups >> configuration. >> >> After you verified, that libcups is used, it might be a good idea to >> increase the log level of samba and cups and examine the logfiles. They >> might contain the information you need. >> >> Bye, >> >> Martin > > Thanks Martin for the tips. > While checking cups' logs, it showed me the infamous "Unsupported > character set" error, and after reading the bug reports regarding this, > I've converted the server to use utf8. Now samba can get the printers > from cups.I've fixed this in the 3.2.x git tree, so should work correctly in the next 3.2.x release. Jeremy