Replicate Wins problem

[Guest]

We use 2 windows 2000 DC that we have wins on, but we have some problem with
wins replication. Ive used it with NT4, and when we upgrade to w2000 for a
couple a years ago we didnt need it. But now for some reasons we need to use
it.

I've add the replication partner to the the two dc's and use push and pull.
I have set that it just should replicate to partners. But it doesnt replicate
anything.

Event ID:4141
WINS pulled records from a WINS while doing Pull replication. The partner's
address and the owner's address whose records were pulled are given in the
data section (second and third DWORD respectively). The number of records
pulled is the fourth DWORD.

***
and
Event ID: 4121

WINS's Replicator could not find any records in the WINS database. This
means there are no active or tombstone records in the database. It could be
that the records being requested by a remote WINS server have either been
released or do not exist.

***
But there is many wins records in the database.

I have looked in the registry and it seems to be correct. (Probalbly not,
but as far as I can see). I have also tried to replicate with another wins
server and it doesnt work, and I have also reinstalled the wins server, but
no success.

Any suggestions?

 

[Richard G. Harper]

If it were up to me, I'd uninstall WINS on both servers. Reinstall it on
one server only, then use DHCP (or whatever mechanism you use to send out
updated network information) to register the new WINS server as the primary
WINS server for all your clients.

Allow time for the server to populate and settle down - at least as much
time as your DHCP lease length, more if at all possible. Once the first
server is stable, set up the second server and configure it as a replication
partner with the first server. Let the replication take place and let
things settle down before sending out the second WINS server address as the
secondary WINS for the network.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Guest]

As I wrote Ive already tried to uninstall them, and reinstall them again.
Everyone on the lan is currently configured through dhcp to work on the first
wins, this is until we get the replication to work.

If it were up to me, I'd uninstall WINS on both servers. Reinstall it on
one server only, then use DHCP (or whatever mechanism you use to send out
updated network information) to register the new WINS server as the primary
WINS server for all your clients.

Allow time for the server to populate and settle down - at least as much
time as your DHCP lease length, more if at all possible. Once the first
server is stable, set up the second server and configure it as a replication
partner with the first server. Let the replication take place and let
things settle down before sending out the second WINS server address as the
secondary WINS for the network.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

We use 2 windows 2000 DC that we have wins on, but we have some problem
with
wins replication. Ive used it with NT4, and when we upgrade to w2000 for a
couple a years ago we didnt need it. But now for some reasons we need to
use
it.

I've add the replication partner to the the two dc's and use push and
pull.
I have set that it just should replicate to partners. But it doesnt
replicate
anything.

Event ID:4141
WINS pulled records from a WINS while doing Pull replication. The
partner's
address and the owner's address whose records were pulled are given in
the
data section (second and third DWORD respectively). The number of records
pulled is the fourth DWORD.

***
and
Event ID: 4121

WINS's Replicator could not find any records in the WINS database. This
means there are no active or tombstone records in the database. It could
be
that the records being requested by a remote WINS server have either been
released or do not exist.

***
But there is many wins records in the database.

I have looked in the registry and it seems to be correct. (Probalbly not,
but as far as I can see). I have also tried to replicate with another wins
server and it doesnt work, and I have also reinstalled the wins server,
but
no success.

Any suggestions?

 

[Herb Martin]

We use 2 windows 2000 DC that we have wins on, but we have some problem
with
wins replication. Ive used it with NT4, and when we upgrade to w2000 for a
couple a years ago we didnt need it. But now for some reasons we need to
use
it.

Practically everyone who needed WINS under NT4 still
needed/needs it under Win2000+ (Many just don't realize
it.)

I've add the replication partner to the the two dc's and use push and
pull.
I have set that it just should replicate to partners. But it doesnt
replicate
anything.

EVERY machine (DCs, servers, WINS server, and clients) needs to
be a WINS client on their NIC properties.

Removing WINS Server and re-installing it might be a good idea but
even that shouldn't be necessary if you just re-register ALL the WINS
clients (which is EVERY computer):

nbtstat -RR

(on each machine AND the CAPITALIZATION is necessary which
is very unusually for a Microsoft command.)

WINS's Replicator could not find any records in the WINS database. This
means there are no active or tombstone records in the database. It could
be
that the records being requested by a remote WINS server have either been
released or do not exist.

 

[Guest]

Every machine on the lan is configured against the wins on dc1. It works
fine. Its only the replication between dc1 and dc2 that is the problem. By
running nbtstat -RR will do them register against dc1 again which alreday
works, or is that another reason to do it?

We use 2 windows 2000 DC that we have wins on, but we have some problem
with
wins replication. Ive used it with NT4, and when we upgrade to w2000 for a
couple a years ago we didnt need it. But now for some reasons we need to
use
it.

Practically everyone who needed WINS under NT4 still
needed/needs it under Win2000+ (Many just don't realize
it.)

I've add the replication partner to the the two dc's and use push and
pull.
I have set that it just should replicate to partners. But it doesnt
replicate
anything.

EVERY machine (DCs, servers, WINS server, and clients) needs to
be a WINS client on their NIC properties.

Removing WINS Server and re-installing it might be a good idea but
even that shouldn't be necessary if you just re-register ALL the WINS
clients (which is EVERY computer):

nbtstat -RR

(on each machine AND the CAPITALIZATION is necessary which
is very unusually for a Microsoft command.)

WINS's Replicator could not find any records in the WINS database. This
means there are no active or tombstone records in the database. It could
be
that the records being requested by a remote WINS server have either been
released or do not exist.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

***
But there is many wins records in the database.

I have looked in the registry and it seems to be correct. (Probalbly not,
but as far as I can see). I have also tried to replicate with another wins
server and it doesnt work, and I have also reinstalled the wins server,
but
no success.

Any suggestions?

 

[Herb Martin]

Every machine on the lan is configured against the wins on dc1. It works
fine. Its only the replication between dc1 and dc2 that is the problem. By
running nbtstat -RR will do them register against dc1 again which alreday
works, or is that another reason to do it?

Ok, so you have them all registered with DC1 and
DC2 won't replicate? (And you have re-installed
DC2's WINS which you didn't mention the first time?)

Did you set EACH of them up as at least a PULL or
PUSH partner of the other? You do not necessarily
have to have each one as a Pull and Push PARTNERS
but each be allowed to PULL.

(Partner REALLY means "initiator".)

For completeness (not really required but likely no harm)
make sure that BOTH are Push and Pull Partners of EACH
OTHER -- from both in both directions.

Since they are DCs authnetication should not be an issue.

The error you received (no records) would be consistent
with DC2-WINS not having any clients and so not having
ANYTHING in the database. Do you get the same error
in the other direction? (The error could be innocuous if
only in one direction AND there is nothing available.)

Also every client can list both DC1-WINS and DC2-WINS
if you wish. Force some to register directly with DC2-WINS
to make sure you have a "database" initialized there -- I have
never heard of such an error but then I have always set up
my WINS server in "plain vanilla" fashion and seldom
experienced ANY of the problems other people have occasionally
reported.

Make sure you don't have any firewall issues -- either intermediate
(unlikely) or the XP-Basic (or third party) local firewalls.
Including no IPSec filter issues but you likely aren't doing that.

Make sure NetBIOS is enabled on the problem DC (WINS should
give EVEN more errors if it's now but I am trying to list everything
that I would check.)




--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

We use 2 windows 2000 DC that we have wins on, but we have some problem
with
wins replication. Ive used it with NT4, and when we upgrade to w2000
for a
couple a years ago we didnt need it. But now for some reasons we need
to
use
it.

Practically everyone who needed WINS under NT4 still
needed/needs it under Win2000+ (Many just don't realize
it.)

I've add the replication partner to the the two dc's and use push and
pull.
I have set that it just should replicate to partners. But it doesnt
replicate
anything.

EVERY machine (DCs, servers, WINS server, and clients) needs to
be a WINS client on their NIC properties.

Removing WINS Server and re-installing it might be a good idea but
even that shouldn't be necessary if you just re-register ALL the WINS
clients (which is EVERY computer):

nbtstat -RR

(on each machine AND the CAPITALIZATION is necessary which
is very unusually for a Microsoft command.)

WINS's Replicator could not find any records in the WINS database. This
means there are no active or tombstone records in the database. It
could
be
that the records being requested by a remote WINS server have either
been
released or do not exist.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

***
But there is many wins records in the database.

I have looked in the registry and it seems to be correct. (Probalbly
not,
but as far as I can see). I have also tried to replicate with another
wins
server and it doesnt work, and I have also reinstalled the wins server,
but
no success.

Any suggestions?

 

[Guest]

Herb,

Ok, so you have them all registered with DC1 and
DC2 won't replicate? (And you have re-installed
DC2's WINS which you didn't mention the first time?)

Its correct, thought I mention that, my mistake.

Did you set EACH of them up as at least a PULL or
PUSH partner of the other? You do not necessarily
have to have each one as a Pull and Push PARTNERS
but each be allowed to PULL.

I have configured both of them as push and pull, Ive tried to set the DC1 to
push and DC2 to pull, but its the same.. If I set both of them as PULL, can
that works. Dont I need one push and one pull? If I did that, should it be
it, or is there a security issue who could send their wins entryn to who?

(Partner REALLY means "initiator".)

For completeness (not really required but likely no harm)
make sure that BOTH are Push and Pull Partners of EACH
OTHER -- from both in both directions.

Since they are DCs authnetication should not be an issue.

The error you received (no records) would be consistent
with DC2-WINS not having any clients and so not having
ANYTHING in the database. Do you get the same error
in the other direction? (The error could be innocuous if
only in one direction AND there is nothing available.)

There is entryn in the database, both dynamic, and static.

Also every client can list both DC1-WINS and DC2-WINS
if you wish. Force some to register directly with DC2-WINS
to make sure you have a "database" initialized there -- I have
never heard of such an error but then I have always set up
my WINS server in "plain vanilla" fashion and seldom
experienced ANY of the problems other people have occasionally
reported.

If I configure a client to DC2 the nebios name is registerd correctly, but
it cant replicate it to my DC1.

Make sure you don't have any firewall issues -- either intermediate
(unlikely) or the XP-Basic (or third party) local firewalls.
Including no IPSec filter issues but you likely aren't doing that.

No such thing here..

Make sure NetBIOS is enabled on the problem DC (WINS should
give EVEN more errors if it's now but I am trying to list everything
that I would check.)

NetBios is enabled on both servers.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

We use 2 windows 2000 DC that we have wins on, but we have some problem
with
wins replication. Ive used it with NT4, and when we upgrade to w2000
for a
couple a years ago we didnt need it. But now for some reasons we need
to
use
it.

Practically everyone who needed WINS under NT4 still
needed/needs it under Win2000+ (Many just don't realize
it.)

I've add the replication partner to the the two dc's and use push and
pull.
I have set that it just should replicate to partners. But it doesnt
replicate
anything.

EVERY machine (DCs, servers, WINS server, and clients) needs to
be a WINS client on their NIC properties.

Removing WINS Server and re-installing it might be a good idea but
even that shouldn't be necessary if you just re-register ALL the WINS
clients (which is EVERY computer):

nbtstat -RR

(on each machine AND the CAPITALIZATION is necessary which
is very unusually for a Microsoft command.)

WINS's Replicator could not find any records in the WINS database. This
means there are no active or tombstone records in the database. It
could
be
that the records being requested by a remote WINS server have either
been
released or do not exist.




--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

***
But there is many wins records in the database.

I have looked in the registry and it seems to be correct. (Probalbly
not,
but as far as I can see). I have also tried to replicate with another
wins
server and it doesnt work, and I have also reinstalled the wins server,
but
no success.

Any suggestions?

 

[Herb Martin]

I have configured both of them as push and pull, Ive tried to set the DC1

to
push and DC2 to pull, but its the same..

That would only replicate ONE WAY which is generally
bad. Two PULLs are the usual case for WANS where one
much control replication carefully.

Two PULL AND PUSH partners are the usual case for LANS
or WANS where replication control is not an overriding concern.

Go back and check and make sure EACH side is able to pull
changes (or both set to both.)

If I set both of them as PULL, can
that works. Dont I need one push and one pull? If I did that, should it be
it, or is there a security issue who could send their wins entryn to who?

Yes, as long as both are PULL PARTNERS they will INITIATE
their own pull based based on time.

(Actually both could be set to PUSH PARTNER and they would
initiate the transfer to their partner so each would get changes too
but that is an unusual setup design.)

There is entryn in the database, both dynamic, and static.



If I configure a client to DC2 the nebios name is registerd correctly, but
it cant replicate it to my DC1.

Sounds like DC1 is NOT set to PULL (and DC2 not set to PUSH to it.)

No such thing here..

Well, watch out for the BASIC (XP-like) firewall on EVERY server.

You of course DO have that if you running Win2003, but may not
have it if you are running Win2000.

NetBios is enabled on both servers.

And the DCs themselves should be WINS clients but I can't
think how this mistake (if you didn't do this) would cause
your specific problems.

Version of the OS and SP/hotfix status?

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Herb,

Ok, so you have them all registered with DC1 and
DC2 won't replicate? (And you have re-installed
DC2's WINS which you didn't mention the first time?)

Its correct, thought I mention that, my mistake.

Did you set EACH of them up as at least a PULL or
PUSH partner of the other? You do not necessarily
have to have each one as a Pull and Push PARTNERS
but each be allowed to PULL.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

:

We use 2 windows 2000 DC that we have wins on, but we have some
problem
with
wins replication. Ive used it with NT4, and when we upgrade to w2000
for a
couple a years ago we didnt need it. But now for some reasons we
need
to
use
it.

Practically everyone who needed WINS under NT4 still
needed/needs it under Win2000+ (Many just don't realize
it.)

I've add the replication partner to the the two dc's and use push
and
pull.
I have set that it just should replicate to partners. But it doesnt
replicate
anything.

EVERY machine (DCs, servers, WINS server, and clients) needs to
be a WINS client on their NIC properties.

Removing WINS Server and re-installing it might be a good idea but
even that shouldn't be necessary if you just re-register ALL the WINS
clients (which is EVERY computer):

nbtstat -RR

(on each machine AND the CAPITALIZATION is necessary which
is very unusually for a Microsoft command.)

WINS's Replicator could not find any records in the WINS database.
This
means there are no active or tombstone records in the database. It
could
be
that the records being requested by a remote WINS server have either
been
released or do not exist.




--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

***
But there is many wins records in the database.

I have looked in the registry and it seems to be correct. (Probalbly
not,
but as far as I can see). I have also tried to replicate with
another
wins
server and it doesnt work, and I have also reinstalled the wins
server,
but
no success.

Any suggestions?

 

[Guest]

Hi Herb,

Thanx for you support. I believe I have to rtfm or something. Ive installed
2 2k DCs running in mixed mode, and 1 XP pro in vmware to test it.

Dc1 and Dc2 have wins pointed at them selves.
XP point at Dc1.
Replicationpartners to eachother with push and pull

When I goes in to wins statistics it says that it has replicated once.. but
my XP record doesnt shows in Dc2.

I go back to the manual to read how it should work, obviously I have missed
something

br
Micke

I have configured both of them as push and pull, Ive tried to set the DC1
to
push and DC2 to pull, but its the same..

That would only replicate ONE WAY which is generally
bad. Two PULLs are the usual case for WANS where one
much control replication carefully.

Two PULL AND PUSH partners are the usual case for LANS
or WANS where replication control is not an overriding concern.

Go back and check and make sure EACH side is able to pull
changes (or both set to both.)

If I set both of them as PULL, can
that works. Dont I need one push and one pull? If I did that, should it be
it, or is there a security issue who could send their wins entryn to who?

Yes, as long as both are PULL PARTNERS they will INITIATE
their own pull based based on time.

(Actually both could be set to PUSH PARTNER and they would
initiate the transfer to their partner so each would get changes too
but that is an unusual setup design.)

There is entryn in the database, both dynamic, and static.



If I configure a client to DC2 the nebios name is registerd correctly, but
it cant replicate it to my DC1.

Sounds like DC1 is NOT set to PULL (and DC2 not set to PUSH to it.)

No such thing here..

Well, watch out for the BASIC (XP-like) firewall on EVERY server.

You of course DO have that if you running Win2003, but may not
have it if you are running Win2000.

NetBios is enabled on both servers.

And the DCs themselves should be WINS clients but I can't
think how this mistake (if you didn't do this) would cause
your specific problems.

Version of the OS and SP/hotfix status?

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Herb,

Every machine on the lan is configured against the wins on dc1. It
works
fine. Its only the replication between dc1 and dc2 that is the problem.
By
running nbtstat -RR will do them register against dc1 again which
alreday
works, or is that another reason to do it?


Ok, so you have them all registered with DC1 and
DC2 won't replicate? (And you have re-installed
DC2's WINS which you didn't mention the first time?)

Its correct, thought I mention that, my mistake.

Did you set EACH of them up as at least a PULL or
PUSH partner of the other? You do not necessarily
have to have each one as a Pull and Push PARTNERS
but each be allowed to PULL.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

:

We use 2 windows 2000 DC that we have wins on, but we have some
problem
with
wins replication. Ive used it with NT4, and when we upgrade to w2000
for a
couple a years ago we didnt need it. But now for some reasons we
need
to
use
it.

Practically everyone who needed WINS under NT4 still
needed/needs it under Win2000+ (Many just don't realize
it.)

I've add the replication partner to the the two dc's and use push
and
pull.
I have set that it just should replicate to partners. But it doesnt
replicate
anything.

EVERY machine (DCs, servers, WINS server, and clients) needs to
be a WINS client on their NIC properties.

Removing WINS Server and re-installing it might be a good idea but
even that shouldn't be necessary if you just re-register ALL the WINS
clients (which is EVERY computer):

nbtstat -RR

(on each machine AND the CAPITALIZATION is necessary which
is very unusually for a Microsoft command.)

WINS's Replicator could not find any records in the WINS database.
This
means there are no active or tombstone records in the database. It
could
be
that the records being requested by a remote WINS server have either
been
released or do not exist.




--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

***
But there is many wins records in the database.

I have looked in the registry and it seems to be correct. (Probalbly
not,
but as far as I can see). I have also tried to replicate with
another
wins
server and it doesnt work, and I have also reinstalled the wins
server,
but
no success.

Any suggestions?

 

[Herb Martin]

Hi Herb,

Thanx for you support. I believe I have to rtfm or something.

We don't generally tell you to do that (directly); it's
general practice here to try to answer your questions
or AT LEAST point out the FINE MANUAL or web page.

Personally I have no problem with being told to RTFM

Ive installed
2 2k DCs running in mixed mode, and 1 XP pro in vmware to test it.

Dc1 and Dc2 have wins pointed at them selves.

Usually fine -- no particular rule here and network
efficiency says you are correct. You can also put
in the "other" as the second WINS server etc.

XP point at Dc1.
Replicationpartners to eachother with push and pull

Make sure you have them exchaning changes in BOTH
directions -- the GUI is a LITTLE confusing although
the Win2000+ version are much clearer than was NT
server.

When I goes in to wins statistics it says that it has replicated once..
but
my XP record doesnt shows in Dc2.

Shows in DC1-WINS, they seem to replicate, yet doesn't show
in DC2-WINS?

I go back to the manual to read how it should work, obviously I have
missed
something

Actually the manual isn't likely much help here.

Do these things: In the GUI for WINS check that EACH
server has a Push and a Pull partnership with the OTHER.
Make sure the properties are sensible.

Check the EVEN log for any errors.

Then search the MS Site OR the built-in help for troubleshooting
methods AND ask here with specifics....



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

br
Micke

I have configured both of them as push and pull, Ive tried to set the
DC1
to
push and DC2 to pull, but its the same..

That would only replicate ONE WAY which is generally
bad. Two PULLs are the usual case for WANS where one
much control replication carefully.

Two PULL AND PUSH partners are the usual case for LANS
or WANS where replication control is not an overriding concern.

Go back and check and make sure EACH side is able to pull
changes (or both set to both.)

If I set both of them as PULL, can
that works. Dont I need one push and one pull? If I did that, should it
be
it, or is there a security issue who could send their wins entryn to
who?

Yes, as long as both are PULL PARTNERS they will INITIATE
their own pull based based on time.

(Actually both could be set to PUSH PARTNER and they would
initiate the transfer to their partner so each would get changes too
but that is an unusual setup design.)

(Partner REALLY means "initiator".)

For completeness (not really required but likely no harm)
make sure that BOTH are Push and Pull Partners of EACH
OTHER -- from both in both directions.

Since they are DCs authnetication should not be an issue.

The error you received (no records) would be consistent
with DC2-WINS not having any clients and so not having
ANYTHING in the database. Do you get the same error
in the other direction? (The error could be innocuous if
only in one direction AND there is nothing available.)

There is entryn in the database, both dynamic, and static.


Also every client can list both DC1-WINS and DC2-WINS
if you wish. Force some to register directly with DC2-WINS
to make sure you have a "database" initialized there -- I have
never heard of such an error but then I have always set up
my WINS server in "plain vanilla" fashion and seldom
experienced ANY of the problems other people have occasionally
reported.

If I configure a client to DC2 the nebios name is registerd correctly,
but
it cant replicate it to my DC1.

Sounds like DC1 is NOT set to PULL (and DC2 not set to PUSH to it.)

Make sure you don't have any firewall issues -- either intermediate
(unlikely) or the XP-Basic (or third party) local firewalls.
Including no IPSec filter issues but you likely aren't doing that.

No such thing here..

Well, watch out for the BASIC (XP-like) firewall on EVERY server.

You of course DO have that if you running Win2003, but may not
have it if you are running Win2000.

Make sure NetBIOS is enabled on the problem DC (WINS should
give EVEN more errors if it's now but I am trying to list everything
that I would check.)

NetBios is enabled on both servers.

And the DCs themselves should be WINS clients but I can't
think how this mistake (if you didn't do this) would cause
your specific problems.

Version of the OS and SP/hotfix status?

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Herb,


:

Every machine on the lan is configured against the wins on dc1. It
works
fine. Its only the replication between dc1 and dc2 that is the
problem.
By
running nbtstat -RR will do them register against dc1 again which
alreday
works, or is that another reason to do it?


Ok, so you have them all registered with DC1 and
DC2 won't replicate? (And you have re-installed
DC2's WINS which you didn't mention the first time?)

Its correct, thought I mention that, my mistake.


Did you set EACH of them up as at least a PULL or
PUSH partner of the other? You do not necessarily
have to have each one as a Pull and Push PARTNERS
but each be allowed to PULL.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

:

We use 2 windows 2000 DC that we have wins on, but we have some
problem
with
wins replication. Ive used it with NT4, and when we upgrade to
w2000
for a
couple a years ago we didnt need it. But now for some reasons we
need
to
use
it.

Practically everyone who needed WINS under NT4 still
needed/needs it under Win2000+ (Many just don't realize
it.)

I've add the replication partner to the the two dc's and use push
and
pull.
I have set that it just should replicate to partners. But it
doesnt
replicate
anything.

EVERY machine (DCs, servers, WINS server, and clients) needs to
be a WINS client on their NIC properties.

Removing WINS Server and re-installing it might be a good idea but
even that shouldn't be necessary if you just re-register ALL the
WINS
clients (which is EVERY computer):

nbtstat -RR

(on each machine AND the CAPITALIZATION is necessary which
is very unusually for a Microsoft command.)

WINS's Replicator could not find any records in the WINS
database.
This
means there are no active or tombstone records in the database.
It
could
be
that the records being requested by a remote WINS server have
either
been
released or do not exist.




--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

***
But there is many wins records in the database.

I have looked in the registry and it seems to be correct.
(Probalbly
not,
but as far as I can see). I have also tried to replicate with
another
wins
server and it doesnt work, and I have also reinstalled the wins
server,
but
no success.

Any suggestions?