I have this folder on my server that I'm trying to share. Normally, I right-click, go to properties, set it to share, and ensure that 'Everyone' has full access. Then I manage NTFS rights separately on the security tab. I wanted to test a scheduled task user's credentials that have NTFS rights for this folder but accidentally clicked 'Add a network location' instead of 'Add mapped drive' when mapping the drive. To my surprise, it let me access the shared folder and modify everything without entering any credentials. How is this bypassing NTFS rights?
5 Answers
It sounds like you're accessing the network share using your own logged-in credentials, which probably have permission to that share. When you clicked 'Add a network location,' it used your current credentials automatically. If you want to test your scheduled task user's access, try mapping a drive and entering their credentials directly, like this: `net use Z: \fileserver.domain.comsharename /user:domainschdtaskuser`. This way, you can properly verify their permissions.
If you're on a domain, your credentials are likely being passed through automatically, allowing you access. If you're not in a domain but have previously authenticated with the server, those credentials can still be valid until you log off. As for the shared folder, the critical part is ensuring you don’t set the share permissions too broadly—like using 'Everyone,' which can open up security risks.
For security reasons, avoid giving 'Everyone' access. It’s better to narrow it down to user groups that actually need it. If you're worried about subfolder permissions, remember those are managed differently than share permissions, so keep an eye on NTFS rights as well. It's smarter to not mix share and NTFS permissions without clear control.
It's usually best to keep NTFS permissions as they are. Set restrictions at the Sharing tab, since they provide visibility on who can access the shared resource without diving deep into NTFS settings. Just remember, share permissions kick in when accessing through the share name.
I highly recommend you change 'Everyone' to 'Authenticated Users' for share permissions. Using 'Everyone' can cause vulnerabilities, especially if you have accounts that shouldn't have full control. It's a good practice to create a specific group for file share permissions instead.

Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures