NetBIOS Question

win2k8

4. Which of the following is true about NetBIOS?

1.

It is required on Windows Server 2003 networks.
2.

It is required for local area network (LAN) browsing through My Network Places.
3.

It is native to the TCP/IP stack.



I thought the answer would be 2 and 3. But the MCSA/MCSE Self-training 70-291 book said its 1 only? Can somebody please clarify?


Thanks in advance,

win2k4

dynamik

Have you checked the errata: http://support.microsoft.com/kb/917983/en-us

I agree with your answer. Or did you misread the question? Maybe it asked what is NOT true...

win2k8

Dynamik,

thanks for your reply, your right its probably an errata. They must have forgot to put the word "NOT" in the actual book, because its missing hehehehehe.


Thanks,


win2k4

win2k8

I check that link http://support.microsoft.com/kb/917983/en-us
and its not even listed on there, maybe my eyes are playing tricks, or maybe theirs a difference in the ebook version, because i'm reading it online using Safari account which i get for free from my college, its sweeeeet!

win2k4

win2k8

Its kind of messed up how theirs mistakes on there like DCHP instead of DHCP or referencing wrong figures... They should do a better job reviewing things before just mass printing them its only common sense.


win2k4

dynamik

Such is the way of IT training materials. Oh well, be an optimist and realize that you have probably gained a better understanding of whatever topic by having researched it, even though you were right in the first place.

Oh, and +1 for Safari. I like to read out of a physical book when I can because I spend so much time in front of a screen already, but it is a phenomenal resource.

cnfuzzd

netbios is not native to the tcp/ip stack, is it?

netbios is required for forest-level stuff, like creating trusts etc.

yeah, this question is all kinds of messed up...


john

dynamik

cnfuzzd wrote:

netbios is not native to the tcp/ip stack, is it?

Yes (at least in Windows), that's what allows you to do things like browse for computers through network neighborhood. At least, I consider that to be part of the stack. Maybe it is technically considered to be separate, but enabled by default.

Edit: That must be the case: http://msdn.microsoft.com/en-us/library/ms819770.aspx

Edit 2: Actually, it looks like they go into it in the application-layer section: http://msdn.microsoft.com/en-us/library/aa505920.aspx

cnfuzzd wrote:

netbios is required for forest-level stuff, like creating trusts etc.

No, that's DNS. You can disable NetBIOS if you don't need people to do things like browse for computers and/or have any legacy applications that depend on it.

cnfuzzd

Yes (at least in Windows), that's what allows you to do things like browse for computers through network neighborhood. At least, I consider that to be part of the stack. Maybe it is technically considered to be separate, but enabled by default.

I thought that netbios was a seperate service that ibm or msoft developed, and then when TCP/IP went huge they developed NetBT, which encapsulates netbios packets in tcp or udp format. From wiki:

The NetBIOS API allows applications on separate computers to communicate over a local area network. In modern networks, it normally runs over TCP/IP (NetBIOS over TCP/IP, or NBT), giving each computer in the network both a NetBIOS name and an IP address corresponding to a (possibly different) host name. Older operating systems ran NetBIOS over IPX/SPX or IEEE 802.2 (NBF). NetBIOS provides services related to the session layer of the OSI model.

This may be arguing semantics though.

No, that's DNS. You can disable NetBIOS if you don't need people to do things like browse for computers and/or have any legacy applications that depend on it.

hmm, i am frantically googling, but i think that netbios is actually required for creating forest trusts. DNS is big also, but let me see here....


http://www.windowsdevcenter.com/pub/a/windows/2004/05/11/netbios.html

Amazingly, NetBIOS is actually still used in the trust creation process -- even though Microsoft has officially "deprecated" NetBIOS in versions of Windows from 2000 on.

Here's a simple illustration. Install Windows Server 2003 on two machines as standalone servers. Use dcpromo (or Manage Your Server) to install Active Directory on one of them, using test.local as the DNS name of the forest root domain. As you walk through this process, dcpromo will automatically suggest TEST as the NetBIOS name for the new domain, and accept this default.

Then promote the second machine and try to create a second forest whose root domain is named test.com. Notice when you do this the wizard automatically suggests TEST0 as the NetBIOS name for the second domain so there won't be any NetBIOS name conflict with the first domain -- even though the two domains are in different forests. Once you're done you can use Active Directory Domains and Trusts in either forest to create a two-way transitive forest trust between the two forests as desired.

Now try it again, but this time after installing Windows Server 2003 on your machines disable NetBIOS on them as follows: open Local Area Connection, double-click on Internet Protocol (TCP/IP), click Advanced, go to the WINS tab, and select the Disable NetBIOS over TCP/IP option (you don't have to reboot for the change to take effect). Now continue as before, creating the forest root domain test.local for the first forest.

But now when you try to create the forest root domain test.com for the second forest, the second machine can't use NetBIOS to detect that another domain is already using TEST for its NetBIOS name and so you end up with two forests, test.local and test.com, both of which have forest root domains whose NetBIOS name is TEST.

Before you try to get the two domains to trust each other, you have to allow them to somehow resolve each other's names. Since NetBIOS is disabled, you must use DNS to do this. The simplest way is to configure conditional forwarding on the test.local domain controller so it forwards all name resolution requests to the test.com domain controller, and vice versa (both machines are also DNS servers since they are the first domain controllers in their respective forests).

Once you've done this extra step, go ahead and try establishing a forest trust (or even an external trust) between the two domains. You can't -- the process fails with an error message even though it walks you through all the steps of the wizard and the domains resolve each other. And enabling NetBIOS at this point on the machines doesn't help either; the problem is the two domains have identical NetBIOS names. So you're stuck and will have to reinstall one of the domains from scratch, for even the domain rename tool (rendom.exe) won't let you rename the forest root domain.

hmmm, not quite what i thought it was. This makes me want to lab this up and watch things break.


John