A share that half the house can read and nobody can write is a permissions problem, not a network problem. Set the share and the NTFS side once, deliberately.
Create a local group for the people who should write, share the folder to that group only, then set **NTFS** permissions to match. Windows applies the **most restrictive** of the two.
A share has its own permission list, and so does the folder on disk. Access needs both, and the effective right is the stricter one. Confusing the two is why a folder is writable for one account and read-only for another.
Give each person a local account and put them all in a single group. Per-person accounts keep the audit trail readable and let you revoke access for one device without touching the rest.
net user family Pa55w0rd! /add
net localgroup smb-users /add
net localgroup smb-users family /addRight-click the folder, open **Properties > Sharing > Advanced Sharing**, tick the box and open **Permissions**. Remove **Everyone** and add the group with **Change** so members can write and delete.
Share name: share
Permissions: smb-users -> ChangeOn the **Security** tab disable inheritance, convert the inherited entries, then add the same group with **Modify**. Without this step the share says yes and the folder says no, which reads as a random failure from the client.
Network discovery and file sharing must be on for the **Private** profile. On a **Public** profile Windows blocks both, and a home network ends up labelled public after many router changes.
Settings > Network & internet > Ethernet > Network profile typeMap the share with credentials so it reconnects after a reboot, then test by writing a file from the client. Browsing the folder in Explorer proves less than one successful write.
net use Z: \\HOSTNAME\hare /user:HOSTNAME amily /persistent:yesThe NTFS tab is stricter. Open the Security tab and check the group's effective rights on that exact folder, not on the parent.
Network discovery is off or the profile is Public. Set the profile to Private and allow File and Printer Sharing in the firewall.
The mapping was made without stored credentials. Recreate it with /persistent:yes and tick Remember my credentials in the dialog.
The link negotiated at 100 Mbit or Wi-Fi is in power saving. Check the adapter speed and use Ethernet for large copies.
No. SMB1 is disabled for good reasons and every Windows 10 and 11 build speaks SMB2 or 3.
Only by allowing insecure guest logons, which weakens the whole network. Use accounts instead.
Stop sharing the folder in **Advanced Sharing**, then remove the group and the local accounts you created. The files themselves stay where they are.
Free · no account needed · tracks your progress