@MSGID: 1@dont-email.me> 349736bf
@REPLY:
<20230720185955.e193a61cb73954c940673a34@gmail.com> 6701a224
@REPLYADDR Jonathan N. Little <lws4art@gmail.com>
@REPLYTO 2:5075/128 Jonathan N. Little
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@RFC-References:
<20230717210521.86130f8c4336fbd2a7d1c42c@gmail.com> 1@dont-email.me>
<20230718073514.e66db53de5f32efce7feaf32@gmail.com> 1@dont-email.me>
<20230718182649.ba3a2765fc63dd40c286024a@gmail.com> <20230720185955.e193a61cb73954c940673a34@gmail.com>
@TZUTC: -0400
@PID: Mozilla/5.0 (Windows NT 10.0; Win64; x64;
rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.16
@TID: FIDOGATE-5.12-ge4e8b94
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
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
 --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.16
 * Origin: LITTLE WORKS STUDIO (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