Cannot write to newly created shares on Windows server 2008

Just created 3 new shares at the root of 2008. No one on the network can write to them, even though "Everyone" has all access (both at the DOS level and NTFS) , even at the root of the drive. Cannot write even if access is provided specifically to the user.
Greg MasonOwnerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

arnoldCommented:
Sharing security is just one aspect, check the security tab to see who actually has rights to write.

Cacls, icacls or xcacls directory will give you the information you are looking for.

Is this a DC?  A DC has a more restrictive .......
0
Greg MasonOwnerAuthor Commented:
It is a DC. Are you saying that the win interface doesn't hold the answer? You've gotta go to a special utility?
0
David Johnson, CD, MVPOwnerCommented:
if the share points to C:\ that is a security restriction that has been in place for a long time, since Windows XP days,.  you can write to subfolders of C:\ but not C:\ itself. This applies only to the system drive.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Greg MasonOwnerAuthor Commented:
Thanks for the replies. Someone suggested running CHKDSK on the volume but we couldn't get even that to work correctly. We ended up moving the data and blowing the volume away. After re-creation, shares now work correctly.  Beats me.

Thanks again.
0
arnoldCommented:
The tools are useful in seeing the security permissions rather than having to go a folder at a tine, and then the ....... Right-click......
0
David Johnson, CD, MVPOwnerCommented:
if chkdsk fails on a drive then yes blowing it away is the only recourse.. I'd be curious as to why chkdsk failed... possible failing disk?
0
Greg MasonOwnerAuthor Commented:
Brand new drive, brand new server. That's what made it easier to start again.

The "drive" is actually a RAID 5 array. CHKDSK would start and then "hang" at about 20-25% - Started again, it would seem to spin through normally and fail on the security part of it. It would just close. Something was kafuckled somewhere.

The RAID tool reported everything was optimal, so we didn't re-create the array, just the volume. The lack of functioning shares was absolutely driving me crazy. All rights set properly , check 5 times - no one could write to the drive - honey, where IS that pint of vodka I left in the office?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.