Networks

Ask something
Discussion Locked

Network Neighborhood loses computers

0 helpful
13 replies

by etgreene

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running a network of 7 computers and a print server. Quite frequently the computers will lose sight of each other in network neighborhood. Some computers also lose sight of the print server. All is usually good after a restart but once they have been on awhile I get access denied pop ups and then the other computer will disappear. I have tried running NETBEUI and that has not seemed to help. The main server is Win2K, there are a few XP home, and Win98. Usually the win98 one are having the trouble. They are all using the same workgroup, hence they work sometimes. A couple of the computers even have trouble connecting to the internet after a startup until I start them again. Any help would be greatly appreciated.

13 replies

by d.walker5

In a Microsoft Windows 95/98/98 Second Edition network, hardware and software-related problems can cause one or more computers to lose the ability to browse or communicate with other computers. These problems range from no network functionality at all to random error messages when transmitting data across the network.
See KB 192534.

Also, I seen this occur when the Server Screen Saver activiates. Check server power settings, be sure the sever doesn't time out.

by techrepublic

Are the machines always on?
If not, the browse master for the network might be getting switched off, and confusing the other machines when they look for what's on the network neighbourhood.

There are registry hacks to prevent things like laptopsbeing browse master for workgroups.

by tduval

And take care of 'windows can stop the device to save energy' option.

I've seen (wifi) cards with this option set to on by default...

by clearsmashdrop

When you lose a machine in the network neighborhood can you ping it from other machines? Can you go to start run \\machinename and access it that way?

by pesk, mbcs, mcse, mcitp, sts

NAT (Network Address Translation), as many other protocols in Windows, rely heavily on WinSock. I would start with a WinSock upgrade/re-install to WinSock v.2 then try other things such as previously suggested, e.g. power options, etc...

by nusferatu22

Specify the TCP-IP of all your computers on the network. It must be in the same subnets (i.e 192.168.0.91, 192.168.0.92, 192.168.0.93,...). This usually solves the problem.

This discussion is closed to new replies.