Solved

W2012 R2 permission question

Posted on 2016-09-19
4
38 Views
Last Modified: 2016-09-22
I have an application that has a setting to allow users to use a file on a share on the server. This worked fine for all workstations but did not work to the T/S. The T/S is a W 2012 R2 server. What I discovered was this. If I address the file as \\servername\c$\share\my file.dat all is fine. However, if I address the file as \\servername\share\my file.dat no users including the domain administrator has no rights to this file. So it appears that there is a security issue with the share. I checked both the security and permissions and everyone has full control. What else can I check? I can go to any other computer and everyone has full control. It is only from the T/S where I have this issue.
0
Comment
Question by:rwheeler23
  • 2
4 Comments
 
LVL 33

Expert Comment

by:ste5an
ID: 41804713
You need to check two things:

1) The rights on the share \\servername\share.
and
2) The rights on the folder of this share (NTFS).

And to clarify your problem: From where do you try to read that file and where is that share located?
0
 
LVL 4

Expert Comment

by:mctigue
ID: 41804803
I concur with ste5an, you need to check the NTFS permissions. Simply giving the Everyone group full control to the share is not going to allow the users to access the files using their AD security credentials (NTFS permissions). The share permissions basically give access to the directory across the network but not the files and folders within that directory at a granular level.

Here's a link that give a quick overview of the concept:

http://www.techrepublic.com/article/learn-the-basic-differences-between-share-and-ntfs-permissions/

Best of luck,
0
 
LVL 4

Accepted Solution

by:
mctigue earned 500 total points
ID: 41804827
So, I think I replied too quickly and read your issue again. I see that you stated that the security settings work since you can access the share from other workstations, just the terminal server is the issue. Did you see if the path works by replacing the servername with the IP address? If this works then it could be name resolution issue which could require flushdns on the local terminal server. If this also fails check the firewall settings on the terminal server. It's possible this is blocking communication to and from shares on other servers.
0
 

Author Closing Comment

by:rwheeler23
ID: 41811594
Thanks
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The article will show you how you can maintain a simple logfile of all Startup and Shutdown events on Windows servers and desktops with PowerShell. The script can be easily adapted into doing more like gracefully silencing/updating your monitoring s…
Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

828 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question