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

Published SSDP Device Not visible on Local Network #26

Closed
parv0888 opened this issue Aug 20, 2016 · 3 comments
Closed

Published SSDP Device Not visible on Local Network #26

parv0888 opened this issue Aug 20, 2016 · 3 comments

Comments

@parv0888
Copy link

I have successfully published the device in my console app.
The device is visible on the system running the console app. But on the other computers running on the same network the device is not being shown.

@Yortw
Copy link
Owner

Yortw commented Aug 21, 2016

Hi,

It is typically difficult to diagnose these issues remotely, as it is often caused by network/firewalls, or by incorrect publishing of the service or device description document.

You might like to start by checking the suggestions in these previous issues, and then follow up again here if you can't solve it using those. Also make sure you're using the latest version of the Nuget package.

#21

#19

It's also possible if you have multiple NIC's that the publisher is being bound to the wrong one, see the end of this issue for how to specify the IP address of the NIC to bind on;

#2

The big issues are;

  1. Make sure no firewall blocking on either client or server (inbound & outbound for UDP multicast on appropriate ports).
  2. Make sure the end point for your device description document is accessible from the remote machines.
  3. Make sure the XML returned from the device description document url is valid XML and contains exactly the same UUID/device type etc. as you configured the publisher with (should do if you used RSSDP to generate the document).
  4. Try using Intel's Device Spy on the client to see if it is receiving the packets at all.

Good luck, let me know if none of that helps.

@parv0888
Copy link
Author

Hi, Thanks for a prompt reply. My router was consuming the SSDP Multicast and not forwarding it.

@Yortw
Copy link
Owner

Yortw commented Aug 31, 2016

Excellent, glad you found the solution. Thanks updating and closing the issue.

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

2 participants