Proposed WINS Changes
About 3 years ago, we laid the groundwork for migrating the WINS servers to a new "MUSC" domain. This effort has been abandoned (for reasons beyond this discussion) so we have to undo what we did; that is, move the WINS servers back to the ClinLAN domain and dismantle the MUSC domain. Before we can make these changes, we need to discuss with you what it will mean to remove the 128.23.203.142 address.Current Configuration:
We have two WINS servers via DHCP:
-- The primary WINS server, DC03: 128.23.110.2
-- A secondary WINS server, DC01: 128.23.9.111. DC01 also has a second NIC, 128.23.203.142, which is not resolved by DHCP. This address was introduced as part of the MUSC domain migration plan.
There are two additional WINS servers that are not assigned via DHCP:
-- DC2: 128.23.9.31
-- DC02: 128.23.9.112
The three secondary WINS servers have a push/pull relationship with the hub; that is, when a change to a secondary WINS server's data records is made, it can be pushed to the hub and then pushed to the other secondary servers or pulled from the host by them.
How WINS Is Used:
Devices that use WINS contact a WINS server by either its name (e.g.,DC01) or its address (.9.111 or .203.142); this server becomes the owner of the device's record. For example, if your device points to "128.23.203.142", the database on DC01 is updated.
This is where the problem comes in.
If you specify an address, such as .203.142, then that -address- owns the record, not the host, DC01. However, since the database resides on DC01, the host name is associated with the record and is propagated throughout the WINS community.
Now, the primary WINS server can understand when a secondary server has multiple NIC addresses; here, DC03 doesn't have a problem with .9.111 and .203.142 being two NICs in DC01. However, the secondary WINS servers cannot make a many-IP-address-to-one translation; consequently, DC2 and DC02 believe DC01 is .9.111 and only .9.111. When it sees that DC01 owns a device, it thinks .9.111 owns the device, not .203.142.
Systems getting their WINS information from DC2 or DC02 look to DC01 to find your device and assume the address that owns the record is .9.111. Since the IP address that owns the record is really .203.142, your device cannot be found. Eventually, the secondary controllers sort out the confusion and your device can be found by all of the secondary WINS servers.
Eventually. Depending on the frequency of the changes, the WINS servers can spend some time being confused as to what address on DC01 owns what record. As one record is sorted out, another can come in and nothing is correct. Replications are not consistent and completely unpredictable.
What's "Owned" by 128.23.203.142:
Four months ago, 25 machines were owned by .203.142. Currently, NO records are registered to that address. It would be nice to assume those 25 machines have been corrected or retired permanently but assumptions are always problematic. There may still be servers looking to the address, just have not registered with the address.
The Proposal:
I propose we take this opportunity to retire 128.23.203.142 so all WINS replications are accurate. Again, we cannot assume no server is looking for this address and needs to use it; therefore, I must to know if there are objections and what they are so we can work out a solution to benefit you and the entire MUSC community.Knowing it's the end of summer and a lot of people are cramming in vacations, I want to leave this discussion open for two weeks, closing on September 21st. If there are no objections, then we will move forward with 128.23.203.142's retirement.
Thank you for your feedback,
Michael J. Dixon