Re: DNS / Net Logon Service Problems When Replacing a Server
- From: zsteve1@xxxxxxxxxx
- Date: 18 Aug 2006 09:46:48 -0700
Ive run the suggested diagnostics and I do see some information that
might be indicating where the problem lies.
(1) The first snippet from NETDIAG indicated that machine isnt working
properly as a domain controller.
(2)The second snippet from DCDIAG indicates the following :
"Event String: The File Replication Service is having trouble
enabling replication from LAMBDA-DBS-01 to
LAMBDA_DB for c:\winnt\sysvol\domain using the
DNS name lambda-dbs-01.lambda.cc. FRS will keep retrying."
It appears that DNS cannot resolve "lamdba-dbs-01.lambda.cc" which is
the server name + the domain name. Im guessing that this is the
problem and that DNS would be able to resolve the server name alone.
What can I do next to aid DNS in resolving the name to replication can
occur?
************ Snippet FROM NETDIAG.EXE **********************
Domain membership test . . . . . . : Failed
[WARNING] Ths system volume has not been completely replicated to
the local machine. This machine is not working properly as a DC.
Machine is a . . . . . . . . . : Primary Domain Controller Emulator
Netbios Domain name. . . . . . : LAMBDA
Dns domain name. . . . . . . . : lambda.cc
Dns forest name. . . . . . . . : lambda.cc
Domain Guid. . . . . . . . . . :
{053A058E-140E-4FB0-9AE3-40D5BC43646A}
Domain Sid . . . . . . . . . . :
S-1-5-21-448539723-343818398-1417001333
Logon User . . . . . . . . . . : Administrator
Logon Domain . . . . . . . . . : LAMBDA
************ Snippet FROM DCDIAG.EXE **********************
Starting test: frssysvol
* The File Replication Service Event log test
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034FE
Time Generated: 08/17/2006 16:52:56
Event String: File Replication Service is scanning the data
in the system volume. Computer LAMBDA_DB cannot become a domain
controller until this process is
complete. The system volume will then be shared as SYSVOL.
To check for the SYSVOL share, at the command prompt, type: net share
When File Replication Service completes the scanning process, the
SYSVOL share will appear.
The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 08/17/2006 16:54:47
Event String: The File Replication Service is having
trouble enabling replication from LAMBDA-DBS-01 to LAMBDA_DB for
c:\winnt\sysvol\domain using the DNS name lambda-dbs-01.lambda.cc. FRS
will keep retrying. Following are some of the reasons you would see
this warning.
[1] FRS can not correctly resolve the DNS name lambda-dbs-01.lambda.cc
from this computer.
[2] FRS is not running on lambda-dbs-01.lambda.cc.
[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.
......................... LAMBDA_DB passed test frssysvol
.
- Follow-Ups:
- Re: DNS / Net Logon Service Problems When Replacing a Server
- From: Paul Bergson
- Re: DNS / Net Logon Service Problems When Replacing a Server
- From: CraigTin
- Re: DNS / Net Logon Service Problems When Replacing a Server
- From: CraigTin
- Re: DNS / Net Logon Service Problems When Replacing a Server
- References:
- DNS / Net Logon Service Problems When Replacing a Server
- From: zsteve1
- Re: DNS / Net Logon Service Problems When Replacing a Server
- From: Paul Bergson
- DNS / Net Logon Service Problems When Replacing a Server
- Prev by Date: Re: Using DNS to block subdomain
- Next by Date: Re: DNS Redesign Issue
- Previous by thread: Re: DNS / Net Logon Service Problems When Replacing a Server
- Next by thread: Re: DNS / Net Logon Service Problems When Replacing a Server
- Index(es):
Relevant Pages
|