search

watson / bonjour

A Bonjour/Zeroconf protocol implementation in JavaScript
MIT License
627 stars 146 forks source link

Not finding devices on Windows 10 #58

Open bblanke opened 4 years ago

bblanke commented 4 years ago

Hi! First off, this library is great. It works flawlessly on Mac. However, I'm having a hard time finding devices on Windows 10.

I can discover devices properly using the mDNS Browser Chrome extension on Windows - so the machine is able to discover devices (somehow). However, I'm unable to discover any services using this library or dns-sd (which I installed through the Apple Bonjour SDK).

I'm sorry if this isn't the best place to post about this, but I'm wondering if anyone's encountered the same issue and how they got around it. Thanks for any help!

RichardFoss commented 4 years ago

I am having the same issue with Windows 10, and unfortunately haven't yet found a way around it. My (very simple) code works fine on my MacBook, but not on my Windows machine: bonjour = require('bonjour')(); // browse for all http services bonjour.find({ type: 'http' }, function (service) { I have used WireShark on my Windows machine to check that I am receiving mdns responses from my various devices, using the same wireless interface, and I am seeing the responses. A local software service associated with one of the devices is picked up. So the Bonjour module does appear to be working, just not responding to network devices. Any help would be much appreciated!

fusionstream commented 4 years ago

Does not work on Windows 10 for me either. Device does not even appear when a localhost bonjour browser.

scpedicini commented 4 years ago

I'm having the same issue (Windows 10), internally bonjour NPM package finds it but doesn't seem visible outside node.

zwhitchcox commented 4 years ago

Same issue

blamay commented 3 years ago

Same

mathertel commented 3 years ago

Just an observation: When disabling all WiFi network adapters and using the ethernet only my machine can find devices. Otherwise not.

ffongmdsp commented 1 year ago

For me, it was the VirtualBox Host-Only Ethernet Adapter. Once I disabled it works fine. And at the same time Wireshark sees the proper MDNS traffic appears on my Ethernet interface.