A computer crash that brings down a network 55

It is unlikely that a computer crash in the DCS system will cause the entire network to be paralyzed, but it should be caused by a defective design, or an error in the communication settings or communication cables. The initial inference is that it is a communication failure, please investigate whether the computer crashes or the communication failure first, whether the DCS controller and the indicator lights of each module are normal, whether the switch is normal, whether the network cable and connector are intact, rule out the cause of the switch and module, and then lock the problem on the computer, check the correct computer software settings, and then check the hardware, focusing on the network card, some DCS systems will monitor the network when designing, and execute the corresponding procedures.

In short, there is a problem that should not occur, it is best to check the settings and connections according to the design requirements, and it is not the server that crashes, so it should not cause the server network to fail. If the line is not easy to check, change to a temporary line. Unfamiliar with the device and unfamiliar with the settings are most prone to this kind of problem.

Our school uses an internal local area network, a network interface in our dormitory, a switch, and six computers access the Internet at the same time.

If there is no problem with the system, is it because you did not find a bug in the debugging of the program installed on the computer, which will cause the crash? Or is the industrial environment too hot causing a crash?

Can I do RAID, and backup each other's hard disks between different computers? Were there any redundant computers in the previous network?

I don't know the specific solution, but I think there is a serious flaw in the design, there is no redundancy or backup means.

Gently I'm coming, knock on the keyboard, and take that point away!

It should be the problem of your software, each computer network connection will occupy cache space, network management software should take a single thread execution, if a machine crashes and cannot be executed, the task can not be executed, then there is an interruption, this network should be a specific demand to make this structure, if the management software releases the unresponsive machine cache, it should be able to continue to execute, or software development multiple threads should be executed at the same time. I'm also guessing that I haven't seen any of this, and the specific situation is not clear.

The best thing is to make a domain server, communicate through a switch, and there will be no problems.

1. Unplug the network cable to play stand-alone games or listen to songs and watch movies, see if there is a crash, if there is, don't look for the reason for the network, or hardware, if not, it is determined that it is the reason for the network, and then check up to avoid detours.

2. If it is the reason of the network, 80% may be a virus, some viruses will not disappear because of the reinstallation of the system, if the virus is in the D disk, as long as you click on the D disk file, the thing will be automatically copied to the C disk, the best way is to install the system, other disks are not important, use the driver and anti-virus software from other people's computers to install it on the U disk, the anti-virus software is updated and then check and kill again, it is recommended to use NOD32

Safety suits.

1.It may be that the heat dissipation performance of your computer is not very good, resulting in too high a temperature,!

2.Maybe your memory is not enough, and you have too many programs to handle!

3.Then you don't operate properly, click too often, my computer is sometimes like this, I know this very well!

I don't know what I said, and I can't tell what the problem is.