We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.
On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.
So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality. If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers. And always feel free to hit us up on Twitter @MxdRealityDev.
Can't connect to HoloLens Device Portal through wifi
So I followed all the steps here: https://docs.microsoft.com/en-us/windows/mixed-reality/using-the-windows-device-portal
and I cannot connect to the Device Portal on my hololens through a wifi connection.
Specifically this does not work:
- Connect from Windows machine on wifi to hololens wifi portal
- Connect from Ubuntu machine on wifi to hololens wifi portal
But this does work:
- Connect from Windows machine via usb cable to device portal
- Connect from Ubuntu machine on ethernet cable to hololens wifi portal
I can't ping the hololens on wifi or on ethernet, but I can connect to the device portal when on ethernet or through a direct usb connection...
I tried disabling windows firewall to no avail. I set the network to a private network, no change.
The hololens is set on developer mode, and device portal is enabled.
Is there anything I may be missing in order to connect over wifi? I already contacted both hololens and windows support, both of which told me to contact the other and that it wasn't their problem.