DFS replicated folders failing with ERROR ID 87

tnorman
tnorman used Ask the Experts™
on
Hi,

I have two server 2008 R2 servers doing namespace with replication between them.  Both are in separate AD sites.

The replication and namespace was working without issue until yesterday.  Server A is fine and works without issue.  Server B is reporting an "error ID: 87 and 4004".  The folders on Server B are inaccessible.  The original replicated folders (Shared, home, accounting) look like shortcut icons and in the same directory there are folders containing the data that have been named like "DFS.bac700da-1b77-4231-be27-56e4ead52068Shared".  The system won't let me rename them.

If anybody can help me with this issue that would be great.


thanks
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Have you tried recreating the namespace and targets?

Author

Commented:
I haven't rebuilt the entire namespace but I have removed the targets from the server that is acting funny.  I still can't delete the folder shortcuts with the original names.
DNS issues maybe?
11/26 Forrester Webinar: Savings for Enterprise

How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.

Author

Commented:
I don't think so.  It's strange what DFS has done here.  The original replicated folders have been converted (by the system) to shortcuts that point nowhere.  In the same directory it has created a second folder that has accessible data but is now named "DFS.bac700da-1b77-4231-be27-56e4ead52068Shared" instead of just "shared".  These new long name folders are also shared with the same long share name.  DFS can't replicate anymore because the original folders don't exist.  Any Idea what is going on here?
I'm assuming you configured the namespace as AD integrated. Maybe something hiccuped with AD replication.

repadmin /syncall coming back clean?

Author

Commented:
repadmin comes back with no errors

Author

Commented:
Started over from scratch, and all is now working.
DFS replication can be funny like that. =)
Did you rebuild the server or the namespace / targets?

Author

Commented:
The latter.
That was my first suggestion:

"Have you tried recreating the namespace and targets?"

Author

Commented:
Thanks for pointing that out. I have given you the points. In a perfect world, a 'fix' would have been ideal, but re-creation had to be done.
No problem. Thanks.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial