|
|
 FAQ
 Search
 Memberlist
 Usergroups
 Register
 Profile
 Private messages
 Log in
|
|
| Author |
Message |
Orvs
Guest
|
 Posted: Thu May 11, 2006 2:28 pm Post subject: Mistake and causing issues for my Windows 2003 / R2 DC |
 |
|
I inserted a new DC using R2 Windows 2003 in my domain. Promotion went
smoothly.
- After the restart. I found out I didnt install DNS prior to Promotion. so
I did
- Install DNS and ensure my AD zone is present with AD Integrated.
- I change the IP settings for my new DCR2 to point to itself. do another
restart.
Problem now is:
in DS Sites and services... There is no automatically created connections..
I tried to do Chek Replication topology it gives me an error " The ff error
occured during attempt to check replication tolology, A databse error occured"
No replication is hapenning and new DCR2 is not propagating outbound
connection.
How can I fix this??
Waht I dont understand is During DCpromo, Windows 2003 R2 should warn me
that I need to install DNS first..... Or there is an option I missied?? |
|
| Back to top |
|
 |
|
|
Carlo Cacciafesta
Guest
|
| Posted: Thu May 11, 2006 3:19 pm Post subject: RE: Mistake and causing issues for my Windows 2003 / R2 DC |
|
|
"Orvs" wrote:
| Quote: | I inserted a new DC using R2 Windows 2003 in my domain. Promotion went
smoothly.
- After the restart. I found out I didnt install DNS prior to Promotion. so
I did
- Install DNS and ensure my AD zone is present with AD Integrated.
- I change the IP settings for my new DCR2 to point to itself. do another
restart.
Problem now is:
in DS Sites and services... There is no automatically created connections..
I tried to do Chek Replication topology it gives me an error " The ff error
occured during attempt to check replication tolology, A databse error occured"
No replication is hapenning and new DCR2 is not propagating outbound
connection.
How can I fix this??
Waht I dont understand is During DCpromo, Windows 2003 R2 should warn me
that I need to install DNS first..... Or there is an option I missied??
|
This is not the first DC, isn't it? So you should already have at least
another DNS server. When you installed DNS server on DCR2, did it acquire DNS
records from the other DNS (if it's AD Integrated it should)? Check the DNS
Management console to verify the existence of records from the other DNS
server.
The Knowledge Consistency Checker (KCC) shoud automatically create the
replication topology. Are there any errors in the "Directory Service" event
viewer? If so, post them.
Dcpromo does warn you about the need for DNS. Did you initially point to
another DNS server?
Regards,
Carlo |
|
| Back to top |
|
|
Orvs
Guest
|
| Posted: Thu May 11, 2006 4:28 pm Post subject: RE: Mistake and causing issues for my Windows 2003 / R2 DC |
|
|
Hi Carlo thanks:
I think my mistake was when I promote it as a DC, I used other DNS Address
from other DC..and that is the reason why during DCPROMO it didnot ask for a
DNS server to be installed in the new DCR2.. I should point it to itself as
the DNS and then run DCpromo.
Here is another error in event log
the KCC failed to update the replicastion topology for the local domain
controller. The KCC will attempt to update replication topogloy at the
following scheduled interval, schedule interval 900.
I restarted it so many times no luck! Can I do dcpromo /force removal??? or
any other solution/
"Carlo Cacciafesta" wrote:
| Quote: | "Orvs" wrote:
I inserted a new DC using R2 Windows 2003 in my domain. Promotion went
smoothly.
- After the restart. I found out I didnt install DNS prior to Promotion. so
I did
- Install DNS and ensure my AD zone is present with AD Integrated.
- I change the IP settings for my new DCR2 to point to itself. do another
restart.
Problem now is:
in DS Sites and services... There is no automatically created connections..
I tried to do Chek Replication topology it gives me an error " The ff error
occured during attempt to check replication tolology, A databse error occured"
No replication is hapenning and new DCR2 is not propagating outbound
connection.
How can I fix this??
Waht I dont understand is During DCpromo, Windows 2003 R2 should warn me
that I need to install DNS first..... Or there is an option I missied??
This is not the first DC, isn't it? So you should already have at least
another DNS server. When you installed DNS server on DCR2, did it acquire DNS
records from the other DNS (if it's AD Integrated it should)? Check the DNS
Management console to verify the existence of records from the other DNS
server.
The Knowledge Consistency Checker (KCC) shoud automatically create the
replication topology. Are there any errors in the "Directory Service" event
viewer? If so, post them.
Dcpromo does warn you about the need for DNS. Did you initially point to
another DNS server?
Regards,
Carlo |
|
|
| Back to top |
|
|
Carlo Cacciafesta
Guest
|
| Posted: Thu May 11, 2006 4:40 pm Post subject: RE: Mistake and causing issues for my Windows 2003 / R2 DC |
|
|
"Orvs" wrote:
| Quote: | Hi Carlo thanks:
I think my mistake was when I promote it as a DC, I used other DNS Address
from other DC..and that is the reason why during DCPROMO it didnot ask for a
DNS server to be installed in the new DCR2.. I should point it to itself as
the DNS and then run DCpromo.
Here is another error in event log
the KCC failed to update the replicastion topology for the local domain
controller. The KCC will attempt to update replication topogloy at the
following scheduled interval, schedule interval 900.
I restarted it so many times no luck! Can I do dcpromo /force removal??? or
any other solution/
|
Try doing this. On DCR2 set the other DC as primary DNS server and DCR2 as
secondary DNS server in TCP/IP configuration, then restart DCR2. The other
DNS server already contains all the records you need, pointing DCR2 to itself
before replicating the DNS zone probably caused the problem.
Let me know if this solves your problem. If you will post other errors from
the event viewer please don't forget to write the source and the error number.
Regards,
Carlo |
|
| Back to top |
|
|
Orvs
Guest
|
| Posted: Thu May 11, 2006 7:43 pm Post subject: RE: Mistake and causing issues for my Windows 2003 / R2 DC |
|
|
I tried and no luck.. I will just do dcpromo /forceremoval of thsi DCR2 and
then do metadata cleanup and promote it again nicely. since it is just a
fresh DC..rather than wasting time...
Is is same in Windows 2002 for the dcpromo /forceremoval, I run it in
Windows 2003 and it gives me a warning? what is this warning can I ignore and
proceed and hope wil not affect my other DCS??
Thanks a lot Man
"Carlo Cacciafesta" wrote:
| Quote: | "Orvs" wrote:
Hi Carlo thanks:
I think my mistake was when I promote it as a DC, I used other DNS Address
from other DC..and that is the reason why during DCPROMO it didnot ask for a
DNS server to be installed in the new DCR2.. I should point it to itself as
the DNS and then run DCpromo.
Here is another error in event log
the KCC failed to update the replicastion topology for the local domain
controller. The KCC will attempt to update replication topogloy at the
following scheduled interval, schedule interval 900.
I restarted it so many times no luck! Can I do dcpromo /force removal??? or
any other solution/
Try doing this. On DCR2 set the other DC as primary DNS server and DCR2 as
secondary DNS server in TCP/IP configuration, then restart DCR2. The other
DNS server already contains all the records you need, pointing DCR2 to itself
before replicating the DNS zone probably caused the problem.
Let me know if this solves your problem. If you will post other errors from
the event viewer please don't forget to write the source and the error number.
Regards,
Carlo |
|
|
| Back to top |
|
|
Orvs
Guest
|
| Posted: Thu May 11, 2006 7:46 pm Post subject: RE: Mistake and causing issues for my Windows 2003 / R2 DC |
|
|
I tried and no luck! there is this 13508 Event ID error.
I'm thinking of dcpromo/forceremioval and do metadata cleanup and redo it
again....
What is thsi warning when you do dcpromo/forceremoval in 2003 R2? can I
ignore it and go ahead.. Hope will not affect my otehr DCs..
thanks
"Carlo Cacciafesta" wrote:
| Quote: | "Orvs" wrote:
Hi Carlo thanks:
I think my mistake was when I promote it as a DC, I used other DNS Address
from other DC..and that is the reason why during DCPROMO it didnot ask for a
DNS server to be installed in the new DCR2.. I should point it to itself as
the DNS and then run DCpromo.
Here is another error in event log
the KCC failed to update the replicastion topology for the local domain
controller. The KCC will attempt to update replication topogloy at the
following scheduled interval, schedule interval 900.
I restarted it so many times no luck! Can I do dcpromo /force removal??? or
any other solution/
Try doing this. On DCR2 set the other DC as primary DNS server and DCR2 as
secondary DNS server in TCP/IP configuration, then restart DCR2. The other
DNS server already contains all the records you need, pointing DCR2 to itself
before replicating the DNS zone probably caused the problem.
Let me know if this solves your problem. If you will post other errors from
the event viewer please don't forget to write the source and the error number.
Regards,
Carlo |
|
|
| Back to top |
|
|
|
|
