SmartDashboard Connection Issue Windows 10

[seg9585]

We have been using SmartDashboard without any problems on our DS laptop (running Windows 8), and a test laptop (running Windows 7), but our DS laptop has been having networking issues so we need to switch to a different one for our next competition (running Windows 10).

However, we are unable to get a connection to the SmartDashboard data with this Windows 10 laptop. The DriverStation software connects to the robot fine (Teleop Disabled, etc), and I verified that all firewalls have been disabled on the new laptop. All the latest FRC update software is installed. The "Connection Indicator" on the SmartDashoard stays false.

Anyone else having trouble with Windows 10 that can recommend another troubleshooting step?

[lethc]

Check through your firewall settings and make sure all FRC-related things are allowed through. Or you could just turn it off.

[seg9585]

Yes, the firewall is turned off, and even if on the FRC related items are allowed through (in advanced settings). What else can I try?

[vScourge]

Try turning User Account Control completely off. Also turn SmartScreen off.. I think we disabled that as well, although I don't recall what it does.

[seg9585]

The above tips didn't seem to change anything, however I did manage to find a workaround by using the Static IP workaround forcing the roboRio to use 10.xx.yy.2 and setting a static IP on the DS), and then disabling mDNS in the SmartDashboard preferences. Not ideal, but at least the smartDashboard now functions.

[TylerS]

Originally Posted by seg9585

The above tips didn't seem to change anything, however I did manage to find a workaround by using the Static IP workaround forcing the roboRio to use 10.xx.yy.2 and setting a static IP on the DS), and then disabling mDNS in the SmartDashboard preferences. Not ideal, but at least the smartDashboard now functions.

Are all your other network adapters besides the one connected to the robot disabled? Whenever we were having trouble connecting using mDNS disabling extraneous adapters always fixed it.