Sujet : Re: SAMBA Problems
De : tnp (at) *nospam* invalid.invalid (The Natural Philosopher)
Groupes : comp.os.linux.miscDate : 18. Feb 2025, 10:54:27
Autres entêtes
Organisation : A little, after lunch
Message-ID : <vp1lcj$1kr74$6@dont-email.me>
References : 1 2 3 4 5
User-Agent : Mozilla Thunderbird
On 18/02/2025 07:59, c186282 wrote:
On 2/18/25 2:43 AM, Lawrence D'Oliveiro wrote:
On Tue, 18 Feb 2025 01:44:13 -0500, c186282 wrote:
>
On 2/18/25 1:06 AM, Lawrence D'Oliveiro wrote:
>
Turn on some more of the server-side logging options, to see if that
gives some clues.
>
Worth a try.
>
Another tip: get better names for your log files with something like this:
>
log file = /var/log/samba/log.%I-%R
>
That puts the client IP address and the protocol version they’re using
into the log file name. I have found this useful for spotting patterns in
which clients are having trouble.
Noted.
There are of course other fields you can include in the name.
The typical problem with logs is TOO MANY fields.
Can't sort the wheat from the chaff.
SAMBA isn't anything NEW - it SHOULDN'T be this
difficult. High success a few years ago, now crap.
SOMETHING changed but I can't pin it down yet.
PROBABLY some "security enhancement", poorly
documented. It ought to Just Work.
Indeed. I think it is probably a trivial configuration issue that has slipped through.
But it is FOSS., Suck it up and delve deep or install M$hit
-- “Those who can make you believe absurdities, can make you commit atrocities.”― Voltaire, Questions sur les Miracles à M. Claparede, Professeur de Théologie à Genève, par un Proposant: Ou Extrait de Diverses Lettres de M. de Voltaire