Meta Quest Pro WiFi setup fail on university network

xRagnorokx "  No, not really.   Fortunately, my university offers a few levels of Wi-Fi access that were sufficient to at least get through the setup.

* We have a "guest" network that doesn't require authorization, but provides little more than web browsing; most ports are closed.  But this is sufficient for me to establish enough of a connection to look at the details and get the MAC address.

* I can then go to a university website and register that MAC address on my account

* Having done that, I can then connect to a "setup" network (intended I guess for IoT and other stuff) that provides enough access to complete the Quest device setup.  The "connect" button turns blue.  [The choice of "setup" as the service name is merely coincidental with the fact that it works for Quest setup.  The university offers it as a mechanism for setting up any kind of device by virtue of pre-registering its MAC address, I guess as an alternative to the domain and system-certificate authentication.]

* Sometimes, after having gone through that, I can then connect to the fully-privileged wireless network, but have not needed to, so haven't thoroughly tested it.  I had an appointment with an IT guy in August to try to debug the connection issue, to verify whether the Quest was sending the correct Domain and System Certificate info.  But then the university was hit with a serious security breach, and a conscious decision was made to disconnect the entire university from the Internet -- right at the beginning of the semester -- until they had a chance to asses the damage, repair, and institute new security measures before reconnecting.  The IT guys worked round-the-clock for several days to get the university back on-line, the Quest-authentication debugging got put on hold, and we've never picked it up again.

Quest has been typically useless in helping to resolve the issue.  I've never gotten any assurance from them that they've tested the Domain and System Certificate functionality to verify that the user input is retained and used, or any explanation of why it's not retained in the user interface.  I don't get the sense that they've even read my comment, or understood it.  Very frustrating; lousy tech support.

Hey there, twhall. We understand that this isn't the response you had hoped for, but as mentioned we are unable to assist with making changes to private networks. The security of our users is one of our highest priorities, and troubleshooting a private network could compromise that security. We appreciate your understanding and we hope you enjoy the rest of your day!

When it comes to XR stuff on this campus, we are the people that the IT department looks to for guidance.  They have guidance for how to connect Android devices to the network, which we have followed.  You haven't given me any information that I can take back to them regarding any additional access requirements that they're not meeting.

You also have not responded to my observation that the Quest Pro does not seem to retain the settings for CA Certificate and Domain, which appears to me to be the most likely cause of the failure to authenticate.

We routinely connect many other devices to this WiFi network, including Microsoft HoloLenses, as well as various notebooks, tablets, and other mobile things, with unfettered access.  If the Quest Pro needs something unusual in terms of IP port access simply to get through the device setup, please provide specific information on what that is.

Please verify that there isn't a bug in the WiFi settings dialog that prevents it from properly applying the Use system certificates selection and Domain name entry.  In any case, please fix the settings dialog so that it retains those selections (as it retains other fields) so that I don't have to repeatedly reset them.