I'm having repeated problems sharing folders between Windows 11 Pro workstations on the same network. The networks are set to Private, and network discovery and file sharing are enabled. I've tried turning password-protected sharing on and off, enabling insecure guest logons through Group Policy, and disabling digitally signed SMB communications, but I still frequently see errors such as "Network path not found" or "Your folder cannot be shared."
The computers can usually ping one another and sometimes appear under File Explorer's Network section. Entering the target computer's IP address occasionally brings up a username and password prompt and then allows access, but other times nothing happens at all. The shares are mostly being hosted directly from workstations, including folders under the Public user directory. All users are being encouraged to use passwords.
What is the most reliable way to troubleshoot and configure file sharing on Windows 11? Would a NAS or central file server be a better approach for these small business locations?
2 Answers
For a small number of occasional files, workstation shares can work, but they become difficult to maintain as more computers and users are added. A NAS or central file server gives you one place to manage permissions, user accounts, backups, and shared folders. You can then map the required shares through a login script or centralized configuration instead of troubleshooting every workstation individually.
Windows 11 has tightened SMB security, so guest access and older sharing methods are increasingly unreliable. If you must use workstation-to-workstation sharing, use named user accounts with passwords, verify both share permissions and NTFS permissions, confirm the File and Printer Sharing firewall rules are enabled, and connect using a consistent path such as \ComputerNameShare or \IP-addressShare. Avoid relying on the Network view, since discovery there does not prove that SMB access is working.
Some environments have restored compatibility by enabling AllowInsecureGuestAuth and disabling SMB signing requirements, but those settings reduce security and should only be used when the device or application genuinely requires guest or legacy access. A properly configured NAS using authenticated SMB access is generally safer and more dependable than weakening security on every workstation.
I had already tried the equivalent Group Policy settings, but the results were inconsistent. Moving the shares to a NAS should avoid most of the guest-access and workstation-dependency problems.
That’s the direction I’m leaning. One location has enough shared files to justify a NAS, while the other mainly needs a simple shared folder for receipts and fuel records.