Hi EE community. Recently I posted a question about getting a new Win2k8 namespace server added to an existing DFS namespace. This has been accomplished, however, I need some help with the DFS replication part.
I implemented a Windows Storage Server box, went into DFS mgmt, and added a namespace entry for a rarely used share on our network. I will refer to the Windows Storage Server as ServerB, ServerA is a Windows 2008 R2 machine holding file shares, also w/ DFS setup.
When i go into DFS mgmt tool on ServerA, highlight my test share, click on Namespace servers tab, I can see both locations on ServerA and ServerB. Both have "Enabled" established as Referral Status. When I browse the share for each respective server path, i see the content
When I go into DFS mgmt tool on ServerB, highlight my test share, click on Namespace servers tab, I can see both locations on ServerA and ServerB; there is no Referral Status column though. When I browse the share for each respective server path, I dont see any content on ServerA or ServerB
on ServerA, when I go to Start > Run field, and enter the DFS namespace for the share, it comes up blank. When i use the UNC syntax \\serverA\sharename, the data is there. When i use the UNC syntax \\serverB\sharename , the data is there. When i check the local volume where this folder is stored, on ServerA, the data and the directories are there.
on ServerB, when I go to Start > Run field, and enter the DFS namespace for the share, it comes up with the data. When i use the UNC syntax \\serverB\sharename , the data is not there. When i use the UNC syntax \\serverA\sharename , the data is not there either.
when I try this from a WinXp workstation, the DFS namespace works, when I try UNC \\ServerA\sharename, no data seen. When I try UNC \\ServerB\sharename, the data is there.
I'm pretty sure I screwed something up with DFS replication setup, but I followed the Technet article as closely as possible.
Under the DFS replication group on ServerB, I didnt have the shared Enabled under Membership Status, I've set this to be Enabled now. Under the Replicated Folders tab the publication status is not set to published. I right click and select "Share and Publish in Namespace" which brings up the wizard. I use the default selection and choose "Share and Publish the replicated folder in a namespace". On the next screen, it shows the members, ServerA, and ServerB. For ServerB, it states, "shared folder needed". The folder exists on the volume, as I manually created it. When I click on edit share, it brings up box, stating:
- Local Path of Replicated folder:
- Use the following Shared folder:
New is selected by default, and existing is greyed out. when I go type in the name of the share, and it says its in use. I open the volume on ServerB, and there's all the replicated data there. So do I need to share it?
Now when I go back to ServerA, use the DFS namespace, the data is there, when i try UNC syntax for \\ServerA\share or \\ServerB\share, there's no data.
When I go back to the WinXP workstation, the DFS namespace has the data, but also same symptoms when accessing \\ServerA\share or \\ServerB\share, no data
OK, im super confused. can anyone please help?