Link to home
Start Free TrialLog in
Avatar of AL_XResearch
AL_XResearchFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Unable to create share if target folder is not in drive root

I am having problems sharing a folder from my Windows 2007 R2 server,

If the folder to be shared is (target folder) is in the root of a local drive then simply selecting, right-clicking and selecting 'Share With...' allows me to create a share. This can be confrmed by a) I can see the share from another machine b) on the server's  [Device Manager - System Tools - Shared Folders - Shares] the new share is listed.

If the target folder is not in the root of the drive then repeating the above actions does not create a share - verified by the two methods above.

Can someone advise the correct way to create a sub-folder share ? I need this becuase I am using the share on another location but that folder can't' be moved on the home server.
Avatar of Paul MacDonald
Paul MacDonald
Flag of United States of America image

Are you suggesting Windows allows you to go through the process of sharing a folder, making you think the process was successful when in fact it was not?  Or are you prevented from completing the sharing operation?
Avatar of AL_XResearch

ASKER

It seems successful but then the target folder is not listed in the shares on that server and I can't see it from another pc in the same domain.

If I create the share with 'advanced sharing' then the share appears in the list but it is problematic to connect to it. I am wondering what the proper way is to share a folder that is not in the root of a drive ?
By the way:
  • typo in my initial post; it is a Windows 2008 R2 server
  • I am creating the share to consume with a CentOS 7 mount. The share works fine when the original folder is in the root of the drive but fails with 'permission denied' when the share comes from a sub-folder
Avatar of ☠ MASQ ☠
☠ MASQ ☠

Just checking, normally you'd Just share the specific sub-folder, apply permissions to it and don't allow permissions to propagate down.
You then need to set the share to to the full path to the sub-folder so you don't get permissions errors trying reaching it because it's in an unshared location. So it looks like \\\\server\\folder\\folder\\sub-folder.
MASQ : How do you mean "you set the share to the full path to the sub-folder" ? If I pick the sub-folder and setup a share called 'myFiles' then I would expect the path to it to be '\\server\myfiles'. This is how it works in Windows or are you saying Linux / CentOS works differently with CIFS shares ?
Sorry, rather clumsily I was describing Traverse Folder and List Folder permissions for "\myfiles" ("This folder only"), it works the same way.
Have you checked the permissions of the share allow your users access as well as the NTFS settings?
as well as the NTFS settings
Please elaborate - what do you mean by 'NTFS settings' ? I have given all the involved users the 'Full Control' permission
ASKER CERTIFIED SOLUTION
Avatar of ☠ MASQ ☠
☠ MASQ ☠

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
MSAQ Thank you for the remote slap around the face ! It was the NTFS permissions,

I originally had the Windows share (with the same folder name) on server A but then moved the folder onto server B and re-created everything exactly (or so I thought) but I seem to have omitted the NTFS permissions for the user I am logging in with from Linux.

Many thanks - I think I was getting too caught up on the Linux side. Just going to test if the share works with the scheduled Linux job,
Ultimately it was me who had omitted restoring the NTFS permissions but 'MASQ' helped me realise that, It always pays to double-check what you think you have done.