Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
This completely worked for me thank you sooo much!
I tried the TKIP versus AES thing, limiting bandwidth, disabling IPv6, but none worked.
I fixed it by trying a different brand of wifi adapter.
The RALink internal PCI card didn't work.
I found an old IOGear USB Wireless N adapter and it fixed the problem.
I get a similar disconnection issue when using torrents.
Here is the detail on how a torrent works:
Client connects to torrent server
Torrent server provides list of addresses with bits of files to download
Client connects to addresses using multiple streams
Client reaches maximum concurrent streams that router is capable of
Client disconnects
To fix this in a torrent client, you limit the number of streams until it doesn't disconnect any more.
World of tanks provide torrent tickbox so you can opt out of torrenting their files. This torrenting crashes the router every time as well so I always turn it off.
To the valve staff member who said steam uses HTTP to download, that has to be part of the problem. I might believe this but I know from using a download manager that my router can handle a maximum of 10 HTTP download streams (virgin router) to one address.
Please allow us to limit the number of concurrent HTTP/TORRENT(as you could call multiple connections) connections. This will fix the 40+ of us here who have posted about this problem. This is definitely an issue with THE STEAM CLIENT.
The TKIP and wireless speed adjustments provide limiters within their driver software that doesn't crash as easily as its not trying to utilise higher speeds with bad drivers that can't handle the wireless transfer properly. TKIP is unlikely to be a fix but good luck if it does.
Control Panel > Network and Internet > Network and Sharing Center > Change Adapter Setting > Right click your connection > Properties > Configure > Advanced > Wireless Mode tab > Value: "IEEE 802.11b/g/n" Change to "IEEE 802.11b/g > Save and exit.
According to my research, the "b/g/n" is the newest and fastest bandwidth capability and the speed that this setting runs on might be too much for older modeled modems, which explains the internet shutting down. The "b/g" setting is the more common, not the oldest but not the latest setting that is common for majority of these not state-of-the-art modems so connectivity is relatively okay with this setting.
The mini wireless adaptor I was using was overheating, causing it to shut down, that could be the problem.
I moved it to the front of my PC, and it seems to now be working.