Home > other >  There are a lot of Time_Wait LAN client
There are a lot of Time_Wait LAN client

Time:09-30

In local area network (LAN) a computer always drops, check for a long time to reason, had no intention of using netstat na view connections within the local area network (LAN), the results there are many Time_Wait hair line, please see below:


Images of IP 192.168.40.197 is a network printer, network printer model is: HP Laser Jet Pro 400 m401n, and client 192.168.40.51 is never used this printer to print anything, and shown on the picture Time_Wait is a boot up the computer I use netstat - na to check the result, I would like to know is what reason is caused, how to solve this problem,

CodePudding user response:

This is a peculiar phenomenon of TCP, when a TCP connection is closed, take the initiative to shut down, the operating system will put the connection in timewait state, to ensure that the other party to receive all the remaining data, general Windows is 240 seconds, Linux is 60 seconds, timewait state, the connection source port has not been released, it was not until after 240 seconds (Windows) releases, short connector can produce such problems, long the linker will not produce a large number of timewait,

CodePudding user response:

Opened the corresponding service on a computer, you can check the service, will not turn off the check.

CodePudding user response:

See which software is even, should be there is something wrong with the software design, the operation not success will continue to the next tried to continue to link, happened so quickly in a short time, a large number of connections, even the port number to use full; Seems to be met before the 360 antivirus or browser performance, so as to upgrade happened, upgrade failed also continue to keep trying to upgrade,
  • Related