search

vervallsweg / cast-web-api

Quick and dirty web API for Google Cast enabled devices.
GNU General Public License v3.0
141 stars 73 forks source link

Mdns doesn't work with Windows Server firewall #84

Open brimmasch opened 5 years ago

brimmasch commented 5 years ago

It appears that after switching to your home grown DNS library discover will not complete or no devices are found in Windows Server 2012 R2.

I see the version print and then the URL:port print and nothing else. It responds to requests so I'm guessing it just doesn't find anything. What information can I provide to help troubleshoot this?

vervallsweg commented 5 years ago

Windows server... I tested it on windows 10 a while back. Are you sure that it works in previous versions on exactly the same setup?

brimmasch commented 5 years ago

Pretty sure. I've had version 1.0.0 pulled from git without changes and running. Updated to 1.0.2 and ran that for a long while without changes aka no code modifications aka port 3000 aka I didn't even bother to specify command line arguments. I changed the branch to 1.1.0 and it won't even do the print that it is attempting discovery.

brimmasch commented 5 years ago

It's related to the firewall. In 1.0.2 I can just open port 3000. In 1.1.0 I have to turn the firewall off or discovery won't complete. Are you using additional ports?

Either way, you may want to set a timeout or whatever it's trying to do and return a meaningful message when it can't complete.

For now I'll just run with the firewall turned off.

vervallsweg commented 5 years ago

Well mdns doesn't really have a logical timeout. You broadcast what you want to know into the network and then whoever thinks he has got a good answer for that, replies to you. Answers to a query don't expire.

I'll look into how the windows firewall might have an issue with the new mdns discovery. Thanks for letting me know 👍