make sure windows network is set to private not public
any vpn is disabled
check router settings, disable wifi isolation

try to ping the ip of the vr set from the host pc

for me a temporary solution was to restart router and (so far) permanent one is to disable mesh wifi in your router

I have literally the same issue on my Meta Quest 3. Did you manage to solve it? If so please share with me.

Also, look for "Guest Network" in your wifi router settings. Sometimes it's hidden deep within the menus of your wifi router. The full troubleshooting list that I've assembled is here: https://help.steampowered.com/en/faqs/view/0E2C-406B-9135-38A4 under "Troubleshooting" "If you cannot connect make sure"

Originally posted by charlesl:

Also, look for "Guest Network" in your wifi router settings. Sometimes it's hidden deep within the menus of your wifi router. The full troubleshooting list that I've assembled is here: https://help.steampowered.com/en/faqs/view/0E2C-406B-9135-38A4 under "Troubleshooting" "If you cannot connect make sure"

I found out that my Avast antivirus wanted to change my network settings and make it privite that you can only see by going it's app ://

i love you for this

To steam staff that is reading this, please remove the mesh wifi as a solution, since that post it turned out that it can lead to even more problems like the headset itself (quest) not being able to find the wifi after switching the setting on and off.

But from now 4 months of my connection working it seems as (for me) the thing was that 5ghz band had its channel setting set to automatic and after changing it (to 48 in my case which was the cleanest channel) its been working ever since.

TLDR: Mesh wifi doesnt work well in a long run, check if your wifi (either 2.4 or 5 ghz depending on which one are you using) has its channel set to auto if it does change it to whatever Wifi Analizer tells you is the least taken channel

i had the same issue, i just needed to change my wifi on the headset to the bell modem wifi which provides the ethernet connection to my pc rather than the google mesh router service.

Update, yes it seems like this is a good fix as my friend right now had this issue and changing the channel from auto to a constant one fixed it for him

what worked for me is to disable the AV
https://communityforums.atmeta.com/t5/Get-Help/Katana-17-B13V-and-oculus-2-won-t-connect-and-support-just-dont/td-p/1279456/emcs_t/S2h8ZW1haWx8bWVudGlvbl9zdWJzY3JpcHRpb258TTVDVTVUSkNSOFJLU0V8MTI3OTQ4NXxBVF9NRU5USU9OU3xoSw/page/2#M350109

I e just gone through this, moving from Mesh network to my router's own network fixed it. Hope this helps someone else.

Originally posted by _I_:

make sure windows network is set to private not public
any vpn is disabled
check router settings, disable wifi isolation

try to ping the ip of the vr set from the host pc

Thanks! The first part of this first response was all I needed. :)

please can i have some help i dont know how to get to the parts you guys are saying

on any newer router, 'guest' networks are isolated from all other devices, and will be forced to use internet relays

use your private ssid, and make sure isolation is disabled so lan and wifi devices can talk to each other and get a similar lan ip 192.168.same.different