Running Debian Sarge, but compiled 3.0.21a from sources. trying to add a printer driver, here is what I keep getting: rpcclient -U'root%xxxxx' -c 'adddriver "Windows NT x86" "Phaser01:\ tkph7401.dll:\ tkph7401.ppd:\ tekinst.dll:\ adobeps4.hlp:\ NULL:\ RAW:\ :adfonts.mfm,adobeps4.drv,adobeps4.hlp,apple380.spd,captport.dll,iconlib.dll,licagrmt.pdf,lpt.vxd,psmon.dll,readme.doc,tek95adb.inf,tekinst.dll,tkph7401.dll,tkph7401.ppd"' WINDA Connecting to host=WINDA resolve_lmhosts: Attempting lmhosts lookup for name WINDA<0x20> resolve_wins: Attempting wins lookup for name WINDA<0x20> resolve_wins: using WINS server 127.0.0.1 and tag '*' Got a positive name query response from 127.0.0.1 ( 192.168.2.1 ) Connecting to 192.168.2.1 at port 445 Doing spnego session setup (blob length=16) server didn't supply a full spnego negprot Got challenge flags: Got NTLMSSP neg_flags=0x608a0235 NTLMSSP: Set final flags: Got NTLMSSP neg_flags=0x60080215 NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x60080215 rpc_pipe_bind: Remote machine WINDA pipe \lsarpc fnum 0x74a8 bind request returned ok. lsa_io_sec_qos: length c does not match size 8 rpc_pipe_bind: Remote machine WINDA pipe \spoolss fnum 0x74a9 bind request returned ok. result was WERR_BADFILE This bug seems very similar, if not the same as reported by bug #3396
Created attachment 1806 [details] Errormessages from cupsaddsmb This ist the output of a cupsaddsmb call. This is for the Versieon 3.0.14a and Version 3.0.21b too. I hope, that samba goes not so far to windows, that samba take the bad site of windows too ;)
Created attachment 1807 [details] Debuglevel 5 Output of rpcclient with the comman set driver This ist the Output from rpcclient of the version 3.0.14a and 3.0.21b set driver command
These are two different bugs. The original bug is mostly caused by not copying the files to the correct location in [print$] on the server before issueing the 'adddriver call'. The second bug is an authorization issue. Without a level 10 debug log from the server (not client), I can't give more information. But it is very doubtful that this a source level bug.
no response. Closing.