NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Properly Setting up Permissions moving from Windows server to ReadyNAS
Complicated post - I'm sorry....I'm a ReadyNAS newbie.
Had a Windows 2008 server. It was just a networked drive. Did not use it for policy setting, pushing updates or anything. Have 9 MACs a...
Stephen - thank you.....the whole "DATA" naming thing - I wondered if that was an issue possibly.
So let me just run this by you. Here is my folder structure:
DATA
--CHAMBER
--CORPORATE
--ECONOMIC DEVELOPMENT
--GRAPHICS and PHOTOS
--PLANNING AND PROPERTY
--TECHNOLOGY
--AP_DRIVE
...so i thought last night, should I just create shares at the main root level PER main folder? Instead of trying to put those 7 main folders UNDER "DATA" or "FILE-SERVER" - that is your recommendation? The only problem with that is on my PCs the "old" server was mapped as the "S:\" drive so all file linking and such still works...becasue "S:\CHAMBER\Inner Folder 1\File1.doc" on the old server is still the sameon the new server and I have 216,000+ files. But if I make "CHAMBER" a share at the root of the NAS, then map that drive, I can only "map" ONE of the main SHARES as "S:\"....? They would have multiple mapped drives to get to each main folder....?
...another question - folder names - spaces? capitalization? symbols? (dashes, etc...) does that matter on a NAS?
...
dpitts wrote:
...another question - folder names - spaces? capitalization? symbols? (dashes, etc...) does that matter on a NAS?
Capitialization rules for SMB are the same as with a Windows Server - you can enter case, but it is ignored when searching, etc. Similarly, rules for spaces and symbols are the same as with Windows.
International characters are allowed, but might not be rendered properly in some places.
dpitts wrote:
But if I make "CHAMBER" a share at the root of the NAS, then map that drive, I can only "map" ONE of the main SHARES as "S:\"....? They would have multiple mapped drives to get to each main folder....?
Yes, if CHAMBER, EXECUTIVE, etc are their own shares, then you'd need to map them as different drive letters
A middle ground is to make ACCOUNTING, EXECUTIVE shares, and rename DATA. Then use network access to control access to ACCOUNTING and EXECUTIVE. That would limit the number of users with multiple drive letters.
To allow just one mapped drive, rename your "DATA" to "SHARES" (for "S:"). Of course, anything other than an existing share, volume, or user name will work, but that seems a natural choice. Doing so does restrict your ability to restrict users to specific areas, but you don't seem to need to do that.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
