Hi Duy,
What you are seeing is almost always the client sending domain credentials to a workgroup server, which that server cannot validate. On the Windows 11 25H2 PC, authenticate explicitly with the server's local account.
When the Windows Security prompt appears, select More choices, then Use a different account. In User name, type 192.168.1.10\localuser replacing localuser with the local account that exists on the Windows 11 24H2 file server. Enter that account's password, optionally check Remember my credentials, then select OK.
If the prompt keeps pre filling LSPACK\user or the sign‑in still fails, open Start and type Credential Manager, open Windows Credentials, remove any saved entry for 192.168.1.10 or the server name, then retry with 192.168.1.10\localuser and its password.
This forces NTLM to evaluate against the server's local SAM instead of the domain and typically resolves the exact error in your screenshot. Please try this and tell me the result. If it does not work, I will walk you through the next step.