Adding a DFS Namespace on Windows 2012 produces an error

Question

I have a very small lab environment with a 2012 AD server and two 2012 clients which I am testing DFSR before placing into production.
I can't seem to get a Namespace created.
Regardless if which host I try to create it on, I get the following error:
\\domain\shared: The namespace server \\hostname\shared cannot be added.  The user name or password is incorrect.
The wizard does not ask for a username or password.
I am logged in with the domain\administrator account.
The share does get created.  I have given Everyone and domain\Administrator  full control.
I am stumped and am looking for direction.
techsupport

Answer 1

Thanks for the reply.
When I create the DFS Namespace, say I call it 'public' as per the example,  'C:\DFSRoots\public' is created.
NOTE: I have tried this logged in locally as Administrator as well as domain\administrator (AD = 2012 also).
NOTE: If I create the Namespace on other volumes, again X:\DFSRoots\public is created - so the problem doesn't appear to follow the volume....
I can see that C:\DFSRoots\public is 'Read Only' - however toggling this attribute does not resolve the problem.
Also viewing Effective Permissions to C:\DFSRoots\public shows that domain\administrator has Full Permissions (all permissions with a green checkmark) as well with local administrator.
Regarding C:\System Volume Information - I was unable to view the contents of this folder until I gave myself Full Permissions - after which my Effective Permissions for C:\System Volume Information\DFSR became Full Permissions top to bottom.
Yet the error remains the same.
If I try the same operation on the other replication partner I get the same error.
I'm wondering if there isn't some inherent 2012 AD Group Policy Restriction causing this behavior.   This is also the first test with a 2012 AD with Domain Functional Level 2012.
This is basically a fresh build from .iso - no customization outside of installing the DFS Roles.
The DFS Replication works swimmingly - no problems either configuring it or observing functionality.
Just DFS Namespace is problematic.
I can't identify where DFS Namespace logs either.   I found the DFS Replication Logs easy enough...
Thanks for any additional advice.
techsupport