Discussion Locked

Unable to browse Network Neighbourhood

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

I am using Win98 Se on a Novell network, although my first login is through Client for Microsoft Networks as I log into an NT4 machine. I have an Intel pro 100 NIC. Today for no apparent reason and this has happened before, I lost my TCP/IP and was unable to browse or ping any other IP machines on the network, although I could still see the Novell Servers.
On previous occasions by removing the TCP/IP in Network properties and adding them again after a reboot, this solved the problem. On this occasion it has to an extent. I can now ping other IP addresses and use all the other IP commands. I can even do a find for another computer or NT Server and then right click on it and explore it. But the problem is when I go to browse Network Neighbourhood nothing shows except the Novell file servers.
This is a strange one I know, but I am really stuck now.
Looking forward to some positive answers.
thanks.

Howell Rees.
howell.rees@lineone.net

22 replies

by kmerrillt

It doesn't sound like you are using NETBEUI by your post. You would need this protocol for network communication. You are able to ping because you are using TCP/IP protocol.

by icrovop

There is no need to load netbeui. Load netbeui would only fix you problem if you NT4 PC and others had Netbeui loaded as well. You need to check that in your network control panel settings and the indentification tab you workgroup is set to to thesame as you NT domain (if you have one) or is the same workgroup name as everyone else. If that does not work you should try getting rid of your clients and TCP/IP, rebooting and then reinstalling. Sometimes Netbios for TCP/IP fails to load properly. As to why you keep losing your network settings. I would suspect a bad network card. The card is not being found on startup which can reset your tcp/ip settings. After you reboot the network card is found again and you can input you tcp/ip settings.

by icrovop

replace sentence #2 of the post with this line.

Loading Netbeui would only fix your problem if you other PC's had Netbeui loaded as well.

I seem to have had a problem with you and your. Please susbstitute you for your where appropriate.

Sorry

by don christner

It sounds like a master browser problem to me. Each protocol that you are running can have a different master browser. Also, you should only have one master browser per protocol, per segment. The master browser is the computer that keeps track of all of the networked devices that are available.

Look in the NT machines event viewer to see if you are getting master browser election notifications. Everytime that the master browser changes, it must rebuild it's list of what is available. Because of the way the service works, it can take about 90 minutes to rebuild the list. You can still see the Novell machines because they use IPX/SPX protocol and have their own master browser.

When you rate this answer, tell me if you what more details on how to set up a master browser.

Don

by cesarcastro

Last month I got the same problem.
Besides to configure Windows Client with the Domain name, TCP/IP protocol with its propper settings, Group parameters complete .... I added the Share Hard Disk Service. I bootuped ... and functioned. Actually I did not share any folder.
Good Luck

by curacao_dejavu

hmm, the fact that it's keeping happening is bothering me.
Is this machine a laptop ?
anyway,
for now it seems like the binding settings are messed up (check the properties of tcp/ip, bindings).
Are you having the latest driver for the nic ?
check also if the browser setting i set to automatic ( it's somewhere in the tcp/ip setting, I can not remember exactly where.)
when you see the novell servers are you able to connect to them as well.

hoping for the best.

regards, Leopold

by biju thomas

Hello
Just try changing your Network Identification name and reboot. Logically it will not make any difference but practically it will help.

Thanks

by kep 001

Try off / on cycling the LAN equipment (hub, router, "modem"). This helps our small system sometimes.

Kep

by robfla

Just from what you've written here, I would suggest looking at the TCP/IP properties. Make sure "Set this protocol as the default" is checked and reboot. That should move tcp/ip to the top of your binding order. It sounds like your pc is defaulting to ipx/spx to browse the network. Could you post a little more info about your tcp/ip setup? Can you ping by name or just IP? It sounds like WINS is fine, as well as your gateway and mask. This leads me to believe the problem is in the bindingorder.

This discussion is closed to new replies.