Re: This machine is not working properly as a DC.

I _think_ your restore has interfered with networking, shoot us the output
of 'ipconfig/all > c:\serverconfig.txt'.

or it possibly has something to do with the age of the backup, how recent
was it?

"sunteckjacks" <sunteckjacks@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E8E34815-3869-4BD0-B26E-074FCE4BC280@xxxxxxxxxxxxxxxx
Ok, just finished rebooting and got some warnings....
event id 2008 source ntds replication, category ds rpc client, user NT
AUTHORITY\ANONYMOUS LOGON

"Active Directory could not use DNS to resolve the IP address of the
source
domain controller listed below. To maintain the consistency of Security
groups, group policy, users and computers and their passwords, Active
Directory successfully replicated using the NetBIOS or fully qualified
computer name of the source domain controller.

Invalid DNS configuration may be affecting other essential operations on
member computers, domain controllers or application servers in this Active
Directory forest, including logon authentication or access to network
resources.

You should immediately resolve this DNS configuration error so that this
domain controller can resolve the IP address of the source domain
controller
using DNS.

Alternate server name:
tsldc02
Failing DNS host name:
8d1c13d4-4110-4a05-9a3d-77417aaf47bc._msdcs.tslus.pri


event id 1085 ntds replication

Internal event: Active Directory could not synchronize the following
directory partition with the domain controller at the following network
address.

Directory partition:
DC=tslus,DC=pri
Network address:
8d1c13d4-4110-4a05-9a3d-77417aaf47bc._msdcs.tslus.pri

If this error continues, the Knowledge Consistency Checker (KCC) will
reconfigure the replication links and bypass the domain controller.

User Action
Verify that the network address can be resolved with a DNS query.

Additional Data
Error value:
1908 Could not find the domain controller for this domain.

For more information, see Help and Support Center at

even id 1061 sourece ntds replication

Internal event: The directory replication agent request returned the
following status.

Additional Data
Error value:
1908 Could not find the domain controller for this domain.

event id 1085 source NTDS replication

Internal event: Active Directory could not synchronize the following
directory partition with the domain controller at the following network
address.

Directory partition:
CN=Configuration,DC=tslus,DC=pri
Network address:
8d1c13d4-4110-4a05-9a3d-77417aaf47bc._msdcs.tslus.pri

event id 1061 source NTDS replication
Internal event: The directory replication agent request returned the
following status.

Additional Data
Error value:
1908 Could not find the domain controller for this domain.




"kj [SBS MVP]" wrote:


"sunteckjacks" <sunteckjacks@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:178BD5BB-87AD-4116-861F-B87FC530D12D@xxxxxxxxxxxxxxxx
The (red X) conditions in the System log are

Event ID 7001. Service Control Manager.
The WinHTTP Web Proxy Auto-Discovery Service service depends on the
DHCP
Client service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because
it
has no enabled devices associated with it.

That is the only one showing.

This is the *first* and only error that shows in the system event log
after
the system restarts?


There are no (red X) conditions in the Directory Service log. There are
multiple Information conditions.
Event ids
1172
1073
1072
1060
1360
1364
1363
2041
1239
1240

These are happing repetivaly over and over again. all with the source
NTDS
Replication.

Thanks for the quick replys...



"kj [SBS MVP]" wrote:


"sunteckjacks" <sunteckjacks@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:FFE65458-1D61-4FFE-B0D4-F6C780F30EC4@xxxxxxxxxxxxxxxx
No outage issue. Everything is actually working right now. I am
sorry
for
being all over the place. Just seems like there are mulitple errors
causeing
one process not to work or vice versa.

I preformed a non-authoritative restore to try and fix the
replication
problems. As of right now my sysvol folder isn't shared. when i look
in
the

"C:\WINDOWS\SYSVOL\sysvol\server.pri"
there is a folder that says
"NtFrs_PreExisting___See_EventLog"

I then try and share it and it won't stay....

Please let me know what else you need from me be it logs or what
not.
Thanks.

A non authoritative restore of the SBS server?

Sysvol not sharing is an intended precautionary measure. Stop trying
to
circumvent the built in protection mechanisims and start
troubleshooting.

What are the "error" (red X) conditions in the SBS server System log
after
restarting?

What are the "error" (red X) conditions in the SBS server Directory
Service
log after restarting?

/kj


"kj [SBS MVP]" wrote:


"sunteckjacks" <sunteckjacks@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:2629A162-E7AD-4384-B381-5D7D022ECDAD@xxxxxxxxxxxxxxxx
This is an SBS 2003 server.

I started to try and fix replication errors and some how messed
something
up. Now i am getting in application error log, MSExchangeAL 8231
errors.
in
File Replication i am getting NtFrs 13508 errors.

To me (which doesn't mean much) it looks like this is not being
seen
as
the
PDC? On my DC02 i am unable to RDP in with the Domain
Administrator
account.
i get the error "The system cannot log you on due to the
following
error:
The
specified domain either does not exist or could not be
contacted."

HELP!

So, I guess the logical question would be, "what did you do to try
and
fix
the replication errors?"

You'll need to be much more forthcomming with meaningfull data like
specific
event log entries and such for us to be much help. You should also
consider
contacting Microsoft CSS if this is an outage situation with
significant
business impacts.

/kj



"SBS Rocker" wrote:

Is this the SBS 2003 server or a W2K3 DC server? What are you
attempting
to
do?

"sunteckjacks" <sunteckjacks@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:BA34C6F9-AA5D-4785-900E-5FB819B5E31B@xxxxxxxxxxxxxxxx
Domain membership test . . . . . . : Failed
DC discovery test. . . . . . . . . : Failed
DC list test . . . . . . . . . . . : Failed
LDAP test. . . . . . . . . . . . . : Failed

These are the failed tests in netdiag.log

failed test NetLogons
failed test Services
failed test frsevent
domain.pri failed test FsmoCheck

These are the failed test in dcdiag.log

This is just the beginning. I am totally lost on where to go.

To me it looks like my PDC was partialy demoted and now I am
have
trouble
replicating and even something as small as getting to shared
folders
on
the
server. I know I am alittle vague here but I am not sure
exactly
where
to
start?














.

Relevant Pages

  • Re: This machine is not working properly as a DC.
    ... this is maybe a little telltale 'IntelPRO/1000 MT Network Connection ... phantom, try running the 'Change Server IP address' wiz, move the server to ... event id 2008 source ntds replication, category ds rpc client, user NT ... computer name of the source domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD Replication issues
    ... Please describe a bit more detailed the network setup. ... Please see output of AD Replication Monitor - Search Domain ... Active Directory Replication Domain Controller Replication Failure ...
    (microsoft.public.windows.server.active_directory)
  • replication after tombstone expired
    ... is there any chance to start a replication after tombstone expired? ... were no computers/users added or deleted since the domain controller was ... unplugged from the network ...
    (microsoft.public.windows.server.active_directory)
  • Re: microsoft ads
    ... We have two domain controller in the network. ... Replication between two ... secondary domain controller is unable to authenticate ...
    (microsoft.public.windows.server.sbs)
  • Re: microsoft ads
    ... We have two domain controller in the network. ... Replication between two ... secondary domain controller is unable to authenticate ...
    (microsoft.public.windows.server.sbs)