Hi MOHD,
This issue may be caused by several conditions.
First, it is recommended that check if the server has reached the maximum access number. We may add the access number to see if the issue will disappear.
Second, we may check the resource monitor in the server, see the value of highest active time. If the value is high, this issue will happen.
Third, we may check if the network exist ARP spoofing. ARP spoofing would be easy to detect if you happen to know the MAC address of the default gateway. We may use arp a at a command prompt to make sure you had the right Mac address of the default gateway.
If you dont know the Mac address, we may use network monitor to catch packetsStart a network capture;
Clear the ARP cache of any entries for the default gateway ("arp -d 192.168.0.1");
Initiate a connection to something on the other side of the default gateway ("ping microsoft.com");
Stop the capture and look to see if you got more than one ARP response when you ARP had for the default gateway.
More information about detecting ARP spoofing attacks:
http://blogs.technet.com/b/neilcar/archive/2007/07/05/detecting-arp-spoofing-attacks.aspx
Forth, we may use network monitor to check if the network exist network loop.
If you want to download the network monitor, you may click the link:
Network monitor download link:
https://www.microsoft.com/en-us/download/details.aspx?id=4865
Best regards,
Anne He