[Samba] rpcclient enumdrivers 3 times out on NT drivers

[Ronan Waide]

This is puzzling me (and hampering some work, slightly):

NT4SP6 + full updates server, with some printers attached.

"rpcclient -U admin%pass enumdrivers 2" server gives me a list of stuff
like this:

[Windows 4.0]
Printer Driver Info 2:
        Version: [0]
        Driver Name: [HP LaserJet 5Si PCL 5e]
        Architecture: [Windows 4.0]
        Driver Path: [\\SERVER\print$\WIN40\0\ADOBEPS4.DRV]
        Datafile: [\\SERVER\print$\WIN40\0\HPLJ5SI2.PPD]
        Configfile: [\\SERVER\print$\WIN40\0\ADOBEPS4.DRV]
...
...
...
[Windows NT x86]
Printer Driver Info 2:
        Version: [2]
        Driver Name: [Lexmark Optra R Plus Series]
        Architecture: [Windows NT x86]
        Driver Path: [\\SERVER\print$\W32X86\2\RASDD.DLL]
        Datafile: [\\SERVER\print$\W32X86\2\OPTRA.DLL]
        Configfile: [\\SERVER\print$\W32X86\2\RASDDUI.DLL]


"rpcclient -U admin%pass enumdrivers 3 server", however, zips through
the Windows 4.0 stuff and then sits there before eventually giving
this:
[Windows 4.0]
Printer Driver Info 3:
        Version: [0]
        Driver Name: [HP LaserJet 5Si PCL 5e]
        Architecture: [Windows 4.0]
        Driver Path: [\\SERVER\print$\WIN40\0\ADOBEPS4.DRV]
        Datafile: [\\SERVER\print$\WIN40\0\HPLJ5SI2.PPD]
        Configfile: [\\SERVER\print$\WIN40\0\ADOBEPS4.DRV]
        Helpfile: [\\SERVER\print$\WIN40\0\HPLJ5SI2.HLP]

        Dependentfiles: [\\SERVER\print$\WIN40\0\hplj5si2.ppd]
        Dependentfiles: [\\SERVER\print$\WIN40\0\hplj5si2.hlp]
        Dependentfiles: [\\SERVER\print$\WIN40\0\adobeps4.drv]
        Dependentfiles: [\\SERVER\print$\WIN40\0\pscript.ini]
        Dependentfiles: [\\SERVER\print$\WIN40\0\psmon.dll]
        Dependentfiles: [\\SERVER\print$\WIN40\0\iconlib.dll]
        Dependentfiles: [\\SERVER\print$\WIN40\0\fonts.mfm]

        Monitorname: [PostScript Language Monitor]
        Defaultdatatype: []

cli_pipe: return critical error. Error was Call timed out: server did not respond after 10000 milliseconds
cli_pipe: return critical error. Error was Call timed out: server did not respond after 10000 milliseconds
cli_pipe: return critical error. Error was Call timed out: server did not respond after 10000 milliseconds
cli_pipe: return critical error. Error was Call timed out: server did not respond after 10000 milliseconds
result was NT_STATUS_UNSUCCESSFUL

I'm trying to hack up a printer cloning script that grabs all the
driver files and bits for a printer using enumdrivers and sticks them
onto another server using adddriver, addprinter, etc. Obviously the
above failure hampers that notion somewhat. Is this a flaw in
rpcclient or in the Windows box?

Cheers,
Waider.
-- 
waider at waider.ie / Yes, it /is/ very personal of me.

caitlin says, "climbing satisfies 2 apparent needs of mind: bashing my knees
    and shoe fetishism"