Solved

DFS folder not showing up in target path

Posted on 2009-05-20
6
3,066 Views
Last Modified: 2012-05-07
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
Comment
Question by:vianceadmin
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 
LVL 38

Expert Comment

by:ChiefIT
ID: 24523967
Any FRS log events, specifically in the 13000s?

Any DNS errors?
0
 

Author Comment

by:vianceadmin
ID: 24526751
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
 
LVL 38

Expert Comment

by:ChiefIT
ID: 24526946
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
Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

 

Author Comment

by:vianceadmin
ID: 24527232
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
 

Author Comment

by:vianceadmin
ID: 24527302
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
 

Accepted Solution

by:
vianceadmin earned 0 total points
ID: 24529045
Ended up being an issue with Veritas Replication Exec also being installed on that server.  Removed it and working fine.  
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Screen Mirroring 7 111
heat agent push through GPO 2 84
Auto-Enrollment Group Policy 2 64
Able to access \\192.168.1.x  but not \\192.168.1.xx from windows 2012 server . 36 102
I've always wanted to allow a user to have a printer no matter where they login. The steps below will show you how to achieve just that. In this Article I'll show how to deploy printers automatically with group policy and then using security fil…
Learn about cloud computing and its benefits for small business owners.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question