ServerWatch content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.
Answer A is incorrect because a firewall or packet filtering router that
blocks outgoing broadcast packets on UDP Port 138 will have no effect on the
Browser service. Master Browsers configured as WINS clients contact the Domain Master Browser via a
directed datagram. Therefore, the blocking of broadcast messages by an
intervening router or firewall will not prevent the segment Master Browser from
communicating with the Domain Master Browser. Another important consideration is
that no other client on the missing Server’s segment is having problems
showing up on the Browse List. If there were communication problems between the
segment Master Browser and the Domain Master Browser, the problem would affect
all computers on the segment.
Answer B
is correct because when you disable NetBIOS over TCP/IP on a
Windows 2000 computer, you also disable the network clients ability to send
server announcements, which are dependent on the NetBIOS interface. A network
client that has the NetBIOS interface disabled is still able to access network
shares on a Windows 2000 network by using the Direct Access
method. In this
instance, the server has had its NetBIOS interface disabled, and therefore will
not show up in the browse list. This is the preferred mode in Windows 2000
networks that do not have NetBIOS dependent applications. This file server is
still able to provide shared network resources, but rather than having users
navigate a long browse list, you can publish the shared network resources on
this server to the Active Directory. Users can then more efficiently search the
Active Directory for the resources they require.
Answer C
is incorrect because an erroneous record on the WINS Server will
not prevent this file Server from showing up on the Browse List. Remember, a
computer name shows up on the Browse List via server broadcast announcements on
the local subnet. These announcements are in no way dependent on NetBIOS
name resolution or WINS. They are broadcast messages to the local segment, and
only the computer name is included on the browse list; the IP address of the
server making an announcement is not included. Therefore, as long as the
segment Master Browser is able to communicate with the Domain Master Browser,
the computer’s name will show up on the Browse List. However, if this computer
does have a static mapping on the WINS Server, and the IP address is incorrect,
then when a user tries to connect to the machine who’s name is on the browse list, it will not
be able to do so, because NetBIOS name resolution will fail.
Answer D
is incorrect because the NetBIOS node type will not have any
effect on the browser service. The m-node client will preferentially use NetBIOS
broadcasts for name resolution before using a WINS Server. However, this will
not have any effect on its ability to issue server announcements on the local
segment.
Answer E
is incorrect because its does not matter if the missing Server
is configured to use a WINS Server, or is even if it is configured with an incorrect IP
address for a WINS Server. The only machines that might require the use of a
WINS Server are the segment Master Browsers (and an LMHOSTS file could be used
instead if you wished). This is a very common misunderstanding that
administrators have about the Browser service. Remember, servers do NOT need to
be configured to use a WINS Server in order for the name to show up on the
Browse List. However, a WINS Server may be an issue when it comes time to
resolve the name on the list.
