[Samba] smbsrv_reply_printwrite not returning a response causing the print job to be truncated to 124 bytes

[Rowland penny]

On 29/04/2021 07:45, Mateusz Mikołajczyk via samba wrote:
> yes, I'm aware that this protocol (and even this way of printing) is
> deprecated and believe me, I would like to move away from it :(
> unfortunetely that's the luxury I don't have.
>
> smb.conf is as following (lines proceeding with # removed for brevity,
> MINOLTA is the name of the CUPS printer (konica minolta)):
>
> ```
> [global]
>     workgroup = WORKGROUP
>     netbios name = SERVER
>     server string = SERVER
>     log file = /var/log/samba/log.%m
>     max log size = 1000
>     logging = file
>     panic action = /usr/share/samba/panic-action %d
>     server role = standalone server
>     obey pam restrictions = yes
>     unix password sync = yes
>     passwd program = /usr/bin/passwd %u
>     passwd chat = *Enter\snew\s*\spassword:* %n\n
> *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
>     pam password change = yes
>     map to guest = bad user
>
> [MINOLTA]
>     printer = MINOLTA
>     browseable = yes
>     printing = cups
>     path = /var/spool/samba
>     printable = yes
>     guest ok = yes
>     writable = yes
>     create mask = 0777
>
>     ntvfs handler = simple
>     aio read size = 0
>     aio write size = 0
>
>     strict sync = yes
>     sync always = yes
> ```
>
> p.s. it could be that this (i.e. synchronous reply with a 0xc1 packet and 3
> null bytes) was an undocumented feature available only in the xp server,
> because when I tried to connect the DOS client to a windows 10 machine (of
> course I enabled smb1 / cifs protocol first) the print job would be added
> to the spooler but would indefinetely show 'buffering'.
>
>

You are running Samba as a standalone server, what Samba binaries are 
you starting ?

Also, what Samba version are you using.

Rowland