In an ideal world, tech gadgets would work flawlessly all the time. But we are not living in an ideal world, are we? If you are currently facing Wi-Fi connectivity issues with your beloved Oculus Quest 2 headset, then you have arrived at the right place.
The most common steps to fix Oculus Quest 2 W-iFi related issues [e.g Disconnects or not connecting at all, Wi-Fi not turning on, connected but no internet]:
- Restart your headset
- Power your router off/on
- Separate 2.4 GHz & 5 GHz bands in router settings
- Forget network and reconnect [Oculus App]
- Do a hard reboot on your headset
- Factory Reset
Let does next look at different scenarios and fixes in a bit more detail. I have divided the Wi-Fi problems into different categories, but feel free to mix and test the different solutions that are offered in this article.
Did you hear? Facebook [Meta] is going all-in on virtual reality and metaverse. Get a Quest 2 headset and be a part of the future of entertainment!
Oculus Quest 2 Keeps Disconnecting From Wi-Fi
If you are able to establish a Wi-Fi connection, but your Quest 2 keeps disconnecting after a certain period, try these steps to fix the problem:
- Power your router off and back on again
- Restart your headset
- Forget the Wi-Fi network and reconnect [via Oculus app]
- Try using different Wi-Fi networks [e.g Windows / Mobile hotspot]
- Disable “Smart Connect” from router settings
- Split 2.4 GHz & 5 GHz bands in router settings
- Reset Router to default settings
- Set up a dedicated router for Quest 2
The most common reason for frequent disconnects from Wi-Fi seems to be that Oculus Quest 2 is unable to properly function with Wi-Fi networks that have 2.4GHz / 5GHz bands configured for a single SSID [Wi-Fi network name].
Often referred to as “Smart Connect”, the router automatically switches devices [including the Quest 2] between the 2.4GHz and 5GHz bands. This, unfortunately, causes disconnects and issues with the Oculus Quest 2.
The solution is to create separate Wi-Fi networks for 2.4GHz and 5GHz bands and connect your Quest 2 to only one of them. For regular gaming, 2.4GHz is enough, but if you use Virtual Desktop or Oculus Air Link, a 5GHz connection should be preferred.
Since there are so many different routers available, it is hard to give a “one-fits-all” manual on how to split the bands. Look under your router for management console login details and google “[your router] split 2.4 and 5ghz” on how to do it.
Before jumping in changing your router settings, be sure to try the simple things first- restart your router and headset. Sometimes forgetting the Wi-Fi network and then reconnecting again via Oculus App on your smartphone might also help.
If nothing else works and you verified that there are no disconnects when using a different Wi-Fi network [e.g mobile hotspot], then sometimes it might be worth trying to reset your router to default settings.
Note! Only reset your router to default settings if you know what you are doing and can later handle basic router configuration.
If you have tried everything and nothing seems to work, you could opt for purchasing and setting up a dedicated router for your Oculus Quest 2. This is actually quite common and recommended for people who are using Virtual Desktop and want optimal performance.
- Article
- 03/03/2022
- 5 minutes to read
This article explains how to troubleshoot frequent disconnections to an Azure virtual machine [VM] through Remote Desktop Protocol RDP].
You face intermittent RDP connectivity problems during your sessions. You can initially connect to the VM, but then the connection drops.
This problem may occur if the RDP Listener is misconfigured. Typically, this problem occurs on a VM that uses a custom image.
To troubleshoot this issue, use Serial control or repair the VM offline by attaching the OS disk of the VM to a recovery VM.
Connect to Serial Console and open CMD instance. Then, run the following commands to reset the RDP configurations. If the Serial Console is not enabled on your VM, go to the next step.
Lower the RDP Security Layer to 0. At this setting, communications between server and client use the native RDP encryption.
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'SecurityLayer' /t REG_DWORD /d 0 /f
Lower the encryption level to the minimum setting to allow legacy RDP clients to connect.
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'MinEncryptionLevel' /t REG_DWORD /d 1 /f
Set RDP to load the user configuration of the client computer.
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'fQueryUserConfigFromLocalMachine' /t REG_DWORD /d 1 /f
Enable the RDP Keep-Alive control:
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'KeepAliveTimeout' /t REG_DWORD /d 1 /f
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v 'KeepAliveEnable' /t REG_DWORD /d 1 /f
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v 'KeepAliveInterval' /t REG_DWORD /d 1 /f
Set the RDP Reconnect control:
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritReconnectSame' /t REG_DWORD /d 0 /f
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'fReconnectSame' /t REG_DWORD /d 1 /f
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v 'fDisableAutoReconnect' /t REG_DWORD /d 0 /f
Set the RDP Session Time control:
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritMaxSessionTime' /t REG_DWORD /d 1 /f
Set the RDP Disconnection Time control:
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritMaxDisconnectionTime' /t REG_DWORD /d 1 /f REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'MaxDisconnectionTime' /t REG_DWORD /d 0 /f
Set the RDP Connection Time control:
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'MaxConnectionTime' /t REG_DWORD /d 0 /f
Set the RDP Session Idle Time control:
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritMaxIdleTime' /t REG_DWORD /d 1 /f
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'MaxIdleTime' /t REG_DWORD /d 0 /f
Set the "Limit the maximum concurrent connections" control:
REG ADD "HKLM\SYSTEM\CurrentControlSet\control\Terminal Server\Winstations\RDP-Tcp" /v 'MaxInstanceCount' /t REG_DWORD /d 4294967295 /f
Restart the VM, and try again to connect to it by using RDP.
Attach the OS disk to a recovery VM.
After the OS disk is attached to the recovery VM, make sure that the disk is flagged as Online in the Disk Management console. Note the drive letter that is assigned to the attached OS disk.
On the OS disk that you attached, navigate to the \windows\system32\config folder. Copy all the files in this folder as a backup, in case a rollback is required.
Start Registry Editor [regedit.exe].
Select the HKEY_LOCAL_MACHINE key. On the menu, select File > Load Hive:
Browse to the \windows\system32\config\SYSTEM folder on the OS disk that you attached. For the name of the hive, enter BROKENSYSTEM. The new registry hive is displayed under the HKEY_LOCAL_MACHINE key. Then load the software hive \windows\system32\config\SOFTWARE under the HKEY_LOCAL_MACHINE key. For the name of the hive software, enter BROKENSOFTWARE.
Open an elevated Command Prompt window [Run as administrator], and run commands in the remaining steps to reset the RDP configurations.
Lower the RDP Security Layer to 0 so that communications between the server and client use the native RDP Encryption:
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'SecurityLayer' /t REG_DWORD /d 0 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'SecurityLayer' /t REG_DWORD /d 0 /f
Lower the encryption level to the minimum setting to allow legacy RDP clients to connect:
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'MinEncryptionLevel' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'MinEncryptionLevel' /t REG_DWORD /d 1 /f
Set RDP to load the user configuration of the client machine.
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'fQueryUserConfigFromLocalMachine' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'fQueryUserConfigFromLocalMachine' /t REG_DWORD /d 1 /f
Enable the RDP Keep-Alive control:
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'KeepAliveTimeout' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'KeepAliveTimeout' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v 'KeepAliveEnable' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v 'KeepAliveInterval' /t REG_DWORD /d 1 /f
Set the RDP Reconnect control:
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritReconnectSame' /t REG_DWORD /d 0 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'fReconnectSame' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritReconnectSame' /t REG_DWORD /d 0 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'fReconnectSame' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v 'fDisableAutoReconnect' /t REG_DWORD /d 0 /f
Set the RDP Session Time control:
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritMaxSessionTime' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritMaxSessionTime' /t REG_DWORD /d 1 /f
Set the RDP Disconnection Time control:
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritMaxDisconnectionTime' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'MaxDisconnectionTime' /t REG_DWORD /d 0 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritMaxDisconnectionTime' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'MaxDisconnectionTime' /t REG_DWORD /d 0 /f
Set the RDP Connection Time control:
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'MaxConnectionTime' /t REG_DWORD /d 0 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'MaxConnectionTime' /t REG_DWORD /d 0 /f
Set the RDP Session Idle Time control:
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritMaxIdleTime' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v ' MaxIdleTime' /t REG_DWORD /d 0 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'fInheritMaxIdleTime' /t REG_DWORD /d 1 /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v ' MaxIdleTime' /t REG_DWORD /d 0 /f
Set the "Limit the maximum concurrent connections" control:
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\control\Terminal Server\Winstations\RDP-Tcp" /v 'MaxInstanceCount' /t REG_DWORD /d ffffffff /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\control\Terminal Server\Winstations\RDP-Tcp" /v 'MaxInstanceCount' /t REG_DWORD /d ffffffff /f
Restart the VM, and try again to connect to it by using RDP.
Contact support. If you still need help, contact support to get your issue resolved quickly.