> Why should you use WINS in a full Active Directory domain? Wasn't it
> supposed to be replaced by DNS?
The answer is too complex to be given here... Basically it has to do with
the design of the browser service, browse lists, master browsers etc. If you
don't use browsing lists in general you can skip WINS altogether, but if you
want/need them you will eventually run into WINS sooner or later.
See the following article from the MS KB:
Troubleshooting browser Event ID 8021 and 8032 on master browsers
http://support.microsoft.com/kb/135404/en-us
Here's a quote:
[start quote]
Name resolution infrastructure
Name resolution among all browsers is very important. Therefore, make sure
that you establish a robust name resolution infrastructure with WINS. For
browsing to work correctly, name resolution must be functional. We strongly
recommend that all WINS servers point to themselves as Primary and Secondary
WINS in the TCP/IP configuration. (more stuff here)
[end quote]
Now, scroll down to the bottom of article and look at the "Applies To"
section. Surprise, surprise: Windows 2003, 2000 and virtually every other
Microsoft O/S that can act as a master browser is listed there.
Virgil