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
try the dns change Sceles posted above first (for it's a fast shot and won't hurt if it does not work out). if this fails to solve you problem, you will have some detective work at hand, for the reasons can be numerous (and often going hand-in-hand too).
- check if your computer clear of any maleware that uses it and your network for nefariious ends. something you should do anyway every now and then. and do the scan not from your OS but from a clean OS (by booting from a usb-stick or an optical with win PE or linux running on it and an AV-prog installed there).
- check that your net-settings in your OS and in your router/modem are correct and running without errors (you will probably have a problem doing this because the lack of knowledg about it, or you would not have posted your question in the first place - so google around for specifics on your hardware (computer and router etc.) for how to do it)
- check the quality of the connection to the warframe control-server and when connecting to a host too, by using a mix of tool your OS already have (console, commands "ping" "tracert" "netstat" etc.) and some tool for logging. microsoft also have a lot of good and free tool from their sysinternal section for download - those make it more easy for you - especially tcpview and process monitor will come in handy here. it still is a lot of testing and try&error involved until you get results you can work with.
- if you discover that neither your rig nor your uplink-device (router/modem) is the source of the problem, but your ISP, contact their support, give them hell (they deserve it usually anyway) and change your ISP if they can't or won't help you.
one more thing: avoid connecting to the net via wireless methods like 3g/4g (no, i don't mean wlan - that only for you privat network to enddevices) - especially when you are in a dense urban region. you have to share the connection point with every other dude/dudess that is around the next antenna and they tend to get overloaded with requests pretty often which can lead to heavy spikes in your latency (high-ping) or even to instability of the connection (short connection losses). both, but especially the later one can gat you those "kicked-back-to ship" issues. usually because you will get an new ip when your rig re-connecting to the endpoint (antena) and the host won't recognize you anymore (well, your ip). the game itself is better in this regard, even with a new ip, it will (most of the time) notice that you are still... you, even with a new public ip (but only if the timeframe isn't to big inbetween the connection loss and re-connecting).
so try (if possible) to play via dsl or cable.