• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

TCP/IP over Netbios?

You've given me a minor headache from that statement 😀
I'll assume you mean though whats the difference between netbios over netbeui and netbios over tcp/ip.

If you run netbios over tcp/ip its routable over the internet so others could get to your shares. That could be good or bad.

If you run netbios over netbeui, it isn't routable so your shares shouldn't be accessable. Once again a good or bad thing depending on your intentions.

Some people take speed of the protocols into consideration too when picking one, but the above is the most important thing, at least to me.
 
over tcp/ip its routable over the internet so others could get to your shares
Click to expand...
Correct me if I'm wrong, but I was able to access remote sharing even without ever installing the NetBios Over TCP/IP
I'd ask my Cisco Instructor about the purporse of having NetBios over TCP/IP.
Frankly, no one know that actual fact, I only receive alot of opinions

If one can access remote share w/o installing NetBios over TCP/IP,
what was its original intention/ purpose?

 
Frankly, no one know that actual fact, I only receive alot of opinions
Click to expand...

You have Microsoft and their great detail in documenting all of their technologies.

If one can access remote share w/o installing NetBios over TCP/IP,
what was its original intention/ purpose?
Click to expand...

NetBIOS is a layer above the protocol, there is already NetBIOS over IPX/SPX, NetBIOS over Netbeui and probably other protocols I'm not aware of. Having NetBIOS run over TCP/IP makes it routable, for one thing, which was necessary as networks grew in size.
 
Netbios is a very old IBM protocol.

There is no layer3 info so therefore it is not routable.

MS decided to use netbios for windows networking (shares, all communications, etc) in something they called netbeui.
They then used netbios in a TCP/IP header for what is called NBT or netbios over TCP. This was the preferred means of communicating during the winnt 3.51/win9x era. Basically NBT consists of a SMB layer, a netbios layer, a tcp layer, and IP layer. Lots of overhead and still relied somewhat on broadcast technology to an extent.

Along comes 2000 and the dependance on NBT is almost gone. You can do just about anything with winnt 5.0 and above versions of windows (win2k, xp) without NBT. That is why you don't need it for shares.

Hope this helps - the one and only way you would use TCP/IP over netbios would be with some of the early internet gateways that would use netbios to communicate with clients but used IP on the gateway itself to talk to the internet. Kind of a really funky proxy.
 
spidey07, that's great info. I was wondering how does network browsing and file sharing work on an all Windows 2000/XP network if "NetBIOS over TCP/IP" is disabled? Does the network have to have a DNS server running to make it work? Does that mean small workgroups without a server(for the the DNS server) must use NetBIOS over TCP/IP?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top