Windows

for a well explained answer go to the following site:

http://support.microsoft.com/support/kb/articles/q119/4/93.asp

the expanation is too long to answer in the allotted space.

Netbios over TCP/IP is called Netbt. You should have seens this protocol on your log files or event viewer. Netbt is use for downward compatibility because under win2k, you can work with only TCP/IP. But the problem is when using win9x/ME/NT/Novell or others that use netbios such as for resolving netbios names, Netbt is used. This allows netbios protocols to travel through tcp/ip protocols.

Hope this helps.

NetBIOS is used along with TCP/IP (i.e over TCP/IP in the protocol stack, NetBios is an Application Layer Protocol) to provide Name Resolution services for Microsoft Windows Networking. All Microsoft Networking clinets/server (apart from Win2K) require NetBIOS in order to generate a session to another Windows Networking product.

Because NetBIOS does not have a Network Layer component in the OSI model it is not routable, which is why we need things like WINS to provide enterprise wide NetBIOS name resolution.

Windows 2000 does not require NetBIOS for name resolution or to generate a session to another Windows 2000 Machine. However to generate a session between Windows 2000 and NT 4 you still require NETBT in order to generate a session. On a pure Windows 2000 domain you can turn off NETBT - which is a Vendor option class within DHCP.

This question was closed by the author