poboy

Where do I set access permisions for the folder targets? I have the
following Namespace:

\\mro.aviation.ad\ITO - fully acessible cant read\write.

I created a Folder Target "Software" and I cannot do anything with it. I
get Access Denied - Network Path not Found. When I access it logged into the
server - e:\support\ito\software - I get E:\support\ITO\Software is not
accessible. the network location cannot be reached. When I right-click on
the folder - there are no secuirty options...just sharing - but it is not set
to be shared. Through the DFS management console - I have the "Folder
Target" share properties set to Everyone Full access. I also added "Domain
users" full access, but that didnt help. Im missing something...

jill zoeller msft

It sounds like you're trying to modify the permissions of the DFS structures
under the root share, correct? I'm guessing your root shared folder is
located at e:\support\ITO, and that when you add a folder called Software to
the namespace, you see a new folder called Software under \ITO. If you're
trying to change the Software folder here, this would explain the behavior
you're seeing--these link folders are essentially reparse points and can't
be accessed locally. When users browse to these link folders remotely, a
referral is triggered and the client is redirected to the appropriate folder
target. You shouldn't attempt to modify permissions on these link folders.
Any permissions should be set on the folder target itself--set up shared
folder permissions directly on \\targetserver\software and set NTFS
permissions directly on the underlying folder that hosts the share (C:\data
or whatever).

This process is described in the DFS technical reference at
www.microsoft.com/dfs. The terminology is not updated to match R2 but the
concepts are the same.


--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.

poboy

Thanks, I just figured that out. I had "data share" set as the "target
share". So the data is not replicated to where the links actually are?
Right now I have everything set to e:\support\ito and want to add the link
"software" to that. I cannot physically put the data in
e:\support\ito\software? It has to be in another share ie:
e:\support\software? Seems kind of redundant...is that why the default
location for the links is c:\DFSRoot? All the roots and links are on C: and
then I can put the actual data on e? With that figured out, I am now getting
the following error. MROPHXFP00 is the server I am setting everything up
on...mrospifp00 is the one to replicate to.

Event Type: Error
Event Source: DFSR
Event Category: None
Event ID: 5012
Date: 7/5/2006
Time: 1:41:22 PM
User: N/A
Computer: MROPHXFP00
Description:
The DFS Replication service failed to communicate with partner MROSPIFP00
for replication group mro.aviation.ad\ito\test. The partner did not recognize
the connection or the replication group configuration.

Partner DNS Address: mrospifp00.mro.aviation.ad

Optional data if available:
Partner WINS Address: mrospifp00
Partner IP Address: 10.110.0.81


The service will retry the connection periodically.

Additional Information:
Error: 9026 (The connection is invalid)
Connection ID: 8923F383-2DE3-4EE1-A128-2A9BC7FB5896
Replication Group ID: B02414C6-F6A4-4018-9D78-871C2A5DF428

jill zoeller msft

Think of the root share as a private folder for DFS to store its structures.
You're right that in R2 we did pick a folder by default to reduce the
complexity of setting up a namespace for admins--it's one less decision you
need to make. All other data that you want accessible in the namespace
should be stored elsewhere on the same server or even on a different server.
DFS will provide referrals to the UNC paths of the data, regardless of where
the data is located.

It sounds like some previous misconfigurations might still be present. Try
running a diagnostic report for additional tshooting guidance for the errors
you're seeing.


--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.

poboy

Errors cleared up...however when I run a diagnotic report, it successfully
creates however it just says "Report Loading. Please wait..." underneath
server health. I assume there is more to the report than:
1. Data Collected on:
2. Replicate Group
3. Reference member
4. Server scope
5. DFS Replication efficiency savings
6. Server health

poboy

Nevermind - about:internet needed to be added to trusted sites...

tom&v&r

The "report loading..." is probably due to Internet Explorer Enhanced
Security Configuration. Go to Control Panel, Add-Remove Programs, Add-Remove
Windows Components, Internet Explorer Enhanced Security Configuration Wizard,
and uncheck For Administrators Group options. Next, Etc, Etc. The report will
then load properly. Best of luck.