I shared a folder from a 2008 r2 server, the user who has full control of folder and files within can't access the folder. I have tried changing the permissions from read only to none at all and still nothing. At a loss of what else to try, this user needs access to this folder any suggestions on how to fix this dilemma?
Shared Folder
- Thread starter jeffb
- Start date
Markverhyden
Well-Known Member
- Reaction score
- 11,109
- Location
- Raleigh, NC
What process did you use to share the folder?
I created a new folder on the C drive, went to properties and the security tab and added the users and permissions. Then I went to the share tab and shared it. It worked after I first shared it, but after a restart it asked for a password for the users account. I entered the password for the acct and it gave me access to the folder the file is in but when trying to open the folder it says c\folder\file not accessible contact network admin for access to the file.
Slaters Kustum Machines
Well-Known Member
- Reaction score
- 2,498
- Location
- Iowa
Did you do both Share and NTFS permissions? Any groups causing problems? Has the user logged off/ on after the change?
No I didn't set NTFS because the file will be shared across a network. As far as I can tell it's not a group setting. Yes the user has logged off and back on no changes.
You still need to set NTFS permissions even if it's being shared across a network. The server will use those to determine what access, if any, the user has to the files within the folder you are sharing.
Which are? They should be set to Full Control.
Both permissions are set to full control.
Markverhyden
Well-Known Member
- Reaction score
- 11,109
- Location
- Raleigh, NC
Try this - from https://technet.microsoft.com/en-us/library/cc770880(v=ws.11).aspx
To share a folder or a drive by using the Windows interface
To share a folder or a drive by using the Windows interface
- Open Computer Management.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
- In the console tree, click System Tools, click Shared Folders, and then click Shares.
- On the Action menu, click New Share.
- Follow the steps in the Create a Shared Folder Wizard, and then click Finish.
The server is a DC, the pc is also part of the domain. On the computers that it works on, I went to computer, network, clicked on the server entered the credentials, clicked on the folder and created a shortcut on the desktop. The file is an excel database. But after a restart when clicking on the shortcut it asked for credentials and then came back with an error saying c:\folder\file was not accessible. So I tried \\C:\folder\file and still asking for credentials was able to get to the main folder just not the file inside the folder. Tells me it is not accessible to contact the admin.
If the user is logged into the domain it shouldn't be asking for credentials
If you go to Start and enter \\servername\sharename in the search box does it show you the file?
Can you clarify this? Does it allow you to access the folder? If not, try using the server's IP instead of it's name, I've seen a similar error where the cause was DNS issues.
The permissions are set for the folder.
Have you checked the permission on the file itself as they would need Full Control of that as well?
I also can't understand why you're entering user credentials to access the share if the computer is a domain member. Regardless, if it is domain authentication try entering the username as domain\user (or user@domain). If you're trying to access the server using a username local to the server (which it sounds like you are), try servername\username instead.
Edit: And if you don't get the option to enter a new credentials, I would check/remove any previous bad connections with 'net use' via cmd.
Personally, I would never set permissions to 'full' for regular users, except maybe for diagnostic purposes such as these; read/write permission should be enough. Once you get it working, I would suggest read/write only for better security.
Regardless, if it is domain authentication try entering the username as domain\user (or user@domain). If you're trying to access the server using a username local to the server (which it sounds like you are), try servername\username instead.Edit: And if you don't get the option to enter a new credentials, I would check/remove any previous bad connections with 'net use' via cmd.
Personally, I would never set permissions to 'full' for regular users, except maybe for diagnostic purposes such as these; read/write permission should be enough. Once you get it working, I would suggest read/write only for better security.
Similar threads
