It happens that when you try to establish an Internet connection or access to a specific resource on the Web instead of connecting, the browser writes: "The timeout period for the request has been exceeded." Not every user knows what this problem is, therefore it is worth considering this error in more detail. You can fix it, but for this you will have to adopt the schemes given below.
Request timed out: nature of the problem
The error itself and its consequences look in the simplest case in a known manner. You are trying to access some resource or connecting to the World Wide Web, a computer device sends a request to the outside world, but does not receive a response.
Why? Yes, just because the Network or communication device cannot initialize the external IP of your computer. So it turns out that there is simply no exchange of packets. The waiting interval for the request has been exceeded, the Network does not give a response just because your device is not detected, despite the fact that in the protocol settings all parameters are set to automation (meaning receiving IP addresses, DNS and using the default gateway).
In other words, packets do not reach your device from the outside. And this is a necessary condition for communication.
Request timed out: how to fix the problem in the fastest way?
If such a problem has arisen, you can use the most common network reset function . While we are not considering more complex methods like ping checking, we are trying, so to speak, to get rid of the problem with the simplest and most affordable methods.
We launch the command console as administrator (cmd in the "Run" menu or manually run the file in the System32 directory via the right-click menu), after which we enter the configuration reset commands.
The sequence looks like this: first, ipconfig / flushdns, then nbtstat –R and nbtstat –RR, then netsh int reset all and netsh int ip reset, and finally netsh winsock reset. Their application clears (resets) the system settings, after which it will be possible to reboot and try to access the desired resource or establish a network connection.
Command line and ping
But this method is the simplest and, depending on the root cause (which, by the way, no one can specify exactly yet), does not always help. After all, a message may again appear that the waiting interval for the request has been exceeded. What to do in such a situation?
You will have to use special pinging commands that accurately determine if there is a response to an outgoing external request from your computer terminal.
For example, if you use a router and a wireless WiFi network, you need to specify a ping procedure on the command line with the internal address of the computer (usually it is ping 127.0.0.1). After that, the exchange of packets should begin. The screen will show that so much has been sent, so many have been received.
But the trouble is: ping seems to be working, but there is no connection. Why? Yes, only because packets were sent to the internal address, and the loopback function worked. For a more accurate check, you should check another random address. And here there will be exact statistics on sending, receiving and packet loss.
Configuration check
Another generally accepted technique for fixing the problem that the wait interval for a request is exceeded is to use the IP configuration configuration commands. The fact is that the previous method is still more informative, rather than instrumental. And this is even provided that the ping command is used. "Exceeded the waiting interval for the request" - far from the worst message from what the system can produce.
To configure, and with the correct verification of options, you must use the ipconfig command entered in the console. It is with its help that you can find out all the parameters set in the system. If you need to know the parameters and settings of all users registered in the system, a special suffix (ipconfig / all) is added to the main command through the right slash.
After that, it makes sense to ping the address of your own router (either 192.168 with the end of 0.1 through the point, or 1.1). If it is not determined, the problem is precisely in it. If everything is fine, move on.
Trace
In some cases, one of the options for checking and correcting the problem that the waiting interval for the request is exceeded (Trove, for example, when accessing online games), it makes sense to check the trace. It represents the transfer of packets from your computer terminal to the outside world. To do this, you can use the tracert command with the addition of suffixes (for example, in the simplest case, the trace is checked using the combination tracert it.sander.su).
The command itself allows you to determine the source of the failure or the stage of the passage of packets at which it occurs. Typically, the TTL trace metric looks like a positive integer. However, a router can reduce it by one unit. If this indicator is set to zero during packet exchange, the trace ends. You will have to use the route print command to view the routing table, but this is a separate topic.
For cases when a message appears stating that the waiting interval for the Trove request has been exceeded, specific remedies can be applied in the form of the Glyph utility launched as administrator. If it does not help, you can use any optimizer program like CCleaner, which can clean and defragment the Windows registry. As a rule, an error of this type is almost always associated precisely with the presence in the registry of erroneous or outdated entries and keys. It’s better not to get into the registry yourself, otherwise the whole operating system can be brought to a state of complete inoperability. And even tracing will not help here. Request timed out - what should I do now?
Ethernet interface setup
If the above options do not give a positive effect, and the message that the waiting interval for the request has been exceeded appears again and again, you will have to tune the network connections, but not in the standard way of changing the configuration of the network itself or the adapter used, but using the command strings. Note that the command line almost always helps to solve most problems on the computer, if you know which commands to enter for specific purposes.
First, we look at the list of settings, which is called by the netstat command, to which you can add the suffix “-n”, “-na” or “-nb” to display data not in the form of a digital code.
Now you need to enter the line for viewing your own address, and then use the combination presented above (as a rule, this works on all systems).
Turn on nodes
In principle, there is one more recommendation that the system issues a notification that the waiting interval for the request has been exceeded. How to fix the situation in the worst case?
Try to call the settings of the same Internet Explorer or any other browser used. Here you need to delve into the parameters of resources that are trustworthy. Their addresses must be entered in a special list.
If this procedure does not work, the message will appear again (“Request timed out”). What to do? Just add the sites you cannot enter into the antivirus exclusion list, and create a new rule for the system firewall with the full path to the executable file of the browser program.
Conclusion
That's all, in fact, with regard to the failure, when there is a situation related to the fact that the waiting interval for the request is exceeded when trying to access some Internet resource or making a communication session. The easiest solution, except for reinstalling the system, will be a normal reset. But this may not be the case, so you have to delve into the parameters of network connections. But it is recommended to perform installation of parameters from the command line, and not by standard methods provided in the system. This option is much more preferable only because the command line uses tools hidden from the user's eyes that are not available in the normal mode when they are accessed by standard means.