Date: Thu, 24 Jul 2003 12:22:29 -0700 From: "Derrick Ryalls" <ryallsd@datasphereweb.com> To: "'P. U. Kruppa'" <root@pukruppa.de>, "'Andrew Stuart'" <elitetek@tekrealm.net> Cc: freebsd-questions@freebsd.org Subject: RE: samba(2.2.8) printer server (on 4.8-RELEASE) Message-ID: <001501c35218$efb2efc0$0200a8c0@bartxp> In-Reply-To: <20030724170138.I766@small.pukruppa.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>=20 > > On Sat, 19 Jul 2003 at 07:58:05 +0200, P. U. Kruppa wrote: > > > > > > Hi! > > > > > > I am trying to set up a printer server > > > (SAMBA 2.2.8 package on 4.8 -RELEASE, printer is a Kyocera > > > FS-3700+ laser printer) which should be accessible from Win2000 > > > and WinNT4 workstations _without_ any authentication. > > > > > > These are the steps I have taken so far: > > > > > > 1. I used apsfilter to make the kyocera work locally as a > > > postscript-printer called lp . > > > 2. (Sorry - stupid me forgot to bring home a copy of smb.cfg over > > > the weekend) > > > I edited smb.cfg so that the printer-server and lp itself can > > > be seen in Windows' network enviroment, i.e. I set > > > security =3D share > > > and put up a share called > > > [printers] > > > browseable =3D yes > > > path =3D /var/spool/lpd/lp > > > read only =3D yes > > > printable =3D yes > > > guest ok =3D yes > > > and I > > > # chmod -R 4777 /var/spool/lpd/lp > > > 3. I used windows' printer setup to install the kyocera driver > > > for lp > > > 4. When I try to print something, everything looks fine from the > > > client side and I can see some blinking of the > > > printer-server's LED's but nothing more happens. > > > The windows printer queue stays empty, no files are created in > > > /var/spool/lpd/lp > > > > > > Any ideas, what could be done next? > > > > did you let samba compile with cups support? (its set by default) > > > > If so, rebuild samba checking the box for nocups "without CUPS" > > > > and try printing again, most likely it will work perfectly. > > > > There appears to be a bug in the way samba handles the cups=20 > support,=20 > > my guess is it defaults the print/lprm/lppause/lpresume commands=20 > > differently then it does when you specify nocups. > Andrew, >=20 > thanks for your answer, > it took me some time to recompile samba on a P75 without=20 > cups. But the problem remains. Still I can see the documents=20 > arriving in Windows' printing queue, but they aren't printed.=20 > Do I perhaps have to produce a machine account for the=20 > printer server in the Windows domain? I am asking this,=20 > because in my mini home network, printing to samba works=20 > fine, but there my samba-machine also acts as Primary Domain=20 > Controller. Or - I configured the printer as Postscript=20 > printer: Perhaps Windows cannot deal with that? Or - is there=20 > any way to analyse the problem - looking at log-files p. ex. ? >=20 When I was trying to get a couple windows boxes to print to a Samba shared, cups controlled printer, I had to do this on the windows side: Control Panel -> add Printer Specify Local Printer (even though the machine is remote) Create a new Port When prompted for a Local printer port name specify \\<machine>\<Samba Printer> Add windows printer driver for model of printer. Print test page. Hope this helps. -Derrick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001501c35218$efb2efc0$0200a8c0>