Master Browser Timing

The more time I spend on the Board, the more I believe that a number of recurring discovery problems may be just the unhappy side effects of the proper operation of a Master Browser in a Workgroup.

So, do I have this right?

1. All the computers in a Workgroup pass information among themselves to determine which computer will serve as the Master Browser. This election process takes very little time.

2. The Master Browser accumulates and maintains a "browse list" of all computers (and other IP devices) in the Workgroup.

3. Every device in the browse list reports back the Master Browser at 12 minute intervals.

4. If a given computer (e.g. Brutus) is switched off and does not report back for three consecutive intervals (36 minutes), Brutus is removed from the browse list.

5. The Master Browser sends the refreshed browse list to all Workgroup computers every 15 minutes.

6. Therefore, it could take up to 51 minutes for other Workgroup computers to be notified that Brutus has left the Workgroup. In the meantime, the other Workgroup computers report to their respective users that Brutus is still connected. However, their users will not be able to access Brutus and may suspect an error of some sort.

7. When Brutus is again switched on, Brutus reports to the Master Browser immediately but it can take up to 15 minutes for the Master Browser to notify the Workgroup the Brutus has rejoined.

Again, is this reasonably correct?

JackHughs

Ms has never published timing on this so we can't say if the timing is correct

The 12 and 15 minute timings I mentioned are taken from a networking textbook published in 2002. I don't know if MS has changed the timings since then.

For my purposes, the important thing is to learn the actual operations of the Master Browser in Windows 10 in order to differentiate between real networking problems and operational realities that initially present as problems.

For example, I connect a new PC to my network and it doesn't even discover itself. I once thought that was a problem. I now think it's simply an artifact of normal Master Browser operation.

JackHughs

The MS documentation is here and some timings are buried in section 3.2.6. 12 minutes is mentioned there...

https://docs.microsoft.com/en-us/ope...7-9b750303387b

for a more whimsical (but still detailed) description I found this. It's certainly a more entertaining read than the rather dry MS docs...

Implementing CIFS: Browsing

Bree said:

The MS documentation is here and some timings are buried in section 3.2.6. 12 minutes is mentioned there...

https://docs.microsoft.com/en-us/ope...7-9b750303387b

for a more whimsical (but still detailed) description I found this. It's certainly a more entertaining read than the rather dry MS docs...

Implementing CIFS: Browsing

Yes, thank you. The second reference is mostly a good read - and entertaining.

I think I'm beginning to understand some of the non-intuitive operations within a Windows Workgroup.

1. A computer joining a Workgroup does not directly discover other computers in the Workgroup - or even itself for that matter. Rather the joining computer broadcasts an "I'm here" message addressed to the Workgroup's Master Browser. When the Master Browser receives that message, it updates the "browse list." The Master Browser then broadcasts the updated browse list to all computers in the Workgroup.

2. It can take more than 15 minutes from the time the computer joined the Workgroup until the Master Browser notifies the Workgroup.

3. If you add a new computer to a Workgroup and it is not immediately recognized by the other Workgroup computers, don't automatically assume the existence of either a hardware or implementation problem. Instead, just relax and let the Master Browser do its job on its own schedule. Network troubleshooting during this time period may actually be harmful

4. If the new computer is not recognized after a half-hour or so, it's time to start troubleshooting.

The above is the super simplified description and there are other interactions among the Workgroup computers that may require additional time to resolve.

And, on the other side, it can take up to 51 minutes from the time a computer leaves the Workgroup for the Master Browser to notify the remaining Workgroup computers.

This is all a learning experience for me and I don't want to spread bad information. If I've got any of this wrong, please let me know.

JackHughs

I also think that most of these issues are related to the Master Browser and the changes Microsoft did in relation to SMB.