search for: smbsplopen

...zone is UTC-4.0 Password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 1.9.18p10] security=share smb: \> print test.txt ERRDOS - ERRnoaccess (Access denied.) opening printer for test.txt smb: \> quit Examining /var/log/smb (at debug level 10) reveals difficulty with the file: switch message SMBsplopen (pid 168) become_user uid=(0,65534) gid=(65534,65534) chdir to /var/spool/lpd/lp is_in_path: test.txt.a00168 is_in_path: no name list. unix_clean_name [test.txt.a00168] calling open_file with flags=0x1 flags2=0x240 mode=0600 Allocated new file_fd_struct 0, dev = ffffffff, inode = ffffffff Error ope...

...S - - debuglevel=3 returns the following error message on the linux console when 7 jobs are spooled in the print queue: print_job_start: Queue p13113 number of jobs (51) larger than max printjobs per queue (50) error string = no space left on device error packet at smbd/reply.c(3041) cmd=192 (SMBsplopen) NT_STATUS_DISK_FULL but there's only 7 jobs in the queue. Release 3.0.7 does not fix this It seems to be an issue in the way Samba calculate the number of jobs that are in the print queue ? The reason why i am testing this is because one of my customer prints A LOT ( over 2 thousand...

...rompt. But if we submit jobs one after the other( 2 or 3 seconds delay) the error won't come and no loss of data also. I want to know why this error occurs. As per the error code mapping it says RPC context mismatch. I'm confused how context mismatch happened even though SMBsplclose and SMBsplopen are having same contexts(as i can see in logs). This can be reproduced everytime when 2 or more jobs are submitted simultaneously from windows command prompt. (CMD prompt: copy filename \\IPaddress\Print) open two command prompts and execute above on one and use different filename on another one)...

...er the other( 2 or 3 seconds delay) the > error won't come and no loss of data also. > > I want to know why this error occurs. > > As per the error code mapping it says RPC context mismatch. > > I'm confused how context mismatch happened even though SMBsplclose and > SMBsplopen are having same contexts(as i can see in logs). > > This can be reproduced everytime when 2 or more jobs are submitted > simultaneously from windows command prompt. > (CMD prompt: copy filename \\IPaddress\Print) > open two command prompts and execute above on one and use different &...

...file stdin-1234 I compared the 2.0.7 source with the 1.9.18 source and found that the cmd_print procedure has changed significantly. In clientgen.c, the cli_open procedure has the following statement : CVAL(cli->outbuf,smb_com) = SMBopenX I changed that to CVAL(cli->outbuf,smb_com) = SMBsplopen; and the ERRaccess error disappeared. It is my guess that the Netgear print server does not support the SMBopenX file SMB commands, but does support the SMBspl print spool SMB commands. I changed the SMBclose command to SMBsplclose in cli_close and the SMBwriteX command in cli_issue_write to...

..._socket(5,57) wrote 57 got message type 0x0 of len 0x2f 1998/10/13 15:35:12 Transaction 10 of length 51 size=47 smb_com=0xc0 smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=24 smb_flg2=3 smb_tid=39 smb_pid=51966 smb_uid=100 smb_mid=512 smt_wct=2 smb_vwv[0]=0 (0x0) smb_vwv[1]=1 (0x1) smb_bcc=8 switch message SMBsplopen (pid 8200) become_user uid=(0,1011) gid=(1011,1011) chdir to /var/spool/samba is_in_path: WILLI.oF8200 is_in_path: no name list. unix_clean_name [WILLI.oF8200] calling open_file with flags=0x1 flags2=0x600 mode=0644 Allocated new file_fd_struct 0, dev = ffffffff, inode = ffffffff Error opening file...

Hello, I've got a problem with printing on a Windows 2K box. Printing from that box to a samba server via the normal print mechanism works fine. The problem is when the person needs to print to a lpt port. The capture succeeds, but when the file is copied to lpt2 it never gets printed. There are other machines that can do the capture and copy to the lpt port but they are Win 9x. The