Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3276
  • Last Modified:

DFS folder not showing up in target path

In DFS managemement, when I add a folder target to the namespace on server 1, the folder shows up in C:\DFSRoots\Namespace but when I add another namespace server and add a 2nd folder target to setup replication, the folder that shows up in server 1 under the DFSRoots folder doesn't show up in C:\DFSRoots\Namespace on server 2 but it should.  Any ideas?  The problem is then any clients using server 2 for a referral don't see the folder under the namespace.  Clients using server 1 do see the folder.  
0
vianceadmin
Asked:
vianceadmin
  • 4
  • 2
1 Solution
 
ChiefITCommented:
Any FRS log events, specifically in the 13000s?

Any DNS errors?
0
 
vianceadminAuthor Commented:
Not a single error.  Can't figure it out.  The first folder that I created in my namespace showed up on both servers (local and remote).  The second folder I created showed up in the server at the local site but not at the remote server.  Nothing in DNS either.  

0
 
ChiefITCommented:
I read an article that stated not to map to a single computer within the namespace, (in other words to one of the two namespace servers). Otherwise it will not copy over. The article stated to map network drives specifically to the namespace itself.

So, here is how I see your predicament. One of two scenarios.

After creating the namespace, you forgot or have an error in creating the replication partners. So, there is probably a misses communication between the replication partners.

The second scenario is you are mapping to one server within the namespace and it is not actually replicating to the other server as a result. Personally, I haven't seen this error. I use DFSR that may accomodate mapping to one server within the namespace while DFS may not.

Check your replication settings and then if you have a logon script to map to one of the two computers within the namespace, edit that to map to the namespace itself.

Example:

NETSHARES<<-----Map to here by using its UNC path of \\namespacename\file folder
DC1---DC2<<<--not here by using \\DC2\file folder
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
vianceadminAuthor Commented:
Not sure I follow.  If I have a share (we'll call it test), then I should be able to create a namespace (domain\DFS) and create a folder that points to \\server1\test and \\server2\test and have it replicate from server1 to server2, right?  Then I can create mapped drives that point to \\domain\DFS\test...
0
 
vianceadminAuthor Commented:
I think I see what you're saying...No, I'm not trying to map to the \\servername\share...I'm trying to map to the namespace\share.  The problem is if the target folder doesn't show up at the other site in the C:\DFSroots, then when people at that site try to go to \\namespace\share, it's not there.  

Server1 at main site:
Contents of C:\DFSRoots

Test1
Test2



Server2 at remote site:
Contents of C:\DFSRoots

Test1

So when users at site 2 try to hit \\namespace\test2, it errors out because the folder never gets created even though I added server2 as a target for the folder.  
0
 
vianceadminAuthor Commented:
Ended up being an issue with Veritas Replication Exec also being installed on that server.  Removed it and working fine.  
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now