Re: WINS frustration

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



So what I understand from the hub-and-spoke design model is that one
WINS server (DC1) is the "master". DC1 replication partners would be
DC2, DC3 and DC4. No replication partners for DC2, DC3 and DC4 other
than DC1.

Based on the sample design, it seemed to be for a WAN....I am sure this
applies to a LAN as well.

Is it not wise to set replications amongst all or is this just asking
for trouble...as what I am experiencing now.


Paul Bergson [MVP-DS] wrote:
What I have found is you want to use a hub and spoke model. Any place I
have been to when converted to this model problems have gone away. Things
have changed over the years and I don;t really touch WINS much any more but
I would recommend you try this and get your netbios name services working
before attempting anything with your environment.

http://technet2.microsoft.com/WindowsServer/en/library/ed9beba0-f998-47d2-8137-a2fc52886ed71033.mspx?mfr=true



--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"BlueIT" <bijal.shah@xxxxxxxxxx> wrote in message
news:1160413677.218692.61820@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have four WINS servers: DC1,DC2,DC3,DC4. I have a 2000 AD
enviroment, attempting migration to 2003. DC1 and DC2 are 2000 server
machines. DC3 and DC4 are 2003 server machines. There is also a
trusted domain with two WINS servers as well (TRUST1 and TRUST2).

The setup is this
DC1 replication parthers all set to Push/Pull......D2, DC3, DC4, TRUST1
and TRUST2
DC2 replication parthers all set to Push/Pull......D1, DC3, DC4, TRUST1
and TRUST2
DC3 replication parthers all set to Push/Pull......D1, DC2, DC4, TRUST1
and TRUST2
DC4 replication parthers all set to Push/Pull......D1, DC2, DC3, TRUST1
and TRUST2

DC1, DC2 and DC3 I get the following error in Event Viewer (System).

Event ID: 4102
The connection was aborted by the remote WINS. Remote WINS may not be
configured to replicate with the server.

Using the Display Server Statistics in the WINS console I view the
following:

DC1 failing to replicate with DC3 and DC4. Since the last restart 1/6
failed.
DC2 failing to replicate with DC1, DC3 and DC4. Since the last restart
1/6 failed.
DC3 failing to replicate with DC3. Since the last restart 1/6 failed.
DC4 seems good so far, but won't be surprise of failures.

Any help appreciated and thanks in advance


.



Relevant Pages

  • Re: Replicate Wins problem
    ... Its only the replication between dc1 and dc2 that is the problem. ... I have set that it just should replicate to partners. ... EVERY machine (DCs, servers, WINS server, and clients) needs to ...
    (microsoft.public.win2000.networking)
  • RE: Firewall Rule Set not allowing access to DNS servers?
    ... # Allow out access to my ISP's Domain name server. ... Firewall Rule Set not allowing access to DNS servers? ... but I never said dc1 was my inside nic. ...
    (freebsd-questions)
  • Re: 2k3 keep hanging?
    ... Verifying that the local machine DC1, ... Connecting to directory service on server DC1. ... Latency information for 1 entries in the vector were ignored. ... The File Replication Service SYSVOL ready test ...
    (microsoft.public.windows.server.general)
  • Re: Event id 2042 /2041 (Directory service) + 12292/11 (VSS)
    ... The Active Directory cannot replicate with this server ... ime since the last replication with this server has exceeded the ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event id 2042 /2041 (Directory service) + 12292/11 (VSS)
    ... The Active Directory cannot replicate with this server because ... ime since the last replication with this server has exceeded the tombstone ...
    (microsoft.public.windows.server.active_directory)