[TriLUG] Samba printers - give the drivers to Windows XP clients

David McDowell turnpike420 at gmail.com
Mon Mar 27 22:07:54 EST 2006 

ARG... I've run into another roadblock here.  As far as delivering the
driver to the client XP machines, I'm still failing there.  However, a
far worse problem has come up.  A user without "local administrator
rights" to their workstation cannot be prompted to choose the driver
of a network printer.  The network printer must deliver the correct
driver to the client.  If I don't get the driver automatically
delivered to the client, the users will NOT be able to install this
printer on their own as they are not allowed to pick and choose the
driver to install for the printer.  This would mean I would have to
visit each and every workstation individually to install this
printer... YUCK.  This does not paint a pretty picture for me.  :(

Well, I've bought steak dinners for people who have shown me the way
before.  Anyone know how to shine this light for me and is interested
in a steak dinner, let me know.  I know some of you will work for
Bojangles, and that's cool too.  :)  I'm seeking someone who can teach
this black magic I'm for some reason unable to figure out.  Matt P,
are you one of those candidates??  :D

alright, goodnight for now and thanks!
David McD


On 3/23/06, David McDowell <turnpike420 at gmail.com> wrote:
> AND, you figure out WAY down the page that yes, root%xxxx is in fact
> asking for username/password  *sigh*  </more vent>
>
> I'm still stuck at the rpcclient part... I can get this info:
>
> [Windows NT x86]
> Printer Driver Info 3:
>        Version: [3]
>        Driver Name: [HP Color LaserJet 8500 PS]
>        Architecture: [Windows NT x86]
>        Driver Path: [\\CGIRB1003D\print$\W32X86\3\PSCRIPT5.DLL]
>        Datafile: [\\CGIRB1003D\print$\W32X86\3\HP_CLJ85.PPD]
>        Configfile: [\\CGIRB1003D\print$\W32X86\3\PS5UI.DLL]
>        Helpfile: [\\CGIRB1003D\print$\W32X86\3\PSCRIPT.HLP]
>
>        Dependentfiles: [\\CGIRB1003D\print$\W32X86\3\HPCJRRPS.DLL]
>        Dependentfiles: [\\CGIRB1003D\print$\W32X86\3\PSCRIPT.NTF]
>        Dependentfiles: [\\CGIRB1003D\print$\W32X86\3\HPCJRUI.DLL]
>        Dependentfiles: [\\CGIRB1003D\print$\W32X86\3\hpcabout.dll]
>        Dependentfiles: [\\CGIRB1003D\print$\W32X86\3\hpcstr.dll]
>        Dependentfiles: [\\CGIRB1003D\print$\W32X86\3\hpljps1.ini]
>        Dependentfiles: [\\CGIRB1003D\print$\W32X86\3\HPCLJX.HLP]
>
>        Monitorname: []
>        Defaultdatatype: []
>
> but the instructions from there which end up telling some indescript
> TDB database that the drivers exist with adddriver... wack.  I quit
> for today before I annoy the list!  :D
>
> Folks, this should be EASIER than this... *sigh*
>
> thanks for everything so far,
> David McD
>
>
>
> On 3/23/06, David McDowell <turnpike420 at gmail.com> wrote:
> > heh, OK, I figured out TURBO_XP is just a stupid hostname... :p
> >
> >
> > On 3/23/06, David McDowell <turnpike420 at gmail.com> wrote:
> > > Those instructions have yet to work for me but I'm trying to
> > > understand them... again... - - Also, they are convoluded and skip
> > > around too much and offer too many different ways in too many
> > > different places and one can only guess which path to follow.  The
> > > only thing I've changed in my approach so far is to use "HP Color
> > > LaserJet 8500 PS" so that my PDF creations can be color instead of
> > > black & white only.  These directions are making my head spin and I
> > > can't get a grasp on which direction to take.  ARGGGG!!!
> > >
> > > they have commands like:
> > >
> > > rpcclient -U'Danka%xxxx' -c \
> > >        'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP
> > >
> > > what the hell is TURBO_XP and what is -U'Dank%xxxx' -c supposed to be,
> > > machine, user%pass, strange swedish?  "bork bork bork!"
> > >
> > > Also, these docs seem to be dated May 31, 2003.  I say they might be
> > > dated. *sigh*
> > >
> > > frustrated,  :)
> > > David McD
> > > *sigh* </vent>
> > >
> > >
> > >
> > > On 3/22/06, Matt Pusateri <mpusateri at wickedtrails.com> wrote:
> > > > Okay so here is one of the downsides to RHEL/CentOS.  Samba is at
> > > > 3.0.21c as a stable release.  *Alot* of work has been done in samba
> > > > with respect to printers and the printing system.  You really need to
> > > > get to a newer version of Samba.
> > > >
> > > > So these directions don't work?  Usually the samba doc's are pretty
> > > > good, and their updated daily.
>
> they're (they are)  ;)  ;)
>
> > > >
> > > > http://us5.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html
> > > >
> > > >
> > > > Matt
> > > >
> > > > On Wed, March 22, 2006 8:20 pm, David McDowell wrote:
> > > > > (yup, still working on this as part of my total solution for samba PDF
> > > > > printer, got that part working w/ usernames as I wanted, will still
> > > > > post that info when I get through this)
> > > > >
> > > > > Scenario:  In a Windows XP client, when you attach to a Windows Server
> > > > > 2003 shared printer, the printer driver required for the client is
> > > > > automatically loaded on the client when you choose that shared
> > > > > printer, the user does not have to pick the correct printer driver.
> > > > > Everywhere I read claims Samba can deliver the same thing to Windows
> > > > > clients with its shared printers.
> > > > >
> > > > > What have I tried so far:  (work has me a bit scattered brained, so
> > > > > hopefully as I write this I'll recall everything I tried)
> > > > >
> > > > > I setup [printer$] hidden share which included the W32X86 path inside
> > > > > it and this contained the driver files for my printer driver.  I want
> > > > > to use the "HP LaserJet 4000 Series PS" driver (no particular reason
> > > > > except it is a familiar and readily available PS driver in Windows
> > > > > XP... meaning, it comes with the OS).  I need a PS driver on the
> > > > > client so the ps2pdf ghostscript function works in the samba print to
> > > > > PDF.  :)
> > > > >
> > > > > Accessing that hidden share at \\hostname\printers$ works fine from my
> > > > > XP client.  In the [pdfprinter] actual shared printer, we already know
> > > > > I use a print command to send that to the ps2pdf.  What I read tells
> > > > > me a LOT about pre Samba 2.2 which allowed you to use 'printer driver
> > > > > = blah' and 'printer driver location = fark' and discussions about a
> > > > > printers.def file etc.  I tried a LOT of combinations here but never
> > > > > got any one of them to work, and when I start the SMB service, it
> > > > > claims printer driver and printer driver location are unknown (as
> > > > > expected in Samba 3.10.x on CentOS 4.2 since some docs say it is
> > > > > depricated).  However, everything I kept reading said I could use
> > > > > those settings in the specific printer shares anyway.
> > > > >
> > > > > I'm at a loss.  I know some folks out there must have done this.  All
> > > > > of us want to use Linux and samba for sharing printers instead of
> > > > > Windows print servers right? ;)  When a user installs a network shared
> > > > > printer, they shouldn't have to choose the driver, the driver should
> > > > > install itself for them.  What's the secret that I'm missing!  :)
> > > > >
> > > > > thanks,
> > > > > David McD
> > > > > --
> > > > > TriLUG mailing list        :
> > > > > http://www.trilug.org/mailman/listinfo/trilug
> > > > > TriLUG Organizational FAQ  : http://trilug.org/faq/
> > > > > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> > > > TriLUG Organizational FAQ  : http://trilug.org/faq/
> > > > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> > > >
> > >
> >
>

More information about the TriLUG mailing list