[darrellt]

We're having problems connecting a Windows 10 laptop to our roboRIO over wifi (OM5P-AN), via the driver station.

We have configured the OM5P-AN according to the WPI instructions. We are using a new Win 10 laptop that has been configured using the latest FRC 2016 software. We have imaged the RoboRIO with the 2016 image.

Here is the data that we have collected.

When connected to the roboRIO via USB (directly) and/or ethernet cable (through the OM5P-AN):
We can access the roboRIO dashboard via its webserver (we had to use Firefox -- IE and Chrome don't support Silverlight) using the URL roboRIO-2635-FRC.local
The dashboard tells us that the IP address for the roboRIO is 10.26.35.18
We can successfully ping 10.26.35.18
We can successfully ping roboRIO-2635-FRC.local
We can successfully connect to the roboRIO via the DS

However, when connected to the roboRIO via wifi (through the OM5P-AN):
We cannot access the roboRIO dashboard using the URL roboRIO-2635-FRC.local, but we can access it via the IP 10.26.35.18.
Interestingly enough, we can also access the dashboard via the URL roboRIO-2635-FRC.lan
We can successfully ping the roboRIO at 10.26.35.18 and roboRIO-2635-FRC.lan
We cannot get a ping at roboRIO-2635-FRC.local
We cannot successfully connect to the roboRIO via the DS

We have tried turning off windows defender and retrying connection via wifi without success.
We have checked and verified that the service nimDNSResponder is running.
The laptop does not have Inventor installed.

We have used the same computer as in the above test and used it to connect and control a robot that is using last year's DAP-1522 wifi router. This all worked just fine -- we had no problems connecting with the drive station through wifi.

This all appears to point to a problem with mDNS on the OM5P-AN when connected via wifi.

Is this strictly a Windows 10 problem? Any ideas for further troubleshooting? Help!