Hello everyone.

The Mixed Reality Forums here are no longer being used or maintained.

There are a few other places we would like to direct you to for support, both from Microsoft and from the community.

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.

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, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.

And always feel free to hit us up on Twitter @MxdRealityDev.

Set up HoloToolkit-Unity Sharing Service Server

Hi, I wanted to set up the Sharing Service by itself on a laptop and have two other HoloLens' connect through WiFi. I've tried running the SharingServices.exe from External/HooToolkit/Sharing/Server/SharingServices.exe -local but get Error code 5 refusal of incoming connections. I've followed the Holograms 240 Lesson to the letter, but seem to still have problems.

Stephen Hodgson
Microsoft HoloLens Agency Readiness Program
Virtual Solutions Developer at Saab
HoloToolkit-Unity Moderator

Comments

  • Seems to be happening only for port 20605 but devices have been able to connect and share. Is this a problem in the SessionManager.UI?

    Stephen Hodgson
    Microsoft HoloLens Agency Readiness Program
    Virtual Solutions Developer at Saab
    HoloToolkit-Unity Moderator

  • @AlexD any thoughts on this?

  • AlexDAlexD ✭✭✭
    edited August 2016

    Port 20605 is used for AutoDiscovery. Essentially every component of the sharing toolkit (server, client, manager) will try and open a listening socket on port 20605 so they can respond to broadcasts that try to detect devices. So if you try to run multiple "components" on the same machine you'll get error 5 because the port is busy and socket cannot be opened. Try and run the server first (no ManagerUI, no emulator, no debug session, no Unity player). Essentially it does not impact the ability for the sharing to work, just that AutoDiscovery won't work.

    As a side note, other important ports to mention (and make sure are not otherwise occupied on the system) are:
    20602 - server incoming connection port
    20601 - "default" session port.

Sign In or Register to comment.