Hello Vencel,
This issue is caused by a mismatch between NTFS permissions on the HDD and the share permissions. Even if “Everyone” has full control on the share, the NTFS security on the drive must also grant access to the same user or group. When you test locally, the server account context is used, which is why it works there but fails remotely.
Check the drive’s Properties > Security tab and ensure the specific user or group has at least Read permissions. Add the account explicitly rather than relying on “Everyone,” since newer Windows Server versions don’t include authenticated users in that group. Then verify the share permissions under Advanced Sharing > Permissions match the NTFS rights. The most restrictive setting always applies.
From the client, confirm authentication with net use \\servername\sharename /user:domain\username. If login fails, the account may not exist or be disabled. Also review SMB settings and firewall rules, as Windows Server 2025 enforces SMB signing/encryption that can block older clients. Event Viewer under Security and SMBServer logs will show if policy is rejecting the connection.
Aligning NTFS and share permissions, confirming authentication, and checking SMB policies should resolve the access denied error without using the administrator account.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
Harry.