I would also mention that we are able to use WINS sometimes to locate rogue Windows machines that don't show up anywhere else short of network sniffing.
From: Andrew S. Baker [mailto:[email protected]] Sent: Wednesday, April 21, 2010 3:39 PM To: NT System Admin Issues Subject: Re: WINS (- was RE: Domain controllers, what is supposed to happen.) I tried removing it on my home network about 12-18 months ago (might even be 24 months) and it was more painful than it was worth. Nothing catastrophic, IIRC, but scripts that depend on the browse list failed. In work environments there are still some apps that support NetBIOS and expect to be able to find this via this protocol. I've found it easier to just configure properly and leave in place. -ASB: http://XeeSM.com/AndrewBaker On Wed, Apr 21, 2010 at 5:41 PM, Micheal Espinola Jr <[email protected]<mailto:[email protected]>> wrote: +1. I've learned the hard-way, that its not worth removing in most circumstances. -- ME2 On Wed, Apr 21, 2010 at 7:21 AM, Ben Scott <[email protected]<mailto:[email protected]>> wrote: On Wed, Apr 21, 2010 at 10:17 AM, Raper, Jonathan - Eagle <[email protected]<mailto:[email protected]>> wrote: > Speaking of WINS, if you don't have any non-windows or pre-w2k clients, is > there ANY good reason to keep WINS running on your network? If so, why? If you're using NetBIOS at all, I strongly recommend WINS. Getting rid of NetBIOS sometimes proves problematic. Aside from vestigial dependencies in some software, it's also what drives the browse list ("Network Neighborhood" or whatever it's called this year). But yah, if you can shut off NetBIOS, that's a beautiful thing, and then you don't need WINS. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
