>>>>Actually, if there is a PDC, it will always be the browse master. In 95 the browse master selection is in the file and print sharing section. I agree that should be disabled. It could also be a flaky: card, cable, hub or even damaged dll on the workstation causing the problem.
>>>
>>>What's a PDC? Another TLA?
>>>
>>>Cabling and other is surely not the matter, we reproduced the behavior in our office. The cables are brand new and have been thoroughly measured and tested; besides, there's the 15 year guarantee we give on them (to ourselves, too), and, anyway, any other communication in the network works excellent.
>>
>>
>>NT Talk - Primary Domain Controller. I thought you might have been operating in a domain as opposed to a workgroup. If you're not, PDCs and BDCs (backup) don't matter.
>
>Oh, that. We've just installed our first NT Server, but at the time we noticed this, it wasn't operational yet. Anyway, no NT in the first case, so this will be the browse master issue.

Actually, running in a domain, or a workgroup with NT Server installed as a standalone server, will resolve the problem as long as the NT Server system is not disallowed as a Master Browser. The only misconfiguration in a domain that would permit this to happen would be if all NT Server systems in the domain were set up not to act as Master Browser, and at least one Win95 box was set up with Browse Master set to Enabled in File and Printer Sharing for Microsoft Networks, a rare (and immensely silly) misconfiguration (that I've seen a couple of times in the past, indicating that there are a whole lot of very silly people setting up NT-based networks <g>). When an MS network is negotiating which system will act as Master Browser, it'll select NT Server systems in preference to anything else.