Discussion Locked

Win98 Network

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a peer to peer network running using Win98, everthing was working just find until we upgraded one of the computers with a new hard and motherboard. When we put the new computer on the network it sees 4 of the 5 computers. What would cause it not to see the 5th computer and how do we fix it? All the other computers on the network can see the new computer, it just doesn't see the one.

15 replies

by dmiles

First check to see if the NIC card is seup properly,are the protocols configured properly,sometimes the proxy server settings could block the computer from seeing one another.On the WINS Configuration tab make sure that Disable WINS resolution is selected.

by magetower

I have found that when adding in a new 95/98 system to a peer-to-peer that the new system takes awhile to pick up the other systems on the network. I run a peer-to-peer (tcpip only) at home and usually have to give any new system anywhere up to an hour to 'aquire' the other systems.

Setting up one of the systems to be the browse master for the network may speed this process up some.

In your network properties select File and Print Sharing then click properties. There you will see the settings for Browse Master.
By default this is set to Automatic but every time a system comes up on a W98 peer-to-peer it forces an election for browse master and tends to slow down building of the browse list. By Enabling one and Disabling the others the election process is eliminated and the designated master will always maintain the browse list.

by lucard

Considering you have a simple peer-to-peer network, the easiest way to solve your problem is to reinstall the network on all stations. To do that, simply remove all the protocols, then reinstall them. Also, consider reinstalling file and print sharing. Be sure that the computers are in the same workgroup.

by nettek

Browsing in Win9x when you don't have WINS or DNS to rely on can sometimes be quirky. A quick fix is as follows:

Open Network Neighborhood on the PC that can't see the one computer.

Go to Start -> Find -> Computer and locate computer that is missing.

Drag and drop the computer into Network Neighborhood. Answer "Yes" to the prompt.

The computer should remain in Network Neighborhood on reboot.

by tech

Hi, I've seen this happen when you use spaces in the computer name. Check that the missing one has a valid name.

by jesaltz

Several possibilities. Try find computer instead of network neighborhood, the neighborhood can take 1 hour to see a computer on the network. Check the missing computer, make sure file and print sharing is on. the suggestion about checking which workgroup the missing computer is on was a good one. Use one of the old computers and find out if it can see the missing computer, if not check your physical connections.

by sorites

If you are using TCP/IP, and you are sure that the config is right then you could try what I call a "Kick Start". In the "Hood" go to the address bar and Type in \\ this should force windows networking to make the connection to the computer at that IP if the setup is correct it will work. Windows will then create an association between that IP and the Netbios name of the computer.

This discussion is closed to new replies.