安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
When you run into this issue next, can you go under the wireless settings in the Quest, and get the IP address from the specific network you are connected to. It is a local IP, not a public IP (so it should be 10.xxx.xxx.xxx, 192.xxx.xxx.xxx or 172.xxx.xxx.xxx)
Then, try pinging it from your host PC by opening a command-prompt and typing
ping [that IP address]
And see if your host PC can ping your headset.
If troubleshooting requires us going out of the public, we may ask to open a support ticket if you are willing.
I checked the IP, and even though I was definitely on the same subnet and everything, it did not work. But getting a new IP did fix this for me.
I don't know if I was still running the beta (I was on version 2.0.5 iirc), and it's hard to see if you're on the beta at all after signing up for it.
But I'd rather assume that this is the way the router does NAT. Depending on your router's software, you may have one or more ways you can change this. Or there may not be an option to do so.
This mac hiding feature can also make a difference.
These simple home routers are now trying very hard to figure out what you want to do, and they're relying more on that than on what settings they have. Therefore, the order in which you turn on is of utmost importance.
If you don't turn off your router, you can try to run the quest before you start the router, and then not turn it off again.
Maybe some savvy guy could help you set up your router.
You can ask if he knows how to set NAT, most friends who will say they can set up a router, they won't know how to configure NAT. :P
edit:
Or maybe you have two routers, and one is connected to the other, then their starting order can make a difference.
1: A temporary solution is to restart your router and for some time (no clue how long, maybe a day and change) you'll be able to connect and play fine
2: This one seems to work so far for me (a week without problems) and is to disable Mesh Wifi setting in your router (for me its under "Local Network/ WLan/ Mesh Wi-Fi")
Remember disabling this like a year or 2 ago when I had problems with connecting to oculus link, back then I turned it off but it seems like it turned itself on again for whatever reason, after disabling it the steam link works fine
Modern routers often have the ability to change the configuration remotely, which ISPs sometimes like to use.
1: For example, your router may be set to restart at midnight every day.
edit:
It can also be a renewal of the DHCP lease by a computer or phone (Quest 2 is a "phone").
posted this fix on some other thread with this issue but changing the wifi Channel to a specific one seems to fix this as I and right now my friend got the headsets (both quest 2) to connect after changing this setting.
The mesh wifi setting (if turned on and off constatly) few times lead to my headset not even being able to find wifi so I would not recommend this as a fix anymore
Worked for me