Further WINS difficulties
Nick Smith
Go back to basics, the PDC and BDC do not necessarily have to be WINS
servers. Depending on the size of your network 2 WINS servers should be
sufficient.
There is confusion as to how the WINS servers should be set up because MS
suggests both methods. Method 1 the WINS server points to itself as Primary
and elsewhere for Secondary. Method 2 sets bboth Primary and Secondary to
itself. Depends which articles you see.
I use method 2 and it works very well.
You can tell if replication has worked because the WINS manager will tell
you when replication last occured. Double clik on your WINS server IP
adddress in the LHS panel and the details appear to the Right panel.
The WINS servers should be both Push and Pull partners with each other.
I have 2 WINS servers in my head office (Sydney) which handles all WINS for
our Australian & New Zealand operations, branches in major capital cities ie
geographically almost as big as the USA. And my network works fine.
--
Nick Smith
nick...@inorbit.com
Eye of the Storm wrote in message
<36717041...@msnews.microsoft.com>...
>I recently posted asking about some difficulties in getting WINS to
replicate. To
>tell you the truth, I can't even figure out if any replication is going on.
How
>exactly do you tell? If I initiate replication manually, I get no errors
in the
>event log.
>
>Anyway, I have read a few articles in the knoweldge base concerning WINS
issues,
>specifically the danger of split-registrations. One of the things they
mention is
>that any WINS server itself should have the TCP/IP properties, WINS
addresses set to
>point to itself as both primary and secondary.
>
>Given that this network was thrown together overnight with absolutely no
planning I
>found many different types of settings on the various BDC's. One had
itself as
>primary and the PDC as secondary, one had the PDC as primary and itself as
secondary,
>one had the PDC as primary and nothing as secondary.
>
>So I broke all replication ties (some had only one side set for
replication, so this
>was never working anyway). Then I tried setting the TCP/IP properties WINS
addresses
>to point to itself as both primary and secondary WINS servers.
>
>The problem is that when this is done each BDC's loses name resolution,
with the
>exception of it's own subnet (one BDC per subnet over a WAN). The PDC does
not lose
>name resolution with these settings.
>
>So on each BDC, the browser is useless other than for it's own subnet. But
I can
>still type \\pdc on the run line and get a connection.
>
>Is anyone familiar with the cause of this situation? Is it a problem with
the
>routers, or rather a need to reconfigure the routers so the BDC's are not
dependent
>on the PDC's WINS server?
>
>
>E-mail Name: dpdragon
>E-mail Address: @execpc.com
>
>"But how is this legal plunder to be identified? Quite simply. See if
>the law takes from some persons what belongs to them, and gives it to
>other persons to whom it does not belong. See if the law benefits one
>citizen at the expense of another by doing what the citizen himself
>cannot do without committing a crime."
> - Frederic Bastiat, The Law [1850]
>
>------------------------------------------------------------------------
>To Respond By E-mail: please combine the e-mail name and address listed
above.