#Connection timeout

1 messages · Page 1 of 1 (latest)

pallid lantern
#

I'd also recommend resetting your router!

#

Went afk rq, let me turn my pc on and we can suss out what's causing this!

#

Not necessary. ALVR does what VD does + more!

#

You are gonna want to make sure you are on the latest update!

#

If you wouldnt mind

#

typo

#

20.6 you'll want to be on!

#

platform, headset, install method, specs, laptop or PC, logs in .txt form and screenshots if applicable

#

that is the info we need from ya! ^

#

Windows 10 or 11

#

you are running older hw

#

which is fine

#

I will stick with my initial recommendation

#

try resetting your router

#

yes

#

if you reset the router, itll reset the whole network, including ethernet!

#

Have you enabled firewall drivers

#

within ALVR

#

yes

#

and in SteamVR

#

yep

#

yep

#

it is in options

#

advanced

#

I dont remember offhand

#

there is only 6 or so tabs itll be under one of them

#

make sure ALVR is enabled once you see it!

#

Uhh

#

what for?

#

Language shouldn't matter so long as you can understand it!

#

I can't understand that

#

I'm sorry

#

The one that is ALVR, enable that

#

I assume you're German or Austrian?

#

ah so Austrian

#

ok

#

It should be there

#

Oh my mistake!

#

Ah yes

#

I should've known that considering I also live in Europe

#

oops

#

There ya go

#

It is enabled!

#

Yes please

#

It is set as it should be

#

I need you to go on ALVR

#

and paste the logs here in a .txt file

#

Should diagnose the issue

#

Then I can find a solution for you

#

on ALVR!

#

on the console

#

terminal

#

'Logs'

#

Ok, so you have a handshake error and OS error 10053. Allow me to quickly check the ALVR github for a solution

#

Oh crap, a massive meteorite is about to hit

#

I will return here in 5 minutes!

#

So this will be within ALVR

#

for the os error

#

Simply follow the instructions that are in the thread based on what you think your PC and setup needs!

#

Report back any issues here and we will do our best to assist!

#

I would recommend not overdoing it!

#

Setting it so it causes even more errors to show up!

#

It works through ports

#

You can do it via USB but that is more complicated, id recommend doing it through ports

#

I should have asked this earlier. How technically competent do you consider yourself?

#

I fear I may have been giving too much technical jargon to you!

#

This probably requires a more simple fix!

#

not a problem!

#

Well the next step would be to do some commands in cmd prompt (admin enabled)

#

Do you feel able to do this?

#

I'd need you to paste the outputs

#

Uhh

#

You shouldn't worry about that

#

That is just scaremongering lol

#

Even for an admin with system priveleges, deleting system32 is extremely difficult

#

powercfg /query SCHEME_CURRENT SUB_SLEEP STANDBYIDLE
powercfg /change standbyidle SCHEME_CURRENT SUB_SLEEP STANDBYIDLE 0

#

These will prevent the network from going to sleep

#

ipconfig /all
ping [Oculus_Quest_IP] (replace [Oculus_Quest_IP] with the actual IP address of the quest. This can be found in your network admin settings

#

first one displays detailed info about the network, second is a ping test

#

you log into your admin in the browser

#

normally

#

log in

#

login to your admin network gateway to confirm which IP your Q2 is using

#

it will be different to the ip displayed on ip listing websites!

#

Eh. don't worry. This may be a bit OTT

#

bear with

#

netstat -an

#

checks for listening states

#

cmd prompt

#

type it in

#

netstat -an

#

what is em

#

oh right

#

are they all working as they should be

#

ok

#

let's try this

#

ipconfig /flushdns

#

check your ALVR and see if it is working as it should be (restart your computer first though)

#

yes

#

see if it works as intended

#

...hm

#

give me a moment

#

Others have recently experienced these issues and it was solved by updating to latest versions on everything

#

ok

#

this may not normally be a good idea, but try disabling your firewall

#

if it works when disabled, we know what the issue is!

#

@copper bison

#

Right, so it is a Quest issue

#

are you on the latest firmware

#

on your q

#

idr offhand, but if it isnt saying you need to install an update you are fine

#

as i said, i don't remember offhand

#

@copper bison

#

could you try air link for me rq

#

where oculus link normally is, air link is also there

#

lucht verbinding

#

it is pretty straightforward

#

you just go into the main menu and select oculus link

#

and then air link

#

is your quest connected to the same wifi as your PC

#

and do you have the oculus app installed

#

doesnt matter, same network!

#

how come

#

if I may ask, how old are you

#

ah ok

#

is this your dads computer you are using?

#

likely he wouldn't want you touching command prompt networking stuff... hmm ok

#

this is tricky

#

Understood

#

I don't discriminate based on age however you may be better off seeking out your father for assistance with this

#

we've done all the main troubleshooting steps... this looks to be a network issue that I likely can't diagnose and solve in this manner unfortunately

#

the next step would be testing air link and tethered ALVR

#

to see if the network issue persists

#

wired

#

via USB

#

this is likely a bit beyond what you are capable of doing yourself!

#

oculus charger is for charging only, not data transfer

#

I feel like you may have missed a step or two in the setting up of your VR

#

and unfortunately, I don't know which steps those are

#

This fella has been having issues with connection timeouts on his Q2

#

Only 13, so I've adapted how I relay technical information

#

My apologies.

#

(OS is Windows)

#

Specs and technical info regarding setup can be found here!

#

Plyshka joined the thread. They are a Linux user, however perhaps they can shed some light on how to fix this issue?

#

I've run you through all the troubleshooting steps I would do myself... so maybe there is another solution?

#

Ah yes, I was looking for that first thread but I couldn't locate it!

#

Thank you!

#

The second one I did link, they tried that, no cigar!

#

I fear that this fellow may not have set up all the programs and headset correctly, maybe missing a step which led to these errors..?

#

Without seeing it firsthand I can't determine where though