Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Nisbo's avatar
Nisbo
Honored Guest
6 years ago

srv _ldap._tcp.dc._msdcs issue

There is a really big issue with the Oculus Software.
Today I tried Oculust Quest with Oculus Link on my Win 10 - 64 Bit PC, so far this worked as expected ... from the Gameplay

However to install it on a different hard-drive than C you have to use parameter like in the stone time ^^ instead of using a gui file chooser ;)
OK this is not the problem, but it is very funny :D

The problem is that after I stopped gaming I observed a high CPU usage on my Unifi Security Gateway (Router)
in between I also observed some small interruption on MultiCast IPTV (I assume this happened due to the CPU usage)

I checked PI Hole (acting as a DNS resolver to detect problems like this) and I was not amused
Millions of entries (5.377.147) in 3 hours (around 5000-6000 every 10 seconds) for
srv _ldap._tcp.dc._msdcs.admin-pc.localdomain   

where admin-pc.localdomain is the local address of my Gaming PC

It started as I installed the Oculus App so it was easy to detect the problem
Taskmanager --> killed all Oculus Apps, no change
btw Oculus is always running in the backgound, there is no option to disable it in the settings, very bad solution/programming :/
I rebooted the PC, no change
I de-installed Oculus, no change --> wtf
I rebooted again after de-install, no change --> really ?

So it looked like an DDOS attack. Restarting the Unifi Security Gateway (Router) solved the problem

After this I started the Oculus setup again and it came back immediately after I start the Oculus Setup
I tried it several times to verify. Don't know what you are doing, looks like you are opening a lets call it back-door to the PC with the wrong routing

and of course there is no ns entry 
Microsoft Windows [Version 10.0.18363.535]
(c) 2019 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\Admin>nslookup -type=srv _ldap._tcp.dc._msdcs.admin-pc.localdomain
Server:  USG-PRO-4
Address:  192.168.178.1

*** _ldap._tcp.dc._msdcs.admin-pc.localdomain wurde von USG-PRO-4 nicht gefunden: Non-existent domain.

C:\Users\Admin>nslookup -type=srv _ldap._tcp.dc._msdcs.admin-pc.localdomain 192.168.178.128
Server:  raspberrypi
Address:  192.168.178.128

*** _ldap._tcp.dc._msdcs.admin-pc.localdomain wurde von raspberrypi nicht gefunden: Non-existent domain.

C:\Users\Admin>

Looking forward to get a solution
Greetings from Germany


1 Reply

  • Nisbo's avatar
    Nisbo
    Honored Guest
    6 years ago

    Here are some more results from my testing regarding the problem in the 1st post, finally I got it running

    • I started the installation
    • the behaviour was observed again
    • I change to google DNS
    • USG CPU load decreased to nominal
    • after the installation I changed back to the PI Hole DNS and everything is still nominal

    The "root case" is the installer because it is doing "crazy" things ^^

    How
    ever it looks like this is a bad combination of installer, USG and
    PI-Hole, somewhere in between there is a small bug, maybe my brain :D