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

Windows 10 Loses Devices On WiFi Network Toggle #29

Open
wumpus7 opened this issue Jun 13, 2019 · 4 comments
Open

Windows 10 Loses Devices On WiFi Network Toggle #29

wumpus7 opened this issue Jun 13, 2019 · 4 comments

Comments

@wumpus7
Copy link

wumpus7 commented Jun 13, 2019

We're seeing the following issue:

Windows 10 laptop on wireless network A.

  1. Start up our app, browse for devices, devices found.
  2. Change wifi network to B. (Old devices lost, new devices found.)
  3. Switch back to wifi network A, no devices found.

The only way to find devices again seems to be to restart the laptop.

@wumpus7
Copy link
Author

wumpus7 commented Jun 13, 2019

Using dns-sd, I can see that the devices are added and removed appropriately until step 3, so this looks like an OS issue. (That is, if dns-sd can't see the devices, then there's no way QZeroConf can.)

@wumpus7
Copy link
Author

wumpus7 commented Jun 14, 2019

Alternatively, since you have to install Bonjour on Windows, it could be an issue with the Bonjour library... Which would make it Apple's bug instead of Microsoft's.

@jbagg
Copy link
Owner

jbagg commented Jun 28, 2019

I've updated the boujour sdk in QtZeroConf from 333 to 878.200. Please test. I've seen a lot of firewall issues with windows 10. Devices initially discover and then disappearing after a few min.

@AVee
Copy link

AVee commented Dec 31, 2019

From what I've seen multicast in Windows depends on the metric of the interface, where the interface with the lowest metric will be used for multicasts. By default Windows sets the metric automatically, but often gets it wrong when there are changes to the interfaces. If you set the metric manually on the Wifi interface to be the lowest in the system it will probably start working again. (Unless the issue you are seeing is something different...)

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

3 participants