Cannot joing laptop to domain - Error ID 4515

Hi All

Suddenly (?) I cannot join a laptop to the domain, my Exchange address book
is not getting up dated, and I cannot control my tape autoloader.

I beleive issue first came when we virtualised our servers, and later then
turned on an old DC to retreive some artowrk.

Error is as below.

I am not good at DNS, so please try and explain clearly. I have looked as
some older posts and AdsiEdit, but cannot work out what to do

Many Thanks


Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4515
Date: 4/12/2010
Time: 5:07:14 PM
User: N/A
Computer: HISTDC01
Description:
The zone historic.lan was previously loaded from the directory partition
MicrosoftDNS but another copy of the zone has been found in directory
partition DomainDnsZones.Historic.lan. The DNS Server will ignore this new
copy of the zone. Please resolve this conflict as soon as possible.

If an administrator has moved this zone from one directory partition to
another this may be a harmless transient condition. In this case, no action
is necessary. The deletion of the original copy of the zone should soon
replicate to this server.

If there are two copies of this zone in two different directory partitions
but this is not a transient caused by a zone move operation then one of these
copies should be deleted as soon as possible to resolve this conflict.

To change the replication scope of an application directory partition
containing DNS zones and for more details on storing DNS zones in the
application directory partitions, please see Help and Support.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 89 25 00 00 ?%..

Hello Lewej,

See here about:
http://support.microsoft.com/kb/867464

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi All
>
> Suddenly (?) I cannot join a laptop to the domain, my Exchange address
> book is not getting up dated, and I cannot control my tape autoloader.
>
> I beleive issue first came when we virtualised our servers, and later
> then turned on an old DC to retreive some artowrk.
>
> Error is as below.
>
> I am not good at DNS, so please try and explain clearly. I have looked
> as some older posts and AdsiEdit, but cannot work out what to do
>
> Many Thanks
>
> Event Type: Warning
> Event Source: DNS
> Event Category: None
> Event ID: 4515
> Date: 4/12/2010
> Time: 5:07:14 PM
> User: N/A
> Computer: HISTDC01
> Description:
> The zone historic.lan was previously loaded from the directory
> partition
> MicrosoftDNS but another copy of the zone has been found in directory
> partition DomainDnsZones.Historic.lan. The DNS Server will ignore this
> new
> copy of the zone. Please resolve this conflict as soon as possible.
> If an administrator has moved this zone from one directory partition
> to another this may be a harmless transient condition. In this case,
> no action is necessary. The deletion of the original copy of the zone
> should soon replicate to this server.
>
> If there are two copies of this zone in two different directory
> partitions but this is not a transient caused by a zone move operation
> then one of these copies should be deleted as soon as possible to
> resolve this conflict.
>
> To change the replication scope of an application directory partition
> containing DNS zones and for more details on storing DNS zones in the
> application directory partitions, please see Help and Support.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 89 25 00 00 ?%.

"Lewej" <> wrote in message news:7AD8D235-F1D2-4CEA-B923-...
> Hi All
>
> Suddenly (?) I cannot join a laptop to the domain, my Exchange address book
> is not getting up dated, and I cannot control my tape autoloader.
>
> I beleive issue first came when we virtualised our servers, and later then
> turned on an old DC to retreive some artowrk.
>
> Error is as below.
>
> I am not good at DNS, so please try and explain clearly. I have looked as
> some older posts and AdsiEdit, but cannot work out what to do
>
> Many Thanks
>
>
> Event Type: Warning
> Event Source: DNS
> Event Category: None
> Event ID: 4515
> Date: 4/12/2010
> Time: 5:07:14 PM
> User: N/A
> Computer: HISTDC01
> Description:
> The zone historic.lan was previously loaded from the directory partition
> MicrosoftDNS but another copy of the zone has been found in directory
> partition DomainDnsZones.Historic.lan. The DNS Server will ignore this new
> copy of the zone. Please resolve this conflict as soon as possible.
>
> If an administrator has moved this zone from one directory partition to
> another this may be a harmless transient condition. In this case, no action
> is necessary. The deletion of the original copy of the zone should soon
> replicate to this server.
>
> If there are two copies of this zone in two different directory partitions
> but this is not a transient caused by a zone move operation then one of these
> copies should be deleted as soon as possible to resolve this conflict.
>
> To change the replication scope of an application directory partition
> containing DNS zones and for more details on storing DNS zones in the
> application directory partitions, please see Help and Support.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 89 25 00 00 ?%..
>


Hello Lewej,

Meinolf gave you an excellent link regarding EventID# 4515.

What I would like to discuss is why it happened. Apparently from what you've described and stated, is you brought up an old DC online to retrieve data off of it. I am assuming the old DC was never properly demoted out of the domain. The reason I say this, if the Event ID 4515 appeared after bringing it back up, that is telling me the Historic.lan zone was previously in a different partition, and it must have been moved to another partition after the DC was taken offline, and now that it was brought upu again, it is now generating a duplicate/conflicting zone issue.

Some questions if you can respond, please:

1. Was the previous DC that you brought back online, properly demoted (running dcpromo), or simply unplugged?
2. How long ago was it taken offline?
3. How many current DCs exist, including the previous DC?
4. Please provide an ipconfig /all from your existing DCs. This will help evaluate any basic DNS and other configuration issues.

Thank you,

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

"Ace Fekay [MVP-DS, MCT]" wrote:

> "Lewej" <> wrote in message news:7AD8D235-F1D2-4CEA-B923-...
> > Hi All
> >
> > Suddenly (?) I cannot join a laptop to the domain, my Exchange address book
> > is not getting up dated, and I cannot control my tape autoloader.
> >
> > I beleive issue first came when we virtualised our servers, and later then
> > turned on an old DC to retreive some artowrk.
> >
> > Error is as below.
> >
> > I am not good at DNS, so please try and explain clearly. I have looked as
> > some older posts and AdsiEdit, but cannot work out what to do
> >
> > Many Thanks
> >
> >
> > Event Type: Warning
> > Event Source: DNS
> > Event Category: None
> > Event ID: 4515
> > Date: 4/12/2010
> > Time: 5:07:14 PM
> > User: N/A
> > Computer: HISTDC01
> > Description:
> > The zone historic.lan was previously loaded from the directory partition
> > MicrosoftDNS but another copy of the zone has been found in directory
> > partition DomainDnsZones.Historic.lan. The DNS Server will ignore this new
> > copy of the zone. Please resolve this conflict as soon as possible.
> >
> > If an administrator has moved this zone from one directory partition to
> > another this may be a harmless transient condition. In this case, no action
> > is necessary. The deletion of the original copy of the zone should soon
> > replicate to this server.
> >
> > If there are two copies of this zone in two different directory partitions
> > but this is not a transient caused by a zone move operation then one of these
> > copies should be deleted as soon as possible to resolve this conflict.
> >
> > To change the replication scope of an application directory partition
> > containing DNS zones and for more details on storing DNS zones in the
> > application directory partitions, please see Help and Support.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 89 25 00 00 ?%..
> >
>
>
> Hello Lewej,
>
> Meinolf gave you an excellent link regarding EventID# 4515.
>
> What I would like to discuss is why it happened. Apparently from what you've described and stated, is you brought up an old DC online to retrieve data off of it. I am assuming the old DC was never properly demoted out of the domain. The reason I say this, if the Event ID 4515 appeared after bringing it back up, that is telling me the Historic.lan zone was previously in a different partition, and it must have been moved to another partition after the DC was taken offline, and now that it was brought upu again, it is now generating a duplicate/conflicting zone issue.
>
> Some questions if you can respond, please:
>
> 1. Was the previous DC that you brought back online, properly demoted (running dcpromo), or simply unplugged?
> 2. How long ago was it taken offline?
> 3. How many current DCs exist, including the previous DC?
> 4. Please provide an ipconfig /all from your existing DCs. This will help evaluate any basic DNS and other configuration issues.
>
> Thank you,
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
> Microsoft MVP - Directory Services
>
> If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
> .
>
Hi - Thanks to Meinolf, good article.

I am not sure which Zone to delete, as the unrecommended one understood by
Win2000 has more entries than the ForestDNSZone or DomainDNSZones zones. Also
rather worrying message in article saying I could kill the server. WOld there
be any way back if I deleted a zone and things went pear shaped?

Ace, thanks for the repsosne.

1.Server just unplugged!
2. Four months or so ago, we virtualised since.
3. 3 DC's, 2 on this site and 1 on another
4. DC 1 Site 1:
Windows IP Configuration



Host Name . . . . . . . . . . . . : histdc01

Primary Dns Suffix . . . . . . . : Historic.lan

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : Historic.lan



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

Physical Address. . . . . . . . . : 00-50-56-B8-10-10

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.0.0.10

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.0.0.1

DNS Servers . . . . . . . . . . . : 10.0.0.10

10.0.1.10
Server 2 Site 1
Windows IP Configuration



Host Name . . . . . . . . . . . . : histdc01

Primary Dns Suffix . . . . . . . : Historic.lan

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : Historic.lan



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

Physical Address. . . . . . . . . : 00-50-56-B8-10-10

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.0.0.10

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.0.0.1

DNS Servers . . . . . . . . . . . : 10.0.0.10

10.0.1.10
Server 1 Site 2


Windows IP Configuration



Host Name . . . . . . . . . . . . : RBHDC01

Primary Dns Suffix . . . . . . . : Historic.lan

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : Historic.lan



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
(NDIS VBD Client)

Physical Address. . . . . . . . . : 00-1E-C9-B1-37-9C

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.0.1.10

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.0.1.1

DNS Servers . . . . . . . . . . . : 10.0.1.10

10.0.0.10

Primary WINS Server . . . . . . . : 10.0.1.10

Secondary WINS Server . . . . . . : 10.0.0.10

Thanks again

Lewej

"Lewej" wrote:

>
>
> "Ace Fekay [MVP-DS, MCT]" wrote:
>
> > "Lewej" <> wrote in message news:7AD8D235-F1D2-4CEA-B923-...
> > > Hi All
> > >
> > > Suddenly (?) I cannot join a laptop to the domain, my Exchange address book
> > > is not getting up dated, and I cannot control my tape autoloader.
> > >
> > > I beleive issue first came when we virtualised our servers, and later then
> > > turned on an old DC to retreive some artowrk.
> > >
> > > Error is as below.
> > >
> > > I am not good at DNS, so please try and explain clearly. I have looked as
> > > some older posts and AdsiEdit, but cannot work out what to do
> > >
> > > Many Thanks
> > >
> > >
> > > Event Type: Warning
> > > Event Source: DNS
> > > Event Category: None
> > > Event ID: 4515
> > > Date: 4/12/2010
> > > Time: 5:07:14 PM
> > > User: N/A
> > > Computer: HISTDC01
> > > Description:
> > > The zone historic.lan was previously loaded from the directory partition
> > > MicrosoftDNS but another copy of the zone has been found in directory
> > > partition DomainDnsZones.Historic.lan. The DNS Server will ignore this new
> > > copy of the zone. Please resolve this conflict as soon as possible.
> > >
> > > If an administrator has moved this zone from one directory partition to
> > > another this may be a harmless transient condition. In this case, no action
> > > is necessary. The deletion of the original copy of the zone should soon
> > > replicate to this server.
> > >
> > > If there are two copies of this zone in two different directory partitions
> > > but this is not a transient caused by a zone move operation then one of these
> > > copies should be deleted as soon as possible to resolve this conflict.
> > >
> > > To change the replication scope of an application directory partition
> > > containing DNS zones and for more details on storing DNS zones in the
> > > application directory partitions, please see Help and Support.
> > >
> > > For more information, see Help and Support Center at
> > > http://go.microsoft.com/fwlink/events.asp.
> > > Data:
> > > 0000: 89 25 00 00 ?%..
> > >
> >
> >
> > Hello Lewej,
> >
> > Meinolf gave you an excellent link regarding EventID# 4515.
> >
> > What I would like to discuss is why it happened. Apparently from what you've described and stated, is you brought up an old DC online to retrieve data off of it. I am assuming the old DC was never properly demoted out of the domain. The reason I say this, if the Event ID 4515 appeared after bringing it back up, that is telling me the Historic.lan zone was previously in a different partition, and it must have been moved to another partition after the DC was taken offline, and now that it was brought upu again, it is now generating a duplicate/conflicting zone issue.
> >
> > Some questions if you can respond, please:
> >
> > 1. Was the previous DC that you brought back online, properly demoted (running dcpromo), or simply unplugged?
> > 2. How long ago was it taken offline?
> > 3. How many current DCs exist, including the previous DC?
> > 4. Please provide an ipconfig /all from your existing DCs. This will help evaluate any basic DNS and other configuration issues.
> >
> > Thank you,
> >
> > --
> > Ace
> >
> > This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
> >
> > Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.
> >
> > Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
> > Microsoft Certified Trainer
> > Microsoft MVP - Directory Services
> >
> > If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
> > .
> >
> Hi - Thanks to Meinolf, good article.
>
> I am not sure which Zone to delete, as the unrecommended one understood by
> Win2000 has more entries than the ForestDNSZone or DomainDNSZones zones. Also
> rather worrying message in article saying I could kill the server. WOld there
> be any way back if I deleted a zone and things went pear shaped?
>
> Ace, thanks for the repsosne.
>
> 1.Server just unplugged!
> 2. Four months or so ago, we virtualised since.
> 3. 3 DC's, 2 on this site and 1 on another
> 4. DC 1 Site 1:
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : histdc01
>
> Primary Dns Suffix . . . . . . . : Historic.lan
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : Historic.lan
>
>
>
> Ethernet adapter Local Area Connection:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
>
> Physical Address. . . . . . . . . : 00-50-56-B8-10-10
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 10.0.0.10
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 10.0.0.1
>
> DNS Servers . . . . . . . . . . . : 10.0.0.10
>
> 10.0.1.10
> Server 2 Site 1
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : histdc01
>
> Primary Dns Suffix . . . . . . . : Historic.lan
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : Historic.lan
>
>
>
> Ethernet adapter Local Area Connection:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
>
> Physical Address. . . . . . . . . : 00-50-56-B8-10-10
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 10.0.0.10
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 10.0.0.1
>
> DNS Servers . . . . . . . . . . . : 10.0.0.10
>
> 10.0.1.10
> Server 1 Site 2
>
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : RBHDC01
>
> Primary Dns Suffix . . . . . . . : Historic.lan
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : Historic.lan
>
>
>
> Ethernet adapter Local Area Connection:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
> (NDIS VBD Client)
>
> Physical Address. . . . . . . . . : 00-1E-C9-B1-37-9C
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 10.0.1.10
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 10.0.1.1
>
> DNS Servers . . . . . . . . . . . : 10.0.1.10
>
> 10.0.0.10
>
> Primary WINS Server . . . . . . . : 10.0.1.10
>
> Secondary WINS Server . . . . . . : 10.0.0.10
>
> Thanks again
>
> Lewej
>
>
Hi Guys
ALSO, how do I get my old server back on line. I did tried to demote it, but
it could not reach a correct DC to do this. Is there anyway I cna demote it
off the network and then get to join again as a memeber server?
Many Thanks

Hello Lewej,

Demoting a DC can be done with dcpromo /forceremoval. But you have to cleanup
AD database also from the old DC:
http://support.microsoft.com/kb/555846/en-us

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> "Lewej" wrote:
>
>> "Ace Fekay [MVP-DS, MCT]" wrote:
>>
>>> "Lewej" <> wrote in message
>>> news:7AD8D235-F1D2-4CEA-B923-...
>>>
>>>> Hi All
>>>>
>>>> Suddenly (?) I cannot join a laptop to the domain, my Exchange
>>>> address book is not getting up dated, and I cannot control my tape
>>>> autoloader.
>>>>
>>>> I beleive issue first came when we virtualised our servers, and
>>>> later then turned on an old DC to retreive some artowrk.
>>>>
>>>> Error is as below.
>>>>
>>>> I am not good at DNS, so please try and explain clearly. I have
>>>> looked as some older posts and AdsiEdit, but cannot work out what
>>>> to do
>>>>
>>>> Many Thanks
>>>>
>>>> Event Type: Warning
>>>> Event Source: DNS
>>>> Event Category: None
>>>> Event ID: 4515
>>>> Date: 4/12/2010
>>>> Time: 5:07:14 PM
>>>> User: N/A
>>>> Computer: HISTDC01
>>>> Description:
>>>> The zone historic.lan was previously loaded from the directory
>>>> partition
>>>> MicrosoftDNS but another copy of the zone has been found in
>>>> directory
>>>> partition DomainDnsZones.Historic.lan. The DNS Server will ignore
>>>> this new
>>>> copy of the zone. Please resolve this conflict as soon as possible.
>>>> If an administrator has moved this zone from one directory
>>>> partition to another this may be a harmless transient condition. In
>>>> this case, no action is necessary. The deletion of the original
>>>> copy of the zone should soon replicate to this server.
>>>>
>>>> If there are two copies of this zone in two different directory
>>>> partitions but this is not a transient caused by a zone move
>>>> operation then one of these copies should be deleted as soon as
>>>> possible to resolve this conflict.
>>>>
>>>> To change the replication scope of an application directory
>>>> partition containing DNS zones and for more details on storing DNS
>>>> zones in the application directory partitions, please see Help and
>>>> Support.
>>>>
>>>> For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>> Data:
>>>> 0000: 89 25 00 00 ?%..
>>> Hello Lewej,
>>>
>>> Meinolf gave you an excellent link regarding EventID# 4515.
>>>
>>> What I would like to discuss is why it happened. Apparently from
>>> what you've described and stated, is you brought up an old DC online
>>> to retrieve data off of it. I am assuming the old DC was never
>>> properly demoted out of the domain. The reason I say this, if the
>>> Event ID 4515 appeared after bringing it back up, that is telling me
>>> the Historic.lan zone was previously in a different partition, and
>>> it must have been moved to another partition after the DC was taken
>>> offline, and now that it was brought upu again, it is now generating
>>> a duplicate/conflicting zone issue.
>>>
>>> Some questions if you can respond, please:
>>>
>>> 1. Was the previous DC that you brought back online, properly
>>> demoted (running dcpromo), or simply unplugged?
>>>
>>> 2. How long ago was it taken offline?
>>>
>>> 3. How many current DCs exist, including the previous DC?
>>>
>>> 4. Please provide an ipconfig /all from your existing DCs. This will
>>> help evaluate any basic DNS and other configuration issues.
>>>
>>> Thank you,
>>>
>>> -- Ace
>>>
>>> This posting is provided "AS-IS" with no warranties or guarantees
>>> and confers no rights.
>>>
>>> Please reply back to the newsgroup or forum for collaboration
>>> benefit among responding engineers, and to help others benefit from
>>> your resolution.
>>>
>>> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007,
>>> MCSE & MCSA 2003/2000, MCSA Messaging 2003
>>>
>>> Microsoft Certified Trainer
>>>
>>> Microsoft MVP - Directory Services
>>>
>>> If you feel this is an urgent issue and require immediate
>>> assistance, please contact Microsoft PSS directly. Please check
>>> http://support.microsoft.com for regional support phone numbers.
>>>
>>> .
>>>
>> Hi - Thanks to Meinolf, good article.
>>
>> I am not sure which Zone to delete, as the unrecommended one
>> understood by Win2000 has more entries than the ForestDNSZone or
>> DomainDNSZones zones. Also rather worrying message in article saying
>> I could kill the server. WOld there be any way back if I deleted a
>> zone and things went pear shaped?
>>
>> Ace, thanks for the repsosne.
>>
>> 1.Server just unplugged!
>> 2. Four months or so ago, we virtualised since.
>> 3. 3 DC's, 2 on this site and 1 on another
>> 4. DC 1 Site 1:
>> Windows IP Configuration
>> Host Name . . . . . . . . . . . . : histdc01
>>
>> Primary Dns Suffix . . . . . . . : Historic.lan
>>
>> Node Type . . . . . . . . . . . . : Hybrid
>>
>> IP Routing Enabled. . . . . . . . : No
>>
>> WINS Proxy Enabled. . . . . . . . : No
>>
>> DNS Suffix Search List. . . . . . : Historic.lan
>>
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>>
>> Description . . . . . . . . . . . : VMware Accelerated AMD PCNet
>> Adapter
>>
>> Physical Address. . . . . . . . . : 00-50-56-B8-10-10
>>
>> DHCP Enabled. . . . . . . . . . . : No
>>
>> IP Address. . . . . . . . . . . . : 10.0.0.10
>>
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>
>> Default Gateway . . . . . . . . . : 10.0.0.1
>>
>> DNS Servers . . . . . . . . . . . : 10.0.0.10
>>
>> 10.0.1.10
>> Server 2 Site 1
>> Windows IP Configuration
>> Host Name . . . . . . . . . . . . : histdc01
>>
>> Primary Dns Suffix . . . . . . . : Historic.lan
>>
>> Node Type . . . . . . . . . . . . : Hybrid
>>
>> IP Routing Enabled. . . . . . . . : No
>>
>> WINS Proxy Enabled. . . . . . . . : No
>>
>> DNS Suffix Search List. . . . . . : Historic.lan
>>
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>>
>> Description . . . . . . . . . . . : VMware Accelerated AMD PCNet
>> Adapter
>>
>> Physical Address. . . . . . . . . : 00-50-56-B8-10-10
>>
>> DHCP Enabled. . . . . . . . . . . : No
>>
>> IP Address. . . . . . . . . . . . : 10.0.0.10
>>
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>
>> Default Gateway . . . . . . . . . : 10.0.0.1
>>
>> DNS Servers . . . . . . . . . . . : 10.0.0.10
>>
>> 10.0.1.10
>> Server 1 Site 2
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : RBHDC01
>>
>> Primary Dns Suffix . . . . . . . : Historic.lan
>>
>> Node Type . . . . . . . . . . . . : Hybrid
>>
>> IP Routing Enabled. . . . . . . . : No
>>
>> WINS Proxy Enabled. . . . . . . . : No
>>
>> DNS Suffix Search List. . . . . . : Historic.lan
>>
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>>
>> Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
>> GigE (NDIS VBD Client)
>>
>> Physical Address. . . . . . . . . : 00-1E-C9-B1-37-9C
>>
>> DHCP Enabled. . . . . . . . . . . : No
>>
>> IP Address. . . . . . . . . . . . : 10.0.1.10
>>
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>
>> Default Gateway . . . . . . . . . : 10.0.1.1
>>
>> DNS Servers . . . . . . . . . . . : 10.0.1.10
>>
>> 10.0.0.10
>>
>> Primary WINS Server . . . . . . . : 10.0.1.10
>>
>> Secondary WINS Server . . . . . . : 10.0.0.10
>>
>> Thanks again
>>
>> Lewej
>>
> Hi Guys
> ALSO, how do I get my old server back on line. I did tried to demote
> it, but
> it could not reach a correct DC to do this. Is there anyway I cna
> demote it
> off the network and then get to join again as a memeber server?
> Many Thanks

"Lewej" <> wrote in message news:89AE5F0F-40C2-4B8A-91FA-...
>
>
> "Ace Fekay [MVP-DS, MCT]" wrote:
>
>> "Lewej" <> wrote in message news:7AD8D235-F1D2-4CEA-B923-...
>> > Hi All
>> >
>> > Suddenly (?) I cannot join a laptop to the domain, my Exchange address book
>> > is not getting up dated, and I cannot control my tape autoloader.
>> >
>> > I beleive issue first came when we virtualised our servers, and later then
>> > turned on an old DC to retreive some artowrk.
>> >
>> > Error is as below.
>> >
>> > I am not good at DNS, so please try and explain clearly. I have looked as
>> > some older posts and AdsiEdit, but cannot work out what to do
>> >
>> > Many Thanks
>> >
>> >
>> > Event Type: Warning
>> > Event Source: DNS
>> > Event Category: None
>> > Event ID: 4515
>> > Date: 4/12/2010
>> > Time: 5:07:14 PM
>> > User: N/A
>> > Computer: HISTDC01
>> > Description:
>> > The zone historic.lan was previously loaded from the directory partition
>> > MicrosoftDNS but another copy of the zone has been found in directory
>> > partition DomainDnsZones.Historic.lan. The DNS Server will ignore this new
>> > copy of the zone. Please resolve this conflict as soon as possible.
>> >
>> > If an administrator has moved this zone from one directory partition to
>> > another this may be a harmless transient condition. In this case, no action
>> > is necessary. The deletion of the original copy of the zone should soon
>> > replicate to this server.
>> >
>> > If there are two copies of this zone in two different directory partitions
>> > but this is not a transient caused by a zone move operation then one of these
>> > copies should be deleted as soon as possible to resolve this conflict.
>> >
>> > To change the replication scope of an application directory partition
>> > containing DNS zones and for more details on storing DNS zones in the
>> > application directory partitions, please see Help and Support.
>> >
>> > For more information, see Help and Support Center at
>> > http://go.microsoft.com/fwlink/events.asp.
>> > Data:
>> > 0000: 89 25 00 00 ?%..
>> >
>>
>>
>> Hello Lewej,
>>
>> Meinolf gave you an excellent link regarding EventID# 4515.
>>
>> What I would like to discuss is why it happened. Apparently from what you've described and stated, is you brought up an old DC online to retrieve data off of it. I am assuming the old DC was never properly demoted out of the domain. The reason I say this, if the Event ID 4515 appeared after bringing it back up, that is telling me the Historic.lan zone was previously in a different partition, and it must have been moved to another partition after the DC was taken offline, and now that it was brought upu again, it is now generating a duplicate/conflicting zone issue.
>>
>> Some questions if you can respond, please:
>>
>> 1. Was the previous DC that you brought back online, properly demoted (running dcpromo), or simply unplugged?
>> 2. How long ago was it taken offline?
>> 3. How many current DCs exist, including the previous DC?
>> 4. Please provide an ipconfig /all from your existing DCs. This will help evaluate any basic DNS and other configuration issues.
>>
>> Thank you,
>>
>> --
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.
>>
>> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
>> Microsoft Certified Trainer
>> Microsoft MVP - Directory Services
>>
>> If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
>> .
>>
> Hi - Thanks to Meinolf, good article.
>
> I am not sure which Zone to delete, as the unrecommended one understood by
> Win2000 has more entries than the ForestDNSZone or DomainDNSZones zones. Also
> rather worrying message in article saying I could kill the server. WOld there
> be any way back if I deleted a zone and things went pear shaped?
>
> Ace, thanks for the repsosne.
>
> 1.Server just unplugged!
> 2. Four months or so ago, we virtualised since.
> 3. 3 DC's, 2 on this site and 1 on another
> 4. DC 1 Site 1:
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : histdc01
>
> Primary Dns Suffix . . . . . . . : Historic.lan
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : Historic.lan
>
>
>
> Ethernet adapter Local Area Connection:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
>
> Physical Address. . . . . . . . . : 00-50-56-B8-10-10
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 10.0.0.10
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 10.0.0.1
>
> DNS Servers . . . . . . . . . . . : 10.0.0.10
>
> 10.0.1.10
> Server 2 Site 1
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : histdc01
>
> Primary Dns Suffix . . . . . . . : Historic.lan
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : Historic.lan
>
>
>
> Ethernet adapter Local Area Connection:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
>
> Physical Address. . . . . . . . . : 00-50-56-B8-10-10
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 10.0.0.10
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 10.0.0.1
>
> DNS Servers . . . . . . . . . . . : 10.0.0.10
>
> 10.0.1.10
> Server 1 Site 2
>
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : RBHDC01
>
> Primary Dns Suffix . . . . . . . : Historic.lan
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : Historic.lan
>
>
>
> Ethernet adapter Local Area Connection:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
> (NDIS VBD Client)
>
> Physical Address. . . . . . . . . : 00-1E-C9-B1-37-9C
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 10.0.1.10
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 10.0.1.1
>
> DNS Servers . . . . . . . . . . . : 10.0.1.10
>
> 10.0.0.10
>
> Primary WINS Server . . . . . . . : 10.0.1.10
>
> Secondary WINS Server . . . . . . : 10.0.0.10
>
> Thanks again
>
> Lewej
>
>



Your ipconfigs are confusing. You said you have 3 DCs? I assume you mean including the one you removed and brought back online? The ipconfigs show 3 DCs, but the first two are duplicates.

Also, with WINS, if both DCs shown in the ipconfigs are WINS servers, a WINS server MUST only point to itself. This is due to ownership of records. If another is listed on a WINS server, it can skew the records. Remove the additional WINS. Also, assuming histdc01 is a WINS server, based on RBHDC01 has it set, point it to itself.

Can you provide the missing DC's ipconfig, as well as please let us know which one was the one you previously unplugged and brought back online?

As far as unplugging a DC, that is one of the worst things to do, unfortunately to say. This is because AD is aware of all DCs in the infrastructure (forest) and sets up replication partnerships between them. When you unplug one, it will cause numerous errors in AD and the event logs.

If the previous DC had the DNS zone in one partition, and the other DC has the same zone yet in a different partition, as the article indicated, it is a duplicate/conflicting zone. That is probably why you are seeing problems where it cannot "find" the other DC. The duplicate of conflicting zone is not usable.

Please read my blog on this issue and how to clean it up. I've provided specifics on what to look for to help understand the difference in how they are depicted in ADSI Edit.

Using ADSI Edit to Resolve Conflicting or Duplicate AD Integrated DNS zones
http://msmvps.com/blogs/acefekay/arc...dns-zones.aspx


Since it has been 4 months, and I *assume* all DCs are Windows 2003, that isn't too bad, since the tombstone time is 180 days. However, if any of the DCs are Windows 2000, the tombstone time is 60 days. A force removal as Meinolf mentioned, is your only option.

Ace