WINS Replication from NT to 2000

[Rich Nielsen]

I am trying to replicate (and then setup dynamically) my
NT 4.0 WINS database to a W2K database, but I am not
having much success. The NT server sits across a subnet
through a fast ethernet port on a router, but I have
opened up multicasting to allow for even that type of
traffic. I am trying to "push" traffic from the NT
machine to the 2000 machine. When I try to push from the
NT machine, it tells me the request has been queued.
However, the event log on the 2000 machine gives an error -
Event 4102. It says, "The connection was aborted by the
remote WINS. Remote WINS may not be configured to
replicate with the server. I swear I have tried every
configuration possible, and I even finally tried to go
straight by the book! Nothing works! Any ideas what I
might be doing wrong?

 

[Marc Reynolds [MSFT]]

Have you set up the Windows 2000 Server as a replication partner of the NT
Wins server as well?

--

Thanks,
Marc Reynolds
Microsoft Technical Support

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

 

[Guest]

This is where things can get really confusing, but it can
be easy to understand if you can keep them straight. I am
assuming the NT 4.0 server, which everyone has listed as
the Primary WINS server (DHCP assigned) is the replication
partner that will "push" the changes down to the new
Windows 2000 Server running WINS. The Windows 2000 server
is the "pull" partner.

On the NT 4.0 Server, I added the new W2K WINS server
through its NetBIOS name by clicking on the Add WINS
Server Selection under the Server menu. By selecting
Replication Partners on either server listed, it shows the
NT 4.0 Server as having a check mark under both the Push
and Pull, with black arrows pointing to the left on the NT
4.0 Server. The WINS Servers To List down below shows a
check box on Push Partners and Other. The Pull Partners
box is not checked. The Replications Options box shows a
check mark on both the Push Partners and Pull Partners.

On the W2K box, the WINS snap-in shows both servers as
well. The NT 4.0 server shows the W2K as a replication
PULL partner, whereas the W2K server shows the NT 4.0 as a
replication PUSH partner.

Every 1/2 hour the W2K event viewer displays the Event
4102 event.

Incidentally, the Windows 2000 Server shows you all the NT
4.0 WINS database on the Windows 2000 server (under Active
Registrations), but the Active Registrations on the
Windows 2000 WINS server only shows perhaps one-sixth of
the entire database. So how come a few of those addresses
are popping up in there? I have no idea!

 

[Marc Reynolds [MSFT]]

You probably want to set up your replication as push/pull both directions.
If the computers list one Wins server as Primary and the other as Secondary
some will end up registering with the secondary at some point. This happens
because there may be times when the primary Wins server is too busy or not
available and the clients switch to the secondary.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

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

 

[Guest]

Marc,

I took your advice and configured it based on your advice
for push/pull.

However, while the Event ID 4102 is no longer showing up
in the Event Viewer, replication is still not taking
place.

Do I need to get rid of the replication setup on the NT
Server 4.0 box running WINS?

Rich

 

[Rich Nielsen]

I was wrong. Replication was actually occurring. I had
to close the application and reopen it in order for it to
refresh. Why? I don't know. It's Microsoft!