I can't even get cupsaddsmb to work right. I followed the configuration instructions from the documentation, and my smb.conf matches what the cupsaddsmb man page says. I am getting extremely frustrated with this and not being able to allow clients to download drivers from Samba. With cupsaddsmb, this is the error I am receiving when it gets to this point, over and over: Running command: rpcclient localhost -N -A /tmp/cupsDdRS7Y -c 'adddriver "Windows NT x86" "pw003:pscript5.dll:pw003.ppd:ps5ui.dll:pscript.hlp:NULL:RAW:pscript5.dll,pw003.ppd,ps5ui.dll,pscript.hlp,pscript.ntf,cups6.ini,cupsps6.dll,cupsui6.dll"' result was WERR_INVALID_PARAM What in the heck is going on? Why can I not get any of this to work?
This is the error with verbose output: pc_api_pipe: got frag len of 28 at offset 0: NT_STATUS_OK rpc_api_pipe: host localhost returned 8 bytes. spoolss_AddPrinterDriver: struct spoolss_AddPrinterDriver out: struct spoolss_AddPrinterDriver result : WERR_INVALID_PARAM result was WERR_INVALID_PARAM On Sep 25, 2012, at 5:59 PM, Kristofer wrote:> I can't even get cupsaddsmb to work right. I followed the configuration instructions from the documentation, and my smb.conf matches what the cupsaddsmb man page says. > > I am getting extremely frustrated with this and not being able to allow clients to download drivers from Samba. > > With cupsaddsmb, this is the error I am receiving when it gets to this point, over and over: > > Running command: rpcclient localhost -N -A /tmp/cupsDdRS7Y -c 'adddriver "Windows NT x86" "pw003:pscript5.dll:pw003.ppd:ps5ui.dll:pscript.hlp:NULL:RAW:pscript5.dll,pw003.ppd,ps5ui.dll,pscript.hlp,pscript.ntf,cups6.ini,cupsps6.dll,cupsui6.dll"' > result was WERR_INVALID_PARAM > > What in the heck is going on? Why can I not get any of this to work? > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
On Tue, 2012-09-25 at 17:59 -0500, Kristofer wrote:> I can't even get cupsaddsmb to work right. I followed the > configuration instructions from the documentation, and my smb.conf > matches what the cupsaddsmb man page says. > > I am getting extremely frustrated with this and not being able to > allow clients to download drivers from Samba. > > With cupsaddsmb, this is the error I am receiving when it gets to this > point, over and over: > > Running command: rpcclient localhost -N -A /tmp/cupsDdRS7Y -c > 'adddriver "Windows NT x86" > "pw003:pscript5.dll:pw003.ppd:ps5ui.dll:pscript.hlp:NULL:RAW:pscript5.dll,pw003.ppd,ps5ui.dll,pscript.hlp,pscript.ntf,cups6.ini,cupsps6.dll,cupsui6.dll"' > result was WERR_INVALID_PARAM > > What in the heck is going on? Why can I not get any of this to work?Even if you could get it to work, is this really what you want? Printing with native Windows drivers is the more normal pattern these days, rather than printing postscript and getting CUPS to do the conversion. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org
Hello Kristofer, please try it first without the cups6-drivers. Use only the original MS-Drivers. I am using Samba 3.4 since years and it is working beautiful. regards Franz
Possibly Parallel Threads
- Samba4 CUPS: NT_STATUS_ACCESS_DENIED opening remote file
- Update from 3.5.10 to 3.6.23 broke cupsaddsmb
- Samba-Cups: all works except browsing when printer is not defined in smb.conf
- Installing windows drivers into print$ on OS X 10.5 Leopard
- cupsaddsmb error: cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received