I've found that some embedded devices have older CIFS clients, which can only talk over SMB1. So, you can adjust your server to allow it, or look for another file transport. Kris Lou klou at themusiclink.net On Wed, Sep 9, 2020 at 3:16 PM Jeremy Allison via samba < samba at lists.samba.org> wrote:> On Wed, Sep 09, 2020 at 02:35:28PM -0700, Peter Pollock via samba wrote: > > I have two photocopiers. > > > > Both have the facility to can to a file on a file server via smb. > > > > Both configured identically. > > > > One can write to a samba share, the other cannot (same server, same > share) > > > > I'm searching for a log somewhere that might show me why the write is > > failing but I cannot see anything. > > > > Which log file on my fileserver would show me if the server is rejecting > > the connection, please? > > From the smb.conf man page: > > log file (G) > > This option allows you to override the name of the Samba log > file (also known as the debug file). > > This option takes the standard substitutions, allowing you to > have separate log files for each user or machine. > > No default > > Example: log file = /usr/local/samba/var/log.%m > > Set it as so, to get a separate log file for the > incoming machine name. > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
The other thing is NTLMv2, also required by default in modern Samba versions. Andrew Bartlett On Wed, 2020-09-09 at 15:39 -0700, Kris Lou via samba wrote:> I've found that some embedded devices have older CIFS clients, which > can > only talk over SMB1. So, you can adjust your server to allow it, or > look > for another file transport. > > Kris Lou > klou at themusiclink.net > > > On Wed, Sep 9, 2020 at 3:16 PM Jeremy Allison via samba < > samba at lists.samba.org> wrote: > > > On Wed, Sep 09, 2020 at 02:35:28PM -0700, Peter Pollock via samba > > wrote: > > > I have two photocopiers. > > > > > > Both have the facility to can to a file on a file server via smb. > > > > > > Both configured identically. > > > > > > One can write to a samba share, the other cannot (same server, > > > same > > > > share) > > > > > > I'm searching for a log somewhere that might show me why the > > > write is > > > failing but I cannot see anything. > > > > > > Which log file on my fileserver would show me if the server is > > > rejecting > > > the connection, please? > > > > From the smb.conf man page: > > > > log file (G) > > > > This option allows you to override the name of the Samba > > log > > file (also known as the debug file). > > > > This option takes the standard substitutions, allowing > > you to > > have separate log files for each user or machine. > > > > No default > > > > Example: log file = /usr/local/samba/var/log.%m > > > > Set it as so, to get a separate log file for the > > incoming machine name. > > > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: https://lists.samba.org/mailman/options/samba > >-- Andrew Bartlett https://samba.org/~abartlet/ Authentication Developer, Samba Team https://samba.org Samba Developer, Catalyst IT https://catalyst.net.nz/services/samba
You're geniuses one and all! That looks to have fixed the problem! At a later date I'll try to work out how to do it via ftp so I can avoid the smb1 protocol altogether, but for now I have a working solution so THANK YOU! On Wed, Sep 9, 2020, 3:45 PM Andrew Bartlett via samba < samba at lists.samba.org> wrote:> The other thing is NTLMv2, also required by default in modern Samba > versions. > > Andrew Bartlett > > On Wed, 2020-09-09 at 15:39 -0700, Kris Lou via samba wrote: > > I've found that some embedded devices have older CIFS clients, which > > can > > only talk over SMB1. So, you can adjust your server to allow it, or > > look > > for another file transport. > > > > Kris Lou > > klou at themusiclink.net > > > > > > On Wed, Sep 9, 2020 at 3:16 PM Jeremy Allison via samba < > > samba at lists.samba.org> wrote: > > > > > On Wed, Sep 09, 2020 at 02:35:28PM -0700, Peter Pollock via samba > > > wrote: > > > > I have two photocopiers. > > > > > > > > Both have the facility to can to a file on a file server via smb. > > > > > > > > Both configured identically. > > > > > > > > One can write to a samba share, the other cannot (same server, > > > > same > > > > > > share) > > > > > > > > I'm searching for a log somewhere that might show me why the > > > > write is > > > > failing but I cannot see anything. > > > > > > > > Which log file on my fileserver would show me if the server is > > > > rejecting > > > > the connection, please? > > > > > > From the smb.conf man page: > > > > > > log file (G) > > > > > > This option allows you to override the name of the Samba > > > log > > > file (also known as the debug file). > > > > > > This option takes the standard substitutions, allowing > > > you to > > > have separate log files for each user or machine. > > > > > > No default > > > > > > Example: log file = /usr/local/samba/var/log.%m > > > > > > Set it as so, to get a separate log file for the > > > incoming machine name. > > > > > > -- > > > To unsubscribe from this list go to the following URL and read the > > > instructions: https://lists.samba.org/mailman/options/samba > > > > -- > Andrew Bartlett https://samba.org/~abartlet/ > Authentication Developer, Samba Team https://samba.org > Samba Developer, Catalyst IT > https://catalyst.net.nz/services/samba > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
Just leaving a note in this thread that might help other people who find it: I had some older clients at one point and I had to allow older levels of authentication (NTLMv1) as well as older levels of the SMB protocol using ntlm auth = yes On 10/09/2020 8:45 am, Andrew Bartlett via samba wrote:> The other thing is NTLMv2, also required by default in modern Samba > versions. > > Andrew Bartlett > > On Wed, 2020-09-09 at 15:39 -0700, Kris Lou via samba wrote: >> I've found that some embedded devices have older CIFS clients, which >> can >> only talk over SMB1. So, you can adjust your server to allow it, or >> look >> for another file transport. >> >> Kris Lou >> klou at themusiclink.net >> >> >> On Wed, Sep 9, 2020 at 3:16 PM Jeremy Allison via samba < >> samba at lists.samba.org> wrote: >> >>> On Wed, Sep 09, 2020 at 02:35:28PM -0700, Peter Pollock via samba >>> wrote: >>>> I have two photocopiers. >>>> >>>> Both have the facility to can to a file on a file server via smb. >>>> >>>> Both configured identically. >>>> >>>> One can write to a samba share, the other cannot (same server, >>>> same >>> share) >>>> I'm searching for a log somewhere that might show me why the >>>> write is >>>> failing but I cannot see anything. >>>> >>>> Which log file on my fileserver would show me if the server is >>>> rejecting >>>> the connection, please? >>> From the smb.conf man page: >>> >>> log file (G) >>> >>> This option allows you to override the name of the Samba >>> log >>> file (also known as the debug file). >>> >>> This option takes the standard substitutions, allowing >>> you to >>> have separate log files for each user or machine. >>> >>> No default >>> >>> Example: log file = /usr/local/samba/var/log.%m >>> >>> Set it as so, to get a separate log file for the >>> incoming machine name. >>> >>> -- >>> To unsubscribe from this list go to the following URL and read the >>> instructions: https://lists.samba.org/mailman/options/samba >>>