cancel
Showing results for 
Search instead for 
Did you mean: 

Connectivity Issue: Unable to Ping PC from Meta Quest Pro on Same Network

CESITDTK
Honored Guest

Hi everyone,

I'm having trouble connecting my Meta Quest Pro to a locally hosted server on my PC, and I’d appreciate some help troubleshooting. Here’s what’s happening:

Initial Setup and Test:

I first tested on a traditional home network:

  • My PC was assigned an IP like 10.191.x.x (private IP range).
  • My Meta Quest Pro had an IP like 194.206.x.x (public IP range).

In this setup:

  • I could ping my Quest Pro from my PC.
  • But I could not ping my PC from the Quest Pro.

Test with Mobile Hotspot:

I switched both devices to my phone’s mobile hotspot to rule out network-specific issues. Here’s what happened:

  • My PC received an IP like 192.168.124.x (private IP range).
  • My Quest Pro still received an IP like 92.x.x.x (public IP, likely from the mobile network).

Again, in this scenario:

  • I could ping the Quest Pro from my PC.
  • But I could not ping the PC from the Quest Pro.

Troubleshooting Steps Taken:

  1. Ensured both devices were connected to the same Wi-Fi network (hotspot).
  2. Verified IP addresses and noted they belong to different subnets in both setups.
  3. Tried pinging both ways:
    • PC → Quest Pro: OK (For work's network).
    • Quest Pro → PC: Fails (for both networks).

Key Observations:

  • In both setups, the Quest Pro is assigned an IP outside the private subnet, even when connected to the same network as the PC.
  • This likely explains why the Quest Pro can’t reach the PC, but I’m not sure how to resolve it.

Questions:

  • Has anyone experienced similar issues with the Meta Quest Pro?
  • How can I ensure the Quest Pro gets a private IP when connected to a hotspot or home network?
  • Any tips for ensuring proper connectivity for local servers?

Thanks for your help! Let me know if more details are needed.

1 REPLY 1

user_901925786032222
Expert Consultant

It doesn't really make sense for two devices connected to the same wifi network to receive IP addresses in different subnets. Assuming both are configured for DHCP, the one way I can see the headset receiving a public IP is if a VPN is involved somehow.