Re: Replicate Wins problem

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


"Herb Martin" wrote:

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]

"Micke__1" <Micke1@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:272AAFE6-EA7D-47D3-855F-2312B3AEE57E@xxxxxxxxxxxxxxxx
Herb,


"Herb Martin" wrote:

"Micke__1" <Micke1@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C46AB4F8-2302-412A-ABBA-77B11EC78E3B@xxxxxxxxxxxxxxxx
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]

"Herb Martin" wrote:

"Micke__1" <Micke1@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:80321092-EA75-4A2E-932A-B43A73903D46@xxxxxxxxxxxxxxxx
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?









.

Relevant Pages

  • RE: User account locked out from only one DC
    ... I performed "replicate now" from both DCs but the problems still exist. ... Showrepl works fine for DC2, but running it for DC1 ... "Naming information cannot be located because: Logon Failure: unknown user ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replicate Wins problem
    ... Its only the replication between dc1 and dc2 that is the problem. ... DC2 won't replicate? ... have to have each one as a Pull and Push PARTNERS ... Force some to register directly with DC2-WINS ...
    (microsoft.public.win2000.networking)
  • AD replication not working
    ... At first, DC1 could take entries in the AD but could not use those entries after they were inputted, even though those objects replicated to DC2; meaning it shows up in AD UC, but is not available to add to NTFS permissions on a DC1 hard drive. ... It allows me to resume or restart but it doesn't help the DC's replicate. ... This can occur when the target server principal name is registered on an account other than the account the target service is using. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Adding to the "replicate to" in NTDS settings
    ... bottom section there is a Replicate to: ... dc1 site has vpn to dc2 and dc3 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Changing the Administrator user name
    ... I changed the built-in administrator name Administrator to WinAdmin on DC1 ... The name change was replicated to DC2. ... Most likely a failure to replicate. ...
    (microsoft.public.win2000.active_directory)
Loading