Is your AWS instance losing network connectivity or scheduled tasks don't run when expected?
This guide will help you.
Sometimes AWS users experience loses in network connectivity while running an AWS instance.
Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to resolve AWS related errors.
What triggers Instance loses network connectivity in AWS ?
Sometimes, when we restart the instance, it loses its network connectivity. This can happen if the instance has the wrong time set.
By default, Windows instances use Coordinated Universal Time (UTC).
So, if we set a different time for the instance then it conflicts with the Windows time. As a result, the instance temporarily loses its IP address when we restart it.
However, the instance regains network connectivity eventually, but this can take several hours. The amount of time that it takes for the instance to regain network connectivity depends on the difference between UTC and the other time zone.
Moreover, this issue can affect the scheduled tasks.
Thus, the scheduled tasks might not run at their expected time because the instance has the incorrect time.
Instance loses network connectivity – How to resolve this error ?
Follow the steps given below to resolve this error.
1. In order to use a time zone other than UTC persistently, it is necessary to set the RealTimeIsUniversal registry key.
Without this key, an instance uses UTC after restarting it.
2. Make sure that you are running the recommended PV drivers.
3. Verify that the below registry key exists and is set to 1:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUniversal[Need urgent assistance in fixing AWS errors? – We are here to help you. ]
Conclusion
This article covers method to fix AWS Instance loses network connectivity error.
Basically, AWS Instance loses network connectivity if the instance has the wrong time set.
To fix Amazon EC2 Windows instance network connectivity issue:
You can create a temporary elastic network interface, and attach the network interface to the Amazon EC2 Windows instance. Then, you can temporarily connect to the instance and fix the issue.
1. Open the Amazon EC2 console, and then choose Instances from the navigation pane.
2. Select your instance. From the Description tab, note the Subnet ID.
3. Create a new network interface in the same subnet as the instance.
Important: Be sure to select a security group that allows incoming Remote Desktop Protocol (RDP) traffic from your IP address.
4. Attach the new network interface to the instance.
Note: The network interface might take a few minutes to come online. If you connect to the instance using RDP, associate an Elastic IP address with the network interface.
5. Using the new network interface, connect to the instance using RDP.
6. Change the network connection settings in Windows to use DHCP. Or, specify the correct private IP address settings. For instructions, see Configuring a secondary private IPv4 address for your Windows instance.
7. Detach the temporary network interface.
Note: If you've associated an Elastic IP address with the network interface, and no longer need the Elastic IP address, release the Elastic IP address.
This article covers method to fix AWS Instance loses network connectivity error.
Basically, AWS Instance loses network connectivity if the instance has the wrong time set.
To fix Amazon EC2 Windows instance network connectivity issue:
You can create a temporary elastic network interface, and attach the network interface to the Amazon EC2 Windows instance. Then, you can temporarily connect to the instance and fix the issue.
1. Open the Amazon EC2 console, and then choose Instances from the navigation pane.
2. Select your instance. From the Description tab, note the Subnet ID.
3. Create a new network interface in the same subnet as the instance.
Important: Be sure to select a security group that allows incoming Remote Desktop Protocol (RDP) traffic from your IP address.
4. Attach the new network interface to the instance.
Note: The network interface might take a few minutes to come online. If you connect to the instance using RDP, associate an Elastic IP address with the network interface.
5. Using the new network interface, connect to the instance using RDP.
6. Change the network connection settings in Windows to use DHCP. Or, specify the correct private IP address settings. For instructions, see Configuring a secondary private IPv4 address for your Windows instance.
7. Detach the temporary network interface.
Note: If you've associated an Elastic IP address with the network interface, and no longer need the Elastic IP address, release the Elastic IP address.
