Hello @Snookred
Because \Jupiter\Temp works from the same client while \Jupiter\Work returns “You do not have permission”, SMB connectivity, computer discovery, and the firewall are already working. The difference is most likely the permissions applied to the physical W:\ drive.
The screenshot shows only the share permission for Work. Windows also evaluates the file-system permissions under Properties > Security. Access must be allowed at both levels; a share-level Everyone: Read entry cannot override a restrictive or missing NTFS permission.
On Jupiter, compare the following properties for W:\ and the working Temp drive:
- Right-click W:\ and select Properties > Security.
- Confirm that the user accessing the share or a group containing that user has:
- Read & execute, List folder contents, and Read for read-only access; or
- Modify for read/write access.
- Check Advanced > Effective Access for the account being used from Mars.
- Check for explicit Deny entries and whether the permissions apply to this folder, subfolders, and files. Windows permissions can be inherited by files and subfolders, but only when the relevant inheritance settings apply.
You can inspect both permission layers from an elevated PowerShell window on Jupiter without changing anything:
Get-SmbShareAccess -Name "Work"
icacls W:\
Get-SmbShareAccess displays the SMB share ACL, while icacls displays the file-system DACL applied to the drive. Compare the results with the working Temp share.
Your screenshot currently grants Everyone only Read at the share level. If write access is required, both layers must permit it, for example, Change on the share and Modify on the physical folder. Do not grant Full Control unless users need to change permissions or ownership.
For a safer and simpler configuration, consider sharing a dedicated folder such as W:\Shared instead of the entire drive root, then assign the intended account at both:
- Properties > Sharing > Advanced Sharing > Permissions
- Properties > Security
Microsoft’s documented sharing procedure configures these two permission locations separately.
The message about people without accounts doesn’t prove that guest access is being used successfully. However, because the Temp share already works from the same client session, changing SMB versions, enabling SMB1, or modifying insecure guest-access policy isn’t justified by the supplied evidence.
References:
- File sharing over a network in Windows
- Windows access-control overview
- Get-SmbShareAccess
- icacls command reference
Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.