Two weeks ago all of our headsets (a mix of Quest 2 and Quest Pro) stopped seeing our computers via Air Link, they spin in "Searching for PCs..." forever.
Cable Link works normally.
Since we have a fairly complicated network setup I contacted our network consultants to see if anything had changed on that side. Nothing had changed, but they still tried to reset our Wi-Fi Access Points, to no avail.
The headsets are on the right subnet, with the right DNS server.
We tried: * a factory reset of one headset * moving to and back from PTC * disabling the windows firewall of the target PC * connecting the PC to the Wi-Fi AP the headset is connected to
Without success.
Using MQDH we are able to connect to the devices via USB and then transition to ADB over Wi-Fi without any problem. Inspecting the logs in MQDH shows that a non factory-reset headset still thinks it's paired to a computer, but is unable to DNS resolve to it's host
mdns: DNSServiceProcessResult failed with 0, failed to resolve the network address for boris::TREB-PC-016
We have a Windows Active Directory Domain, so we host our own DNS. It is accessible and can successfully resolve TREB-PC-016.
It would be nice if headsets in Development Mode could Air Link to a specific IP.
This is a big productivity hit for us because everyone is used to Air Link and we don't have enough Link Cables to plug all the headsets.
