Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

DFS folder not showing up in target path

Posted on 2009-05-20
6
Medium Priority
?
3,220 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 39

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 39

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
Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

 

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

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

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

Numerous times I have been asked this questions that what is it that makes my machine log on so slow, there have been cases where computers took 23 minute exactly after taking password and getting to the desktop. Interesting thing was the fact th…
Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Have you created a query with information for a calendar? ... and then, abra-cadabra, the calendar is done?! I am going to show you how to make that happen. Visualize your data!  ... really see it To use the code to create a calendar from a q…

715 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