I am trying to configure a shared folder in a PC with windows 11 to store csv files from a MP370 panel.

To test if I can access to the shared folder, in the panel, in the file explorer, I enter in the network folder and in the address I write the path of the shared folder: \\PlcServer\csv

At this point, I am prompted for the credentials. I set the user that I have created in the PC and I set the password. I check the checkbox to update the default credentials. But it seems it doesn't save it, because I am promted one and another time.

it is similar to the problem that this used had: https://support.industry.siemens.com/forum/es/en/posts/logon-to-network-server/32063

Also, I am following this guide: https://support.industry.siemens.com/cs/de/en/view/13336639

Anyway, my problem is not configurating the PC, I enabled SMB 1.0, I create a user in the PC called SIemens that has permissions to modify in the sharing options and it has modify permissions in the security options of the folder. Also de panel can find the folder. The problem is when I am prompted to set the credentials, that are not accepted for some reason.

Thanks so much.

EDIT: in the server, in the events viewer, if I see the events of the SMB server, I see this error:

SMB Session Authentication Failure

Client Name: \\192.168.1.201
Client Address: 192.168.1.201:1026
User Name: eeee
Session ID: 0x0
Status: The attempted logon is invalid. This is either due to a bad username or authentication information. (0xC000006D)
SPN: session setup failed before the SPN could be queried
SPN Validation Policy: SPN optional / no validation

Guidance:

You should expect this error when attempting to connect to shares using incorrect credentials.

This error does not always indicate a problem with authorization, but mainly authentication. It is more common with non-Windows clients.

This error can occur when using incorrect usernames and passwords with NTLM, mismatched LmCompatibility settings between client and server, an incorrect service principal name, duplicate Kerberos service principal names, incorrect Kerberos ticket-granting service tickets, or Guest accounts without Guest access enabled