Originally posted by: Shawn
Originally posted by: spidey07
And to Klin's point it is still the recommended protocol for LAN file/print sharing.
this is for on a single broadcast domain...once you get out of the SOHO environment/5 computers the ballgame changes drastically.
yeah, but then does it have to be installed on all computers?
Yes it does.
MS browsing works on a "who has a list of services for the network" mentality. That was all fine and dandy when networks were only a few hundred nodes.
Sequence goes like this...
client - who is my master browser (broadcast)
master browser - I am, here is a list of services
client - great, thanks Mr. Master Browser, I shall remember you and ask you again
works very well for extremely small networks.
The problem is when you have clients that decide they want to be master browsers. Happens all the time. You have master browsers for NBT (netbios over TCP) that don't accept (more appropriate don't listen to) requests from clients running netbios/netbeui.
If I had a white board I could explain it much better.
Needless to say, there is a disconnect between layer2/3 broadcasts and the OS itself. It is inherently unreliable and the only true way around it is getting name/subnetmasterbrowser stuff under control is through the use of WINS (windows internet naming service)
Sure, MS tells you that that approach is going away...but if you look at the traces (packet traces) you see that it isn't and they are still using LANmanager techniques.