Windows

NT Networks have a Browse Master that keeps a list of all the Machines in the Network Neighbourhood. What may be happening is that early in the morning and late at night the lists in the Network Neighbourhood are inaccurate. Its just something you have to live with. The work around is to type \\server from the run command. or \\server\share. My favourite is to make shortcuts on the desktop e.g. \\server.
The other work around you have spotted - leave the machines running!

Your information is a bit vague. Without knowing the exact error message you are getting about the Master Browser, this is difficult to diagnose.

I would suspect the IP address or the Computer/Host name (or name resolution). These must be unique on the network. It's also possible that you have a flakey NIC/NAC.

If you use WINS, make sure you don't have an old reference in the data base. If you use DHCP, make sure it isn't assigning an address that's statically assigned to another machine.

If this is a Peer to Peer network, you are probably best to just use NETBEUI (it's much simpler and less overhead). You may want to use TCP/IP for some other reason, but you should get rid of IPX/SPX unless you are connecting to NOVELL. Use the fewest protocols possible.

Have you tried changing your NIC? I have talked to fellow technicians who have had NICs act like that even though they bench test ok.

Elliott.

First Problem: NetBEUI and TCP/IP and IPX/SPX. Get rid of ll but one (recommend TCP/IP for routing / internet access). By having multiple protocols you add additional traffic and additional Browse Masters tot he net work (one Browse Master - withback-up - per protocol and per subnet).

After that clean up your LMHOSTS files and WINS data base (if you are using WINS). Also check this registry hack to "fix" browser elections - but be careful you fully understand it before hacking the registry. Look for "HKLM\System\CurrentControlSet\Browser\Parameters". Set MaintainServerList to "No" on all but the PDC. Set IsDomainMaster to false on all but the PDC. Set to Yes and True on the PDC.

If you have routers within your network, you may need to hack additional boxes (one per subnet) to allow them to be Browse Masters.

Finally: You cannot mix workgroups and domains. Recommend putting all boxes into a NT domain.

What I have found with Microsoft networks (WIN95 and WIN98 workstations) and it also applies to NT workstations i'm told, is that you need to disable the browse master on the workstation because what is happening is that the workstation is fighting with the NT server to be the master browser. Needless to say, server will always win. When you restart the workstation, it will eventually log in. Unfortunately, I can't remember how to disable the browse master in NT workstation, but i'm sure it's not difficult to find.

Good Luck,

Dave