|
Home > Archive > 70-210 > March 2003 > NetBIOS
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| What is NetBIOS? API, Protocol or...
Thank you
Neka M.Asadi | |
| anaconda 2003-03-16, 10:41 am |
| quote:
Originally posted by asadi
What is NetBIOS? API, Protocol or...
Thank you
Neka M.Asadi
a simple search webopedia.com
http://www.webopedia.com/TERM/N/NetBIOS.html
would have answer this question for you if you don't know about that then enter it in google.
general advice: do your own digging, only
post when truly stumped otherwise it reinforce a negative stereotype about women being need help for every little thing. | |
|
|
| jimboit 2003-03-17, 7:05 pm |
| While it is good to develop your own way to research information, don't be afraid to ask questions. Everyone has to start somewhere and some things are harder for you than they will be for me. I hope you will feel you can ask a question without criticism.
Now - NetBIOS was originally NOT a protocol, but an application programming interface. It's grown beyond that, but still is fundamentally an API.
If you are in a Windows 2000 or newer environment, technically you can get away without it, assuming other services such as DNS are available. If you have just one Windows98/NT or older machine, you must have it.
NetBIOS is unaware of networks, it just knows names. So to route it across network boundaries, you have to encapsulate it in TCP/IP or other routable protocol.
It's also considered a "chatty" protocol.
By the way - in the real world, it occasionally corrupts if there are too many WINS servers or too many NB hosts in the domain.
A good book on this is "Guide to TCP/IP" by Chappell and Tittel. |
|
|
|
|
