| Author |
Message |
John VG
Guest
|
 Posted:
Thu Jan 13, 2005 1:05 pm Post subject:
Trying to remove dfs / errors in FRSdiag |
|
|
I had two servers set up with FRS / DFS and one server died (DC2). So
obviously DC2 was not gracefully removed from the FRS / DFS. now I have error
in FRSDiag about the DFS that doesn’t exits. This is driving me nuts! how
can I resolve the errors from frs. here is the example (names are changed to
protect the innocent)
NtFrs 1/6/2005 6:56:08 AM Warning 13508 The File Replication Service is
having trouble enabling replication from DC2 to MAIN-SERV for f:\fileserver
using the DNS name dc2.contoso.com. FRS will keep retrying. Following are
some of the reasons you would see this warning. [1] FRS can not
correctly resolve the DNS name dc2.contoso.com from this computer. [2]
FRS is not running on dc2.contoso.com. [3] The topology information in
the Active Directory for this replica has not yet replicated to all the
Domain Controllers. This event log message will appear once per
connection, After the problem is fixed you will see another event log
message indicating that the connection has been established. |
|
| Back to top |
|
 |
Glenn L
Guest
|
| Posted:
Fri Jan 14, 2005 9:33 am Post subject:
Re: Trying to remove dfs / errors in FRS |
|
|
If MAIN_SERV and DC2 only hosted the SYSVOL replica set, then the cleanup is
simple.
follow KB216498 to remove DC2 from AD.
--
Glenn L
CCNA, MCSE 2000/2003 + Security
"John VG" <JohnVG@discussions.microsoft.com> wrote in message
news:05176953-A102-4CB5-ACE9-0550335EAA01@microsoft.com...
| Quote: | I had two servers set up with FRS / DFS and one server died (DC2). So
obviously DC2 was not gracefully removed from the FRS / DFS. now I have
error
in FRSDiag about the DFS that doesn't exits. This is driving me nuts! how
can I resolve the errors from frs. here is the example (names are changed
to
protect the innocent)
NtFrs 1/6/2005 6:56:08 AM Warning 13508 The File Replication Service is
having trouble enabling replication from DC2 to MAIN-SERV for
f:\fileserver
using the DNS name dc2.contoso.com. FRS will keep retrying. Following
are
some of the reasons you would see this warning. [1] FRS can not
correctly resolve the DNS name dc2.contoso.com from this computer. [2]
FRS is not running on dc2.contoso.com. [3] The topology information in
the Active Directory for this replica has not yet replicated to all the
Domain Controllers. This event log message will appear once per
connection, After the problem is fixed you will see another event log
message indicating that the connection has been established.
|
|
|
| Back to top |
|
|
Richard Chinn [MSFT]
Guest
|
| Posted:
Thu Jan 20, 2005 1:42 am Post subject:
Re: Trying to remove dfs / errors in FRSdiag |
|
|
Your dead DC probably still has some objects in AD that haven't been
cleaned up. As a result, FRS on its surviving partner machine(s) is
still trying to connect to the offline machine. Your options are to
ignore the problem or to clean up the stray AD objects.
Cleaning up the AD objects can be dangerous, so you should be sure to
take a full backup before making changes. You can refer to the
following KB for help.
296183 Overview of Active Directory Objects That Are Used by FRS
http://support.microsoft.com/?id=296183
--Richard
Please post FRS related questions to
microsoft.public.windows.server.dfs_frs and prefix the subject line
with "FRS:" to make it easier to spot. Note that FRS is used to
replicate SYSVOL on domain controllers and DFS root and link targets.
For additional FRS resources, please visit
http://www.microsoft.com/frs.
This posting is provided "AS IS" with no warranties, and confers no
rights.
On Wed, 12 Jan 2005 23:05:01 -0800, "John VG"
<JohnVG@discussions.microsoft.com> wrote:
| Quote: | I had two servers set up with FRS / DFS and one server died (DC2). So
obviously DC2 was not gracefully removed from the FRS / DFS. now I have error
in FRSDiag about the DFS that doesn’t exits. This is driving me nuts! how
can I resolve the errors from frs. here is the example (names are changed to
protect the innocent)
NtFrs 1/6/2005 6:56:08 AM Warning 13508 The File Replication Service is
having trouble enabling replication from DC2 to MAIN-SERV for f:\fileserver
using the DNS name dc2.contoso.com. FRS will keep retrying. Following are
some of the reasons you would see this warning. [1] FRS can not
correctly resolve the DNS name dc2.contoso.com from this computer. [2]
FRS is not running on dc2.contoso.com. [3] The topology information in
the Active Directory for this replica has not yet replicated to all the
Domain Controllers. This event log message will appear once per
connection, After the problem is fixed you will see another event log
message indicating that the connection has been established. |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in