I'm not entirely sure, but it could be a result of the local browser election picking one of the Win98 machines to be the SMB local master browser on your network. The LMB is responsible for mapping Windows share names to machines and facilitates communication between machines. When a Windows machine starts up, for instance, it broadcasts to the network, "I am the local master browser!" Then the computer that THOUGHT it was the current local master browser will challenge the new announcement. They compare some strings set by Microsoft to determine who "wins" and the computer that wins the election will take over those responsibilities.
Generally, the progression of browsers goes like this:
Win95 -> Win98 -> WinME -> WinNT Workstation 3.5 -> WinNT Workstation 4.0 -> Win2k Pro -> WinXP -> WinNT Server -> Win2k Server
With the machines on the left always yielding to the machines on the right.
So, obviously WinNT Server and Win2k Server are designed to take over Master Browser responsibilities. If you don't happen to have a copy of those, however, you can also configure Samba (for Linux or *BSD) to take over as a Master Browser, and do it for free.
There's a free O'Reilly book on Samba that you can download. It sheds light on the dark, secret mysteries of the SMB networking protocols.
Andrew Tridgell, the author of Samba, has stated many times that every time Microsoft releases a new version of Windows, they have to be completely backwards compatible with old version of Windows SMB. Therefore, the SMB protocol is now one gigantic HACK. He has stated that there is TONS of overhead because of all of the bugs and problems with each Windows' implementation of SMB... The newer versions of Windows must maintain compability with all of the quirks of previous editions... And so SMB networking keeps getting slower and slower and more and more bloated with age.