Replacing a DC which has Wins & DNS services by re-addressing.

[Guest]

I have just put up a new W2K DC (on new hardware) and I'd like to put it into
place to replace an existing DC with older hardware (which I will remove and
later take out of service, after I'm sure everything works).

Existing servers:
ServerA (old hardware) - 10.10.10.1 - runs MS-DNS and WINS
ServerB (old hardware) - 10.10.10.2 - runs MS-DNS and WINS
ServerC (old hardware) - 10.10.10.3 - runs MS-DNS and WINS

New server:
ServerD (new hardware) - 10.10.10.10 - runs MS-DNS and WINS

all site clients point "statically" to any two of the above servers.

WINS is configured to use ServerB as the "center" of hub-n-spoke replication
(both server A and server C replicate only to server B not with each other.

The DNS zones are AD-integrated (and since I have promoted ServerD, I see
them within it's DNS utility already).

Here are the steps I intend to follow.

- On ServerD (follow KB300468) to move the any non-AD DNS zones - done.
- On serverD shutdown Wins service - done.
- On serverD set DNS/WINS client to point to serverB - reboot - done.
- On serverA set DNS/WINS client to point to serverB - reboot - done.
- On ServerB make sure WINS replicates OK now - done.

Tomorrow I will
- delete existing WINS replication between ServerA and ServerB.
- shutdown Wins service and set service to DISABLE on ServerA.
- Change IP on ServerA from 10.10.10.1 to 10.10.10.55 - Reboot.
then.
- Set WINS service on serverD to manual
- Shutdown WINS service on serverD and remove existing datafile.
- Change IP on ServerD from 10.10.10.10 to 10.10.10.1 (old serverA address)
- reboot ServerD.
- copy WINS.MDB from ServerA (per KB875419) to ServerD and start WINS service.
- set up WINS replication between ServerB and ServerD.
- verify that after replication ServerD has site wins records.

then a few days after everything appears OK.
- give GC role to ServerD
- take GC role away from ServerA

wait a few more days.
- Demote ServerA, check site replication, look for legacy objects.
- Shutdown, physically remove ServerA

questions:

1) I'm assuming that RE-ADDRESSING a DC changes the server's IP address
values in both the AD-integrated DNS zones and server netlogon.dns file - is
this true?

2) When the 10.10.10.1 WINS records are repopulated into ServerD (by either
the MDB copy or WINS replication, will serverD own them because it's now
10.10.10.1 or will they still reference ServerA.

 

[Jason Tan]

Hi,

Thanks for posting!

Based on the description, I would like to provide you with the following
information for your reference:

---1) I'm assuming that RE-ADDRESSING a DC changes the server's IP address
values in both the AD-integrated DNS zones and server netlogon.dns file -
is this true?

Correct. You may remove the old DNS record and re-register the DNS record
with Ipconfig after introducing the new server.

For more detailed information, please refer to the following ariticle:
223413 Options for Ipconfig.exe in Windows 2000
http://support.microsoft.com/?id=223413

---2) When the 10.10.10.1 WINS records are repopulated into ServerD (by
either the MDB copy or WINS replication, will serverD own them because it's
now 10.10.10.1 or will they still reference ServerA.

You may remove the old WINS record and manually add a Dynamic WINS entry.

For more detailed information, please refer to the following article:

Delete WINS entry
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Serve
rHelp/8fd40dad-8d31-491d-a19d-5568cecf9b60.mspx

233375 HOW TO: Manually Add a Dynamic WINS Entry to a Windows 2000 WINS
Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;233375

If there is anything that is unclear, please feel free to let me know.

Thanks & Regards,

Jason Tan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Replacing a DC which has Wins & DNS services by
re-addressing.
| thread-index: AcVdc1FF7p/mX9xBSIihVRFWvE94/Q==
| X-WBNR-Posting-Host: 150.131.130.127
| From: "=?Utf-8?B?QmlsbC1NVA==?=" <[email protected]>
| Subject: Replacing a DC which has Wins & DNS services by re-addressing.
| Date: Fri, 20 May 2005 12:37:11 -0700
| Lines: 60
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.win2000.networking
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.networking:24053
| X-Tomcat-NG: microsoft.public.win2000.networking
|
| I have just put up a new W2K DC (on new hardware) and I'd like to put it
into
| place to replace an existing DC with older hardware (which I will remove
and
| later take out of service, after I'm sure everything works).
|
| Existing servers:
| ServerA (old hardware) - 10.10.10.1 - runs MS-DNS and WINS
| ServerB (old hardware) - 10.10.10.2 - runs MS-DNS and WINS
| ServerC (old hardware) - 10.10.10.3 - runs MS-DNS and WINS
|
| New server:
| ServerD (new hardware) - 10.10.10.10 - runs MS-DNS and WINS
|
| all site clients point "statically" to any two of the above servers.
|
| WINS is configured to use ServerB as the "center" of hub-n-spoke
replication
| (both server A and server C replicate only to server B not with each
other.
|
| The DNS zones are AD-integrated (and since I have promoted ServerD, I see
| them within it's DNS utility already).
|
| Here are the steps I intend to follow.
|
| - On ServerD (follow KB300468) to move the any non-AD DNS zones - done.
| - On serverD shutdown Wins service - done.
| - On serverD set DNS/WINS client to point to serverB - reboot - done.
| - On serverA set DNS/WINS client to point to serverB - reboot - done.
| - On ServerB make sure WINS replicates OK now - done.
|
| Tomorrow I will
| - delete existing WINS replication between ServerA and ServerB.
| - shutdown Wins service and set service to DISABLE on ServerA.
| - Change IP on ServerA from 10.10.10.1 to 10.10.10.55 - Reboot.
| then.
| - Set WINS service on serverD to manual
| - Shutdown WINS service on serverD and remove existing datafile.
| - Change IP on ServerD from 10.10.10.10 to 10.10.10.1 (old serverA
address)
| - reboot ServerD.
| - copy WINS.MDB from ServerA (per KB875419) to ServerD and start WINS
service.
| - set up WINS replication between ServerB and ServerD.
| - verify that after replication ServerD has site wins records.
|
| then a few days after everything appears OK.
| - give GC role to ServerD
| - take GC role away from ServerA
|
| wait a few more days.
| - Demote ServerA, check site replication, look for legacy objects.
| - Shutdown, physically remove ServerA
|
| questions:
|
| 1) I'm assuming that RE-ADDRESSING a DC changes the server's IP address
| values in both the AD-integrated DNS zones and server netlogon.dns file -
is
| this true?
|
| 2) When the 10.10.10.1 WINS records are repopulated into ServerD (by
either
| the MDB copy or WINS replication, will serverD own them because it's now
| 10.10.10.1 or will they still reference ServerA.
|
|
|

 

[Guest]

Jason, thanks for the info. Everything went as planned except I have the
following WINS issues.

1) After I moved the WINS mdb to ServerD everything seems fine except I
can't get PUSH replication to work between ServerD and ServerB (PULL
replication appears to work fine - no errors). But, I get the following
error when attempting a PUSH replication.
=====================================================
Event Type: Error
Event Source: Wins
Event Category: None
Event ID: 4102
Date: 5/22/2005
Time: 10:26:20 AM
User: N/A
Computer: ServerD
Description: The connection was aborted by the remote WINS. Remote WINS may
not be configured to replicate with the server.
Data: 0000: 00000337 e0000008
==================================================

When I looked up this error, it appears to indicate that there is a TCP
issue (lack of connectivity issue). However I don't believe this is so as
PULL replication appears to works fine [shows OK in the win server
replication stats display and no errors are generated in event log] and the
Wins Owner Index values (highest ID) appear to be matching (changing -
updating) on all Wins databases (B,C & D).

----------

2) I pointed both ServerA and ServerD to ServerB for Wins during this
transition. After I finished I reset ServerD to point only to itself for
WINS and did PULL replications (could not do push replication see above).

I noticed that after the PULL replication was done the WINS records for
ServerD was split (two records own'd by ServerD and two records owned by
ServerB - 'split registration') within the ServerB Wins database (on ServerD
all four records are owned correctly by ServerD).

So on ServerB I manually removed the two ServerD records incorrectly owned
by ServerB, but even after several replication cycles the two ServerD records
I removed from ServerB have never been replicated back from ServerD (where
they exist and are correct) so the registration for ServerD on ServerB is two
records short. (The two missing records are the WorkStation and File Server
records).

Can you help me correct these two issues. thanks. - bill

 

[Jason Tan]

Hi Bill,

Thanks for posting!

Please understand that our newsgroup is an issue based service, meaning we
usually respond to one question/issue per post. This will lessen the
confusion for both of us, as well as ensure that our results are accurate
and not a result of a test for a different question. Therefore, I will
work with you on the first issue. Regarding the second issue, I suggest you
open a new post so that the dedicated MS engineer can help you on it in a
more efficient manner. Thanks for your understanding and support!

Based on my research, I would like to provide you with the following
article for your reference:

1. The very first thing to check for is a reboot of the Wins Server.

2. Please refer to following article to troubleshoot the issue.
=======================================================
137849 Event 4102 Error with WINS Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;137849

Troubleshooting WINS error event ID 4102, 4243, 4242, and 4286 messages
http://support.microsoft.com/default.aspx?scid=kb;en-us;321208

Recommended Practices for WINS
http://support.microsoft.com/default.aspx?scid=kb;en-us;185786

Hope the information helps. If there is anything that is unclear, please
feel free to let me know.

Thanks & Regards,

Jason Tan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Replacing a DC which has Wins & DNS services by
re-addressing.
| thread-index: AcVfulTedwna0G43QsKO+Ytn6wyzhQ==
| X-WBNR-Posting-Host: 150.131.128.43
| From: "=?Utf-8?B?QmlsbC1NVA==?=" <[email protected]>
| References: <[email protected]>
<[email protected]>
| Subject: RE: Replacing a DC which has Wins & DNS services by
re-addressing.
| Date: Mon, 23 May 2005 10:10:34 -0700
| Lines: 48
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.win2000.networking
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.networking:24095
| X-Tomcat-NG: microsoft.public.win2000.networking
|
| Jason, thanks for the info. Everything went as planned except I have the
| following WINS issues.
|
| 1) After I moved the WINS mdb to ServerD everything seems fine except I
| can't get PUSH replication to work between ServerD and ServerB (PULL
| replication appears to work fine - no errors). But, I get the following
| error when attempting a PUSH replication.
| =====================================================
| Event Type: Error
| Event Source: Wins
| Event Category: None
| Event ID: 4102
| Date: 5/22/2005
| Time: 10:26:20 AM
| User: N/A
| Computer: ServerD
| Description: The connection was aborted by the remote WINS. Remote WINS
may
| not be configured to replicate with the server.
| Data: 0000: 00000337 e0000008
| ==================================================
|
| When I looked up this error, it appears to indicate that there is a TCP
| issue (lack of connectivity issue). However I don't believe this is so
as
| PULL replication appears to works fine [shows OK in the win server
| replication stats display and no errors are generated in event log] and
the
| Wins Owner Index values (highest ID) appear to be matching (changing -
| updating) on all Wins databases (B,C & D).
|
| ----------
|
| 2) I pointed both ServerA and ServerD to ServerB for Wins during this
| transition. After I finished I reset ServerD to point only to itself for
| WINS and did PULL replications (could not do push replication see above).

|
| I noticed that after the PULL replication was done the WINS records for
| ServerD was split (two records own'd by ServerD and two records owned by
| ServerB - 'split registration') within the ServerB Wins database (on
ServerD
| all four records are owned correctly by ServerD).
|
| So on ServerB I manually removed the two ServerD records incorrectly
owned
| by ServerB, but even after several replication cycles the two ServerD
records
| I removed from ServerB have never been replicated back from ServerD
(where
| they exist and are correct) so the registration for ServerD on ServerB is
two
| records short. (The two missing records are the WorkStation and File
Server
| records).
|
| Can you help me correct these two issues. thanks. - bill
|
|

 

[Guest]

Jason, thanks for the references. Problem one appears to have gone away on
its own.
After a series of PULL replications, I re-enabled PUSH replication between
servers and I no longer get error 4102. I did review the references you sent
below and have enabled advanced detail logging on the servers in question.
So maybe that will help me resolve issue 2.

thanks for your time. - bill

 

[Jason Tan]

Hi bill,

Thanks for your update! I am glad to hear that the information helps. If
you have any concerns or questions, please do not hesitate to post back!

Thanks & Regards,

Jason Tan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Replacing a DC which has Wins & DNS services by
re-addressing.
| thread-index: AcVgiFW++N5CTG7mSymh9FDYvoWUAQ==
| X-WBNR-Posting-Host: 150.131.131.193
| From: "=?Utf-8?B?QmlsbC1NVA==?=" <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
| Subject: RE: Replacing a DC which has Wins & DNS services by
re-addressing.
| Date: Tue, 24 May 2005 10:45:12 -0700
| Lines: 47
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.win2000.networking
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.networking:24138
| X-Tomcat-NG: microsoft.public.win2000.networking
|
| Jason, thanks for the references. Problem one appears to have gone away
on
| its own.
| After a series of PULL replications, I re-enabled PUSH replication
between
| servers and I no longer get error 4102. I did review the references you
sent
| below and have enabled advanced detail logging on the servers in
question.
| So maybe that will help me resolve issue 2.
|
| thanks for your time. - bill
|
| "Jason Tan (MSFT)" wrote:
| > and not a result of a test for a different question. Therefore, I will
| > work with you on the first issue. Regarding the second issue, I suggest
you
| >
| > Based on my research, I would like to provide you with the following
| > article for your reference:
| > 1. The very first thing to check for is a reboot of the Wins Server.
| > 2. Please refer to following article to troubleshoot the issue.
| > 137849 Event 4102 Error with WINS Server
| > http://support.microsoft.com/default.aspx?scid=kb;en-us;137849
| > Troubleshooting WINS error event ID 4102, 4243, 4242, and 4286 messages
| > http://support.microsoft.com/default.aspx?scid=kb;en-us;321208
| > Recommended Practices for WINS
| > http://support.microsoft.com/default.aspx?scid=kb;en-us;185786
| > Hope the information helps. If there is anything that is unclear,
please
| > feel free to let me know.
| > Jason Tan
| > =====================================================
| > | 1) After I moved the WINS mdb to ServerD everything seems fine except
I
| > | can't get PUSH replication to work between ServerD and ServerB (PULL
| > | replication appears to work fine - no errors). But, I get the
following
| > | error when attempting a PUSH replication.
| =====================================================
| > | Event Type: Error
| > | Event Source: Wins
| > | Event ID: 4102
| > | Description: The connection was aborted by the remote WINS. Remote
WINS
| > | not be configured to replicate with the server.
| > | Data: 0000: 00000337 e0000008
| > | ==================================================
| > |
| > | When I looked up this error, it appears to indicate that there is a
TCP
| > | issue (lack of connectivity issue). However I don't believe this is
so as
| > | PULL replication appears to works fine [shows OK in the win server
| > | replication stats display and no errors are generated in event log]
and
| > | Wins Owner Index values (highest ID) appear to be matching (changing
-
| > | updating) on all Wins databases (B,C & D).
|
|