Re: Disabled NetBIOS, Now Clients Can't Browse

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 03/16/04 

Date: Tue, 16 Mar 2004 13:02:20 -0500

Nyet - (D)DNS doesn't let you browse; it handles name resolution. NetBIOS is
responsible for browsing, as Mark said.

Up to you if you want people to be able to browse or not.

David wrote:
> Thanks for the info, Marc. But why have I read so often that DDNS
> "replaces" NetBIOS? And maybe users not browsing the network isn't
> such a bad thing... David
>
> "Marc Reynolds [MSFT]" <marcrey@online.microsoft.com> wrote in message
> news:e%23DJQN2CEHA.3748@TK2MSFTNGP11.phx.gbl...
>> If you want the clients to be able to browse you will need to enable
>> NetBIOS on them. Browsing is completely based on NetBIOS and will
>> not function without it.
>>
>> --
>>
>> Thanks,
>> Marc Reynolds
>> Microsoft Technical Support
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "David" <deaton@nospamever.dsnonline.org> wrote in message
>> news:XTD5c.77876$LD5.70115@twister.rdc-kc.rr.com...
>>> Since we run a native-mode Windows 2000 Server DC with
>>> DNS-integrated Active Directory and all clients run 2000 and XP
>>> Pro, I followed the advice I've read to disable NetBIOS and LMHOSTS
>>> on the clients. The two I disabled now can't see any computers in
>>> My Network Places. Clicking the network icon produces and error:
>>> <Domain> is not accessible.
>>> The list of servers for this workgroup is not currently available.
>>> But they aren't part of a workgroup; they're domain computers.
>>> Typing a path to a share on another computer on the network works
>>> fine. I didn't disable NetBIOS on the DC yet. What should I do next?
>>> Thanks very much,
>>> David

Relevant Pages