Disabled NetBIOS, Now Clients Can't Browse

[David]

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

 

[Marc Reynolds [MSFT]]

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.

 

[jbogren]

I was under the same impression but---
We have multiple Vlans, some of which need to access the
same windows domain. I appear to need Netbios over TCPIP,
WINS and File and Print Sharing. F&P sharing appears to
control Ports 137/138 which is the WINS Broadcast Ports.
IF F&P sharing is off you can browse but can't be seen.

 

[David]

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

 

[Lanwench [MVP - Exchange]]

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.

 

[Shane Brasher]

Hello All,

Marc is correct. You will need Netbios over TCP. Active directory
browsing is much different than browsing via "my network places". Active
directory browsing is more along the lines of a search, browsing by "my
network places" will need WINS and/or Netbios over TCP. Because the
browser service relies on server broadcasts, its communication is
connectionless and by definition unreliable. It is possible to NOT see a
computer in the browse list and still access it's resources. Unless there
is a reason to have browsing, I would not rely on it for name resolution or
accessing resources.


Shane Brasher
MCSE (2003,2000,NT),MCSA Security, Network+, A+
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[greenbay]

I jump in..

I tried to disable netbios over tcp/ip, and I still could connect(eg
map) to two servers, but not our fileserver. Should i be possible to
map a resource on the network if I disable Netbios?
//Mike

 

[J.C. Hornbeck [MSFT]]

With Windows 2000, Windows XP and Windows Server 2003 you don't need NetBIOS
over TCP/IP to connect to shared resources. This is called Direct Hosting.
In fact, browsing and connecting have absolutely nothing to do with each
other. Whether you can browse the network or not doesn't make any
difference in whether you can map drives or connect via UNC paths.

--
J.C. Hornbeck, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.

 

[greenbay]

With Windows 2000, Windows XP and Windows Server 2003 you don't need NetBIOS
over TCP/IP to connect to shared resources. This is called Direct Hosting.
In fact, browsing and connecting have absolutely nothing to do with each
other. Whether you can browse the network or not doesn't make any
difference in whether you can map drives or connect via UNC paths.

I figured out half of my problem. My fileserver doesnt respond on port
445, thats why I cant map a folder when I've choosen to disable
netbios over tcpip.. the other half, why it doesnt respond is what im
trying to solve now...