Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AD issues and replication

Status
Not open for further replies.
ITMax

ITMax

IS-IT--Management
Apr 15, 2003
24
0
0
US
I have inherited a nasty problem, hoping someone else has encountered this...

I have 2- w2k servers sp3 the first server was the AD FSMO
the second was a member server in the domain.

the AD server crashed (had only one hard drive) I was able to bring it back up for a short time but the drive was failing, I added the second server as a DC to the AD domain, and replicated userid's etc... however the first server crashed irrevocably afterwards and I was not able to complete the full transfer for FMSO, I then seized all 5 process Domain naming, infrastructure, etc..

and did so successfully, however there are still some quirky issues in the domain, but the main thingis I dont trust this domain controller, it still has entries for the previous domain and the GC is intermittent, I made the current server the GC (clicking the check box) but still something seems off.

I have replaced/upgraded the priginal server with a pair of 73gb u160 with Raid-1 and have installed and updated w2k as well.

I had a vague idea of just recreating the domain and users from scratch on the new server and then demoting the current server to member status and adding it to the new server/domain as an AD DC, but that has been nixed.

so I have done the opposite, the old server (re-imaged) has been added to the current domain and has been made an DC in the domain.

The current operations master has the following issues, and I am pretty sure its mainly DNS related .. but how to fix it is starting to frustrate me.,..

Testing server: Default-First-Site-Name\SERVER2
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
with DNS
......................... SERVER2 passed test Connectivity

----------------------

Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... SERVER2 passed test frssysvol
Starting test: kccevent
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/28/2003 12:25:52
Event String: The attempt to establish a replication link with
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/28/2003 12:26:15
Event String: The attempt to establish a replication link with
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/28/2003 12:26:38
Event String: The attempt to establish a replication link with
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/28/2003 12:27:02
Event String: The attempt to establish a replication link with
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/28/2003 12:27:25
Event String: The attempt to establish a replication link with
An Warning Event occured. EventID: 0x800004F1
Time Generated: 04/28/2003 12:27:48
Event String: The attempt to establish a replication link with
......................... SERVER2 failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 11:55:42
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 11:56:52
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 11:58:01
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 11:59:12
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:00:22
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:01:36
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:02:46
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x40011006
Time Generated: 04/28/2003 12:03:05
Event String: The connection was aborted by the remote WINS.
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:03:55
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:05:04
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:06:14
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:07:23
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:08:32
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:09:42
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:10:51
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:12:00
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:13:10
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:14:19
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:17:48
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:18:57
Event String: Registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 04/28/2003 12:20:06
Event String: Registration of the DNS record
......................... SERVER2 failed test systemlog

any insight would be appreciated

 
Sort by date Sort by votes
Hm,... first tel me if I understood properly:

You have DC1 and DC2
1. DC1 was seized from the AD, then demoted
2. DC2 became the FSMO and the only DC
3. you revived your old DC1
4. you joined it to the AD

Where is the DNS server? On DC2? What name has DC1? Same like it had before? What errors are in the EventViewer of DC1?

Gia Betiu
gia@almondeyes.net
Computer Eng. CNE 4, CNE 5, MCSE Win2K
new: (just started)
 
Upvote 0 Downvote
Not quite...

DC1 and DC2

both running DNS,

DC1 crashed .. unrecoverable,

DC2 seized FSMO

DC1 re-imaged and added to the domain new name, call it DC3

there are no errors in the current DC3

the errors above are from DC2

current situation DC2 and DC3 are DC in the domain.

there are still issues on DC2 with DNS, as well as having remenant DC1 entries/records.



 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

rzammit82
  • Locked
  • Question
Windows Server 2016 - DNS/AD problem
Replies
1
Views
143
suncit
suncit
DrB0b
  • Locked
  • Question
Hybrid on prem AD with Azure AD
Replies
2
Views
84
DrB0b
DrB0b
DTGMI
  • Locked
  • Question
WIN 10 Pro PC & Adding back to our Network
Replies
0
Views
90
DTGMI
DTGMI
DrB0b
  • Locked
  • Question
Terminal Server issues doing anything network related after RDPing into
Replies
3
Views
74
DrB0b
DrB0b
mangentle
  • Locked
  • Question
What are the key advantages of using Microsoft Windows Servers for businesses?
Replies
1
Views
133
gbaughma
gbaughma

Part and Inventory Search

Sponsor

Back
Top