[Samba] cli_pipe: return critical error. Error was Call returnedzero byte (EOF), hilfe!

[Dragan Krnic]

Hi Kurt,

I've read the new document. It's a very fine piece of
technical documentation. However, it doesn't help me 
in the present predicament. Going now by this book
I'm only getting more frustrated. I'm stuck!

For example adding driver with rcpclient invariably
ends in "Segmentation fault" (Signal 11) immediately
after pop_sec_ctx, whose push counterpart was invoked
before a long series of opening and closing all normal
files in W32X86/3. This is the command I used:

rpcclient -d 4 -Uroot -c 'adddriver \
"Windows NT x86" \
"lp:\
lexpsnt3.dll:\
OPC720.PPD:\
LEXPSNTU.DLL:\
LEXPSNT.HLP:\
NULL:\
LEXPSLNG.DLL,LEXDRVX.DLL,LEXFNTRC.DLL,LEXPSHOW.HLP,\
LEXPSNT.CNT,PTGUIW32.DLL,PTRESW32.DLL,PTAPIW32.DLL,\
LEXMV95.HLP,DRVNPANT.DLL,LEXDRVIN.EXE,LEXPSNT.ALL,\
OPTRASBM.DLL,SC1275BM.DLL,K1220BM.DLL,OC1200BM.DLL,\
OC40BM.DLL,OC45BM.DLL,E855BM.DLL,W810BM.DLL,\
W820BM.DLL,M410BM.DLL,T61XBM.DLL,T62XBM.DLL,\
C710BM.DLL,C720BM.DLL,C750BM.DLL,C910BM.DLL,\
E32XBM.DLL,LMPCLTHK.DLL,LEXCFI.DLL,LEXEDF.DLL,\
LEXPPDS.ZIP,PTZIPW32.DLL,LEXUNST.ZIP"\
' p90

Cheers
Dragan

>> I tried to explain my problem to you at Göttingen
>> but it looks like I'm the only one who gets this
>> error.
>> 
>> I've just reinstalled my box with SuSE 8.2, kernel
>> 2.4.20-62, samba 2.2.8a, and cups 1.1.18, moved all 
>> config files, databases, scripts and jobs to it and
>> it looks like samba has become even better and 
>> faster. No one noticed anything wrong except I just 
>> can't come to terms with cups. I hoped my problem 
>> would be gone with the new installation but it 
>> wouldn't.
>> 
>> I've gone strictly according to the book, your
>> "Printing with CUPS (Samba 2.2.x and 3.0)", which
>> I picked up at Samba Experience,
>
>Please get yourself the updated version from
>
>   http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/
>
>It contains a lot more material on that question,
>including how to do it all manually with rpcclient.
>
>> but I still get
>> the same buggy result NT_STATUS_UNSUCCESSFUL when
>> cupsaddsmb executes adddriver for "Windows NT x86"
>> and "Windows 4.0" as well as when it finally does
>> the set driver. Here is a slightly edited log:
>
>Sorry, I don't have time right now to look thru that 
>log in detail. But probably I will tonight, in which 
>case you will find s.th. in your mailbox tomorrow 
>morning...
>
>Cheers,
>Kurt


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005