I work IT at a small college and we use a couple meta quest 2s for a class. They reported issues with connecting to WiFi. The network uses WPA2-Enterprise (needs a username and domain entered along with the password). This used to work fine, but they claim a recent update took away the domain field when "use system certificates" is selected. To be clear, I checked and nothing changes when moving from "select certificate..." to "use system certificates", so, at least in our environment, it's a real issue. Is this a known issue, or is it something we are doing wrong? Also, what needs to be done to fix this?
Hey there! We see you're trying to get your headsets connected to your school wifi. We know being connected to the Internet helps maximize the use of these headsets, so we're happy to help get to the bottom of this. First, for a Meta Quest headset to connect properly to Meta servers, the following domains must be accessible for their networks:
oculus.com
facebook.com
meta.com
fbcdn.net (the "Facebook Content Distribution Network" and delivers photos and videos to people who use Facebook)
akamaihd.net (another Content Distribution Network used by some of the biggest tech companies in the world to stream audio and video and host downloads.)
Also the following ports to allow outbound connections will need to be opened.
443 (TCP)
3478 (TCP)
50000-59999 range (UDP)
This should help get these connections going. If this fails, could you please DM us, get us a screen shot of what you're seeing on your end with these connections and we can go from there.
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Hey again, @kylerc! I wanted to circle back around to see if everything has been taken care of, or if you're still having challenges. Please let us know!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
