Discussion Locked

Network Neighborhood Disappered

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Running a single NT Domain with PDC, 4 BDC's.
Approx 100 Win95 clients in one workgroup. Never had problems before, has worked for years... no changes on server side that would effect this. Can ping other systems, can do a "find" and find a computer... just can't browse net neighborhood...get "unable to browse network" error when I try to browse on client or on server. Any ideas?

9 replies

by dft3

You might want to check and see that the WINS settings are all configured properly. Not being able to browse is a NetBIOS problem.

by calves

I am sure you're familiar with the Master Browser concept, if you not, you need to introduce yourself to the principal.
It's very common on networks, where W95 machines have File & Print Sharing installed, for a Win95 machine to become a Master Browser. With 100 machines on your network, I say you have some work ahead of you. However, to identify the ones that have that option, look at network neighborhood and all the 95 machines that can be seen, have the option installed. You need to go tothose machines and in the properties of network neighborhood, highlight file & print sharing, properties, highlight master browser option and select disable, the Master Browser should be one of the DCs not client machines. If you leave on, any machine will be allowed to participate on the election for Master Browser and if a W95 wins the election, everytime that computer is rebooted or become unavailable, a new election takes place and all that will not just delay the availability of Network Neighborhood, but also

by gihan.jayasundera

On the client, check and see if the workgroup name matches the server workgroup name and check to see if File and print sharing is installed in Network Properties. This is a common problem. Hope this helps.

Gihan

by tomsal

I guess everyone assumes that people use TCP/IP all the time, however your message doesn't hint to TCP/IP so I'll take a stab in the dark that you may be running IPX. If this is the case, the solution is simple - Enable Netbios over IPX, reboot - done.

IF you are running TCP/IP instead, please let us know about your DHCP and WINS server arrangements/configurations.

On IPX networks, when people explain this problem - I have yet to see the Netbios over IPX NOT WORK... ;)

Take care.

-Tom

This discussion is closed to new replies.