Re: Distributed File System / File Replication Service
From: Jill Zoeller [MSFT] (jillz_at_online.microsoft.com)
Date: 03/15/04
- Next message: Phil Drapeau: "Demote Windows 2000 DC in a 2003 AD - same ole dcpromo procedure?"
- Previous message: Jill Zoeller [MSFT]: "Re: Distributed File System / File Replication Service"
- In reply to: Hegg: "Re: Distributed File System / File Replication Service"
- Next in thread: Hegg: "Re: Distributed File System / File Replication Service"
- Reply: Hegg: "Re: Distributed File System / File Replication Service"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 15 Mar 2004 13:51:27 -0800
Give this more forceful approach a try:
HOW TO: Force Deletion of DFS Configuration Information 224384
http://support.microsoft.com/?id=224384
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hegg" <hegg@netwidedev.com> wrote in message news:%23hpjNJtCEHA.2404@TK2MSFTNGP11.phx.gbl...
Even with recreating the shared folder, the command still says:
System error 2 has occurred.
The system cannot find the file specified.
The folder still exists, the share still exists, but the DFS root (of course) does not still exist (since the first step was to delete it).
I also am getting the "The specified domain either does not exist or could not be contacted." error. What can I do to verify that the DNS is set up correctly? Maybe that's the base problem.
Thanks again for your help.
Hegg
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message news:u$EU7zsCEHA.2600@TK2MSFTNGP12.phx.gbl...
I had one customer report that you have to recreate the shared folder before running these commands. Give that a try and see how it works.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hegg" <hegg@netwidedev.com> wrote in message news:uilACusCEHA.1340@TK2MSFTNGP12.phx.gbl...
When running the first command (unmapftroot), the primary server reports:
The system cannot find the file specified
which I think is probably ok since I have already unshared that folder and everything.
When running the first command (unmapftroot), the secondary server reports:
System error 1355 has occurred.
The specified domain either does not exist or could not be contacted.
Which worries me and makes me wonder if something else is causing problems. I'm using dynamic DNS and the servers appear to have registered everything in my domain (tons of SRV records, ._msdcs, ._tcp, etc.). The secondary server seems to have the AD replicated to itself, so I assumed DNS was working properly.
Any suggestions? Thanks again for your great help,
Hegg
P.S. The 2nd command worked fine on both servers.
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message news:ODtt%23NsCEHA.3064@tk2msftngp13.phx.gbl...
Try deleting the roots and then start over (see procedure below). Also, we recommend that you enable FRS replication at the link level only, not at the root level. There are several reasons for this recommendation and I can give you more details if you'd like.
1. Remove the root server from the DFS namespace by using one of the following methods:
a.. In the Distributed File System snap-in, right-click the root target you want to remove, and then click Remove Target.
b.. Using the version of Dfsutil.exe included in the Windows Server 2003 Support Tools, run the following command, where RootTargetServer refers to the root server to be decommissioned: Dfsutil /UnmapFtRoot /Root:<DFSName> /Server:RootTargetServer /Share:<Share>
2. On the decommissioned root target, remove DFS information from the registry by using the following Dfsutil.exe command: Dfsutil /Clean /Server:RootTargetServer /Share:<RootName>
3. On the decommissioned root target, at the command prompt, type net stop dfs & net start dfs.
If you don't have a copy of Dfsutil, you can download it from the Microsoft Download Center (just search for Dfsutil).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hegg" <hegg@netwidedev.com> wrote in message news:ec%239O9rCEHA.2060@TK2MSFTNGP12.phx.gbl...
> Hello,
>
> I have two Windows 2003 Servers on which I am trying to get file replication
> working properly. I had created a new domain DFS root on the primary
> server, then created a new root target to point to the secondary server
> (same folder name, etc.). Then I realized that I had made a mistake, so I
> deleted the DFS root and unshared the two folders so that I could try again.
>
> However, when trying again, I create a new DFS root (domain, not
> stand-alone), specify the server and folder to share. Then I add a new root
> target and specify the secondary server and folder to share. That all works
> fine still (it appears). Status for both are 'online'. When I go into
> "Configure Replication" however, on the "Select an initial master" screen
> (the first step), both targets have a red X through them with the message:
> "This target is not eligible because the folder overlaps an existing
> replicated folder on that computer."
>
> I have tried everything I can think of and cannot get around this problem.
> Regardless of what I do, it says that it is overlapping an existing
> replicated folder. Can anyone help me? This is a really frustrating
> problem that has been going on for 3 days.
>
> I really appreciate any help someone can give. It doesn't seem to me that
> this should be that hard.
>
> By the way, I wasn't sure which newsgroup was best for this, so I hope this
> is in the right place. Thanks in advance,
>
> Hegg
>
>
- Next message: Phil Drapeau: "Demote Windows 2000 DC in a 2003 AD - same ole dcpromo procedure?"
- Previous message: Jill Zoeller [MSFT]: "Re: Distributed File System / File Replication Service"
- In reply to: Hegg: "Re: Distributed File System / File Replication Service"
- Next in thread: Hegg: "Re: Distributed File System / File Replication Service"
- Reply: Hegg: "Re: Distributed File System / File Replication Service"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading