Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Even if the game is being hosted by you or some other players' machines, it still needs to talk to DE's server to manage stuff like your mission rewards/etc and for trades.
So maybe your internet connection isn't "fine". Or just "not good" for the few seconds your PC needs to talk to DE's servers, you'll get this error message. It can be as random as lag.
Not much you can do easily besides being patient [it should keep retrying unless the connection is really bad]. Meanwhile check to see if the game has all the necessary permissions for your firewall/etc.
anyway, lets clear Asphe's post up a bit:
"network not responding" means indeed only the connection from the host to the server couldn't be conducted in the given timeframe (also known as: timeout). the reasons for that can be everywhere though - starting from ther server being offline or being attacked, your or the hosts machine having connection problems somewhere between the own network and the control server of DE (and there are many points inbetween that can be at fault here too).
so, best start with what the first post said, and restart your router/modem - might be all that is amiss here. if that won't solve the problem, you could test the connection to the control server next by using a trace-route to it (you'll get the IP of the server with the consol command "netstat -a" or more easy by downloading microsoft/sysinternal TCPview from the technet.
the trace-route (command is "tracert" ) will show you if and where there might be a clogging between your network and the control server - keep in mind that not all the stations listed will be sending out information, and if you see a timeout in one place, but the next (or the one after) is not affected by this, it's because of the router/server/switch won't respond to incomming querries, but will still do it's job and pushing data through... or in more easier words: only if you get one timeout after another, there is something wrong. a simple "ping" command to the server will also tell that much.
furthermore, you can test if your used DNS-server is the problem here - try using a pubic DNS like the one from google. since you didn't say anything about having such a problem before, i guess you can rule out any NAT problems - except, if someone else is configurating your router and put a new NAT-setting on (strict, most likely). if that is the case, kick this person аrse for doing so without telling you about it and then set the correct port forewarding in place (or activate upnp, if your router have this option).