Quote:
Originally Posted by Greg McKaskle
I haven't seen it this year, but one of the bugs that we weren't able to make much progress on was when the multicast group was not up to date. So the mDNS calls return normally, but return cached results. I was watching the TCP traffic and could tell that the discovery was not going over the wire.
I believe that if you fiddle with the laptop networking enough, it will connect without requiring a reboot. Specifically, when Windows decides it needs to update the multicast group, the mDNS call will suddenly find the device that was connected the whole time. I was never able to find a way to flush or rebuild that info.
|
Other than a full PC reboot, disabling and re-enabling the network adapter consistently resolves the problem whenever I see it. Presumably that forces the multicast group update.
I've not been able to resolve the problem just using "ipconfig /flushdns"
Hope this helps!
EDIT: sorry, neglected to also mention that when I've seen the problem, other networking apps all work fine....I'm able to ping roborio-XXXX-frc from the command line, able to ssh into it with PuTTY, etc