Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to Streamer issue #13

Closed
msuch opened this issue Dec 13, 2017 · 6 comments
Closed

Connecting to Streamer issue #13

msuch opened this issue Dec 13, 2017 · 6 comments

Comments

@msuch
Copy link

msuch commented Dec 13, 2017

Hello there,

I have a problem when running Streamer app on HL and trying to connect to it through ComputeOnDesktop.

Streamer on HL works fine - I can air-tap and I see updated video stream object. Launching ComputeOnDesktop, after entering IP app waits 30 seconds then throws an exception:
WinRT information: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

IP address is correct (app is deployed wirelessly). I checked nmap on HL device for open ports while Streamer is running, but only http/s were open (I was expecting 23940 to be also open).

@mtee
Copy link

mtee commented Dec 20, 2017

edit:
this solved it for me:

  1. go to device portal -> Security and disable "Require SSL"
  2. reboot
  3. then the ComputeOnDesktop worked for me.

@msuch
Copy link
Author

msuch commented Dec 28, 2017

@mtee that worked, thank you!

@leoyala
Copy link

leoyala commented Jul 16, 2018

To target an App on the HoloLens for ComputeOnDesktop, which IP should I enter when asked for it? It is a dedicated App on the HL (not deployed wirelessly). Should I deploy the app wirelessly and then deploy the ComputeOnDesktop?

@valavakilian
Copy link

I have the same problem as leonardo-menjivar when deploying with a usb cable

@leoyala
Copy link

leoyala commented Feb 18, 2019

Hello @valavakilian I haven't been able to solve this so far.

@argo-1
Copy link

argo-1 commented Feb 21, 2019

Same issue encountered with ComputeOnDesktop. Receiver runs for ~20 seconds and then throws the same exception. Disabling 'Require SSL' had no impact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants