Does your AWS instance loses network connectivity or scheduled tasks don’t run when expected? We can help you fix your AWS issues.
Here at Bobcares, we have seen several such AWS-related errors as part of our Server Management Services for web hosts, AWS users, and online service providers.
Today we’ll take a look at the causes for this error and see how to fix it.
Why does Instance loses network connectivity
Before we get into the solution part of this problem, let’s first see why this error occurs.
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 fix
Now let’s see what suggestions our Support Engineers provide to our customers to resolve this error.
- 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.
- Make sure that you are running the recommended PV drivers.
- Verify that the below registry key exists and is set to 1:
[Need any further assistance in fixing AWS errors? – We are here to help you.]
In short, AWS Instance loses network connectivity if the instance has the wrong time set. Today, we saw how our Support Engineers fix this error.