Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Network 'dropout'

May 6, 2005 8:42PM PDT

Every couple of weeks my small (3 workgroups(4 computers each)) fails to communicate btwn the workgroups. Nodes within the workgroups can talk to each other, but not go outside. Just a suddenly, the entire network reappears and everything is fine.

Any thoughts, anyone?

Risto

Discussion is locked

- Collapse -
Bad switch or router?
May 6, 2005 10:13PM PDT

sounds like a hardware issue.

- Collapse -
other possibility
May 7, 2005 5:38AM PDT

sounds to me its a "classic" issues with Microsoft OS. Their so call "Master Browser" broadcast the "Master browse list" (the list of computer you see in entire network) every 12mins or so. Since you dont have a domain controller (server OS), all computer can become the "Master browser" for its own workgroups. In most cases, it will not have any problem but once in a while, the "master browse list" can get out of sync. With 12 computers on the network, its wise to have a server to centralize all resources.

- Collapse -
Any solution . . .
May 7, 2005 10:24PM PDT

ac414,

Any solution, or work-arounds, other than server? My boss is dead-set against a server based network.

- Collapse -
Network 'dropout'
May 12, 2005 10:34PM PDT

I still don't understand . . . if I get a response from pinging various computers, why can't I see these computers on 'My Network Places'?

Risto

- Collapse -
Because Network Neighborhood is not real time.
May 12, 2005 11:24PM PDT

Microsoft writes "NOTE: If a computer is removed from the network before the computer is logged off the network, it may take up to 51 minutes for that computer to be removed from the browse list."
http://support.microsoft.com/kb/q134304/

It also notes a 15 minute timespan in which new machines might appear. Another article noted a 15 hour delay in populating this display.

-> Not so funny. I know a company that based it's product offering on the functionality of the Network Neighborhood display. They lasted about a year and folded. There is no cure!

---> What does work is the command line. Open it up and type in NET VIEW. With more NET VIEW commands you can forcibly see what machines are responding.

A firewall will break this area as well.

In closing, the Network Neighbor is not "broken." It just doesn't work the way people expected it to.

Bob