@MSGID:
<20230721182116.b867a490ade87373e2b43f63@gmail.com> 3acd0aa9
@REPLY: 1@dont-email.me> 349736bf
@REPLYADDR pinnerite <pinnerite@gmail.com>
@REPLYTO 2:5075/128 pinnerite
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<20230721182116.b867a490ade87373e2b43f63@gmail.com>
<20230717210521.86130f8c4336fbd2a7d1c42c@gmail.com>1@dont-email.me
><20230718073514.e66db53de5f32efce7feaf32@gmail.com> e><20230718182649.ba3a2765fc63dd40c286024a@gmail.com><20230720185955.e193a61cb73
954c940673a34@gmail.com>1@dont-email.me>
@TZUTC: 0100
@TID: FIDOGATE-5.12-ge4e8b94
On Fri, 21 Jul 2023 10:39:19 -0400
"Jonathan N. Little" <lws4art@gmail.com> wrote:

> pinnerite wrote:
 > > Windows 10 seems to have cleared itself. I decided to
overwrite smb.conf with a version that I knew had been reliable and tested
again.
> > 
> > Bingo! Both XP and Win-10 are accessing the Linux shares again.
> 
> testparm -d might have helped.
> 
> Also "diff non_working_smb.conf backup_smb.conf" might be informative
> 
> -- 
> Take care,
> 
> Jonathan

You`re right. I haven`t used diff for over 20 years!  :)
--- Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
 * Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441