Windows Forum

Ask something
Discussion Locked

Network Browser failure under W98/MS Net

0 helpful
15 replies

by basil.cinnamon 1 view

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

OOPS-mistakenly closed thread, reposting:
Can't browse nw on a PC on W98 peer to peer nw, MS Networks with NetBEUI and TCP/IP only.

Symptoms:

-troubled computer does not see itself in Nw Neighborhood [sometimes can't see self, but others CAN see it; sometimes CAN see self but others cannot see it; sometimes neither;

-can often see myself with Find Computer but only under Workgroupname, not under Nw Neighborhood;
-Other computers sometimes can see me and access my resources
- Find Computer on another PC finds troubled PC but under Workgroupname, not under Network Neighborhood; cannot see shared resources;
-can ping the IP of the troubled computer; other computer from the troubled computer
-DOS NET command used for diagnostics,no errors, so all the low-level connectivity is OK (NICs, cables, hubs, etc.) and all other properties are OK
--No other problems with the PC;

Tried & failed:
-removed/ reinstalled NIC, nwadapters, protocols, properties in Network;
-waited 24hrs for nw to recogniz

15 replies

by trentcook

you said removed/reinstalled NIC...Is that the same NIC that was in it, or did you actually try another NIC all to gether?

Put a new NIC, or one of the ones from another PC in it and try it out....

Im guessing that is your prob, as I had same prob on my LAN.

Are you by any chance using a realtek NIC....Very troublesome with odd errors that seem to make no sense at all.

HTH

Trent Cook
Sys Admin
MCSE, MCP+I, CNA, A+

by csheltcomp

When you are doing peer to peer, the best protocol to use is netbios. Disable the netbeui and load netbios.

by eap

You seem to be having a problem with name resolution. This can often be a problem in peer-to-peer networks as there is no Domain controller that is specified to always be the master browser. You may try creating a hosts file.

In the root of the Windows directory on any of the PC's in your LAN, create a new text file and call it "hosts". Do not put an extension on this file.

In this file, you will have a line for each computer in your LAN. Each line will first have the IP address of a given machine, then its name seperated by one tab space. Example:

192.168.0.1 WKSTN1
192.168.0.2 WKSTN2

etc. There should already be a sample hosts file in the root of your Windows directory called hosts.sam which you can refer to for moreinfo. Open it in any text editor and have a look.

Copy the hosts file you create to the root of the Windows directory of each PC in your LAN. Now your Workstations will be able to refer to this file for name resolution rather than having to browse for it.

Good luc

by mcse lee

I agree with #3 - you need to configure a HOSTS and/or LMHOSTS file on each workstation. I would eliminate NetBEUI and run TCP/IP only - you'll have better success.

by rlmiller

Try checking your network cables and make sure that they are in good physical repair. Also, try to switch out the cables and give it another try. You could also try using a different NIC and/or hub/switch. That could make a huge difference.

by dejan

What NIC u use ? Check drivers, W98 have most bad drivers. if u use any RTL 8029 (without AS, 8029AS work correct) chip based NIC and W98 generic driver, for example, it's will problem. (sory fro bad english)

This discussion is closed to new replies.