If everything you want works without it, go ahead. If you start getting
odd problems with printers or backups or an application which has Netbios
names hardwired in, you will know that you needed it!
The non-routability of Netbios is a red herring. You are not using it
for routing. TCP/IP does that. You are using it for name resolution, and
WINS (using Netbios over TCP/IP) lets you do that across a routed network.
"Thomas H" <(E-Mail Removed)> wrote in message
news:623BF5E7-DA82-461D-8DF3-(E-Mail Removed)...
> Wow, interesting stuff, thanks for the link! But we're not running WINS
> now
> and everything's OK. We rely 100% on DNS because we go through a few
> routers
> on different subnets (and NetBIOS can't route). So shouldn't I just go
> ahead
> and get rid of netbios all together?
>
> "Thorsten Kampe" wrote:
>
>> * Thomas H (Sun, 30 Dec 2007 12:33:02 -0800)
>> > Thanks for the reply! I think I'll mark all the boxes to disable
>> > netbios
>> > over tcp/ip then. I wouldn't want to set up WINS just to browse;
>>
>> It's not just browsing. A MVP(?) has recently posted this link[1].
>> You'd be astonished how many services use NetBIOS.
>>
>> > the less services the better!
>>
>> WINS is good for you...
>>
>>
>> Thorsten
>> [1] http://support.microsoft.com/kb/832017/en-us
>>