@Steve_Dunthorne I had a previous customer that found a solution to this Windows issue. We were at our wits end on the machine side. Here is what this customer found:
“Changing the windows authentication policy to allow insecure guest logins allowed the network share to be mapped”
“…I did turn off the Enable Insecure Guest Logons again for security reasons and used the Connect using Different credentials to map the network drive drive. This, along with enabling SMB (and an assist from ChatGPT to find the default logon credentials, LOL) corrected the behavior.”
I will admit, this is a bit out of my depth, but I figured I would share it here, just in case it helped anyone else!