WINS Design

Working on our AD child domain design and was curious how
others have implemented WINS.

We will be a single child domain that will have 16 unique
sites over VPN connections. Should I setup only a SINGLE
WINS server at the "head" of the VPN tunnels, or should
there be WINS servers located closer to each resource on
the insides of the VPNs?

Each site will have at least 1 DC/GC.

Some say one way, others another. Be curious what others
have done in a similar design where you are a single
domain across WAN connections.

If your clients are 2K or XP, there is no need for WINS. I wouldn't even
use it.

"Dave Clark" <(E-Mail Removed)> wrote in message
news:5e7d01c42df4$c3e10270$(E-Mail Removed)...
> Working on our AD child domain design and was curious how
> others have implemented WINS.
>
> We will be a single child domain that will have 16 unique
> sites over VPN connections. Should I setup only a SINGLE
> WINS server at the "head" of the VPN tunnels, or should
> there be WINS servers located closer to each resource on
> the insides of the VPNs?
>
> Each site will have at least 1 DC/GC.
>
> Some say one way, others another. Be curious what others
> have done in a similar design where you are a single
> domain across WAN connections.
>

As much as I would like to get rid of NETBios resolution
we have found in our testing that too many applications
that we are running just don't work without it. We need
to keep WINS for a while now, even though we are only
going to be allowing 2000+ clients into the new network.

>-----Original Message-----
>If your clients are 2K or XP, there is no need for
WINS. I wouldn't even
>use it.