Below are a list of possibly reasons this could be happening:
Influx of ingress and egress traffic could overwhelm the network card -Extended CPU load could overwhelm the system -Windows updates are missing
I recommend is to create another Network Interface for your instance for the sole purpose of Remote Desktop Connections -- use the other Network Interface for normal web traffic, this may help reduce the load. 1. Create an Elastic IP 2. Create a Network Interface (for RDP) with the same Subnet ID and VPC ID of your instance 3. Associate the Elastic IP with your new Network Interface 4. Assign the new Network Interface to your instance 5. Reboot 6. Use the Elastic IP for RDP connections only (Make sure security groups are correct)
Influx of ingress and egress traffic could overwhelm the network card -Extended CPU load could overwhelm the system -Windows updates are missing
I recommend is to create another Network Interface for your instance for the sole purpose of Remote Desktop Connections -- use the other Network Interface for normal web traffic, this may help reduce the load. 1. Create an Elastic IP 2. Create a Network Interface (for RDP) with the same Subnet ID and VPC ID of your instance 3. Associate the Elastic IP with your new Network Interface 4. Assign the new Network Interface to your instance 5. Reboot 6. Use the Elastic IP for RDP connections only (Make sure security groups are correct)
Comments