Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Windows 2003 domain controller that we needed to take down in order to move it. When it was brought back up DFS wasn't working, our previous shares were marked as disabled. It turns out that the sharing permissions had been reset to basic read. By changing them to read/write and restarting the DFS service the shares could be enabled again in DFS.

What is bugging us is how/why did the permissions reset? Nobody touched them, and they shouldn't have been reset just from bringing the server down, correct?

share|improve this question
Did the IP or name of this server change after the move? And also, while not an answer to your question, this is another good example of why you shouldn't pile other services or roles onto a Domain Controller (with the possible exception of DHCP, depending on who you ask). – HopelessN00b Feb 12 '13 at 15:17
Well DFS is so lightweight it really shouldn't be an issue (in my opinion). The server name and IP remained the same. It may also be worth mentioning the folders in question are on SAN LUNs and not local hard drives. – Tony Feb 12 '13 at 17:39
It's not a performance issue, it's a complexity issue. Not being an AD expert, or having all the details of your setup, all I can really say is "hmmm, weird things happen when you run other services on a Domain Controller." – HopelessN00b Feb 12 '13 at 18:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.