Discussion Locked

NetBIOS over TCP/IP?

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a bit of an issue with NetBIOS over TCP/IP.... Seems a bit belt and braces to me, and isn't NetBIOS a broadcast protocol? If you have a Master Browser (and from my experience some Server machine on the network is going to want to be...) whyuse NetBIOS?

3 replies

by deadly ernest

The different protocol are there to send us crazy, that is all they do now.

Seriously most date back to the early days when each manufacturer went their own way and each created the whell with different size setting. For reasons of backward compatibility we have the most used protocols still available.

Some people still use the older protocols for security reasons. they switch protocols between major network segments, drives the hackers crazy.

Best use I have seen is some types of traffic is sent with one protocol and other types with a different one. Thus you restrict what can go where by what protocols you set up. tricky and finicky but some people think it worthwhile.

by tbragsda

Explaning NetBIOS can take a year. Just to start, its not a protocol. It defines a software interface and a naming convention, realy a API. "Extended BIOS". Forget the history. NetBIOS is, like TCP/IP a group of "stuff" that are protocols. SMBand CIFS are importan bits of it.

The big thing to discuss is, you need some sort of name resolution to get somwehere on a network. If you have older MS OSs, or OS2, or.... you need NetBIOS. If you have multi segment LAN, you need to route thatover IP to get somewhere. Hence NetBIOS over IP, or IPX or anyother routable protocol.

MS 2k now uses DNS, so if you take all 9x, NT workstations and servers off the network, you can be done with NetBIOS almost.

This discussion is closed to new replies.