There used to be a lot of talk a few years ago about getting rid of Netbios.
There is not much talk about it anymore because everybody found out that you
can almost never get rid of it. There are too many things that depend on
it,...it isn't just about Windows,...it is also about all the millions of
Applications that have been written that still in some form or another need
it.
We are a TV Station and our whole news room system that controls a huge
amount of what goes on the air during the news still needs it.
About any application that accesses network resources using a "single name"
to the target machine probably still needs it.
Network Browsing, Network Places, Network Neighborhood (whatever you want to
call it) still needs it.
My advice is to leave it alone. It ain't broke,..don't fix it.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"Mike55" <(E-Mail Removed)> wrote in message
news

5D50E94-BF38-4603-A9D6-(E-Mail Removed)...
> I'd like to disable NetBIOS, but I'm not sure how to completely disable it
> or
> even if it should be disabled. I have two 2003 DCs and one 2000 DC
> (legacy
> going away soon) with win2k and xp clients. I can disable NetBIOS over
> TCP/IP for each client network adapter without any problems, but when I
> tried
> stopping the TCP/IP NetBIOS Helper service, I could no longer logon to the
> client (I use roaming profiles).
>
> What's the difference between disabling NetBIOS over TCP/IP for the
> network
> adapter and the TCP/IP NetBIOS helper service?
>
> Should the service ever be disabled on clients and/or servers?
>
> If the client adapter is disabled but the service is left enabled, is
> NetBIOS really off?
>
> Thanks,
> Mike