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

We have a Windows 2008 server (not R2) acting as a primary file source in a DFS replication group with a single other server that happens to be Windows Storage Server 2008. All is well in terms of 2-way replication.

What we cannot explain is how at random times the replicated folder on the primary location is becoming hidden and system on its attributes. Users call to ask where did their folder go. I've set up a scheduled task that runs every 5 minutes to log the folder attributes to a file so I can nail down a window of time when the attributes are getting flipped. Then I've created custom filters in the Event Viewer to show all events around this time frame (+/- 10 minutes), and checked it on the primary file server, secondary file server, and domain controllers hosting the namespace.

I cannot find a single entry that looks out of the ordinary to explain what's happening. The closest event I can find that occurred on the primary file server and 2 of the domain controllers is a informational Group Policy event (ID 5327) saying "Estimated network bandwidth on one of the connections: 0 kbps." But I'm not sure this is related, and even so on the primary file server a second or two later there's another ID 5327 telling the bandwidth on a connection is back up to normal.

Any ideas??

share|improve this question

1 Answer

We have the exact same issue as of the past couple of days. I've been using DFS for a couple of years now on 2008 R2 and never seen this problem.

The other DFS setup has 4 folders but only 2 of them have changed to hidden folders somehow ?? The only temporary fix I've found is by using the attrib trick here (but I'm guessing the system may change them back to hidden).

attrib -r -h -s "G:\folder_name" (on the source folder)

Can't find any other answers anywhere!! ... a recent windows update maybe ?

share|improve this answer
Strange! Yes attrib gets to the end result but as you mentioned it will probably revert at any time. I've done two things to further the analysis. The first is check the C:\Windows\Debug logs that contain VERY detailed DFSR information... unfortunately that's not helping me in this case as far as I can interpret it. The other thing is enable detailed Windows security auditing on folder attributes as in this link here, we'll see... – Chris Klose Apr 20 '12 at 12:40

Your Answer

 
discard

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

Not the answer you're looking for? Browse other questions tagged or ask your own question.