Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

I'm having trouble getting the mDNS for the roboRIO to resolve on our team's DS over wireless. I've installed the NI FRC 2015 update, configured our bridge using the 2015 Bridge Configuration Utility, flashed the roboRIO and installed Java 8, and successfully deployed code and enabled the robot over a wired connection. Our DS is a Windows 7 VM running on VMware Fusion bridging the wifi connection.

Our D-LINk is in 5 GHz AP mode, and I can lookup the mDNS on the Mac, but the lookup fails on the Windows 7 side on wi-fi (but not a wired connection). However, I am able to ping the corresponding IP and connect to the web dashboard for the roboRIO. I have checked that the NI mDNS responder is installed and has properly enabled firewall exceptions, so I'm not too sure what the problem is.

Anyone have any suggestions?

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

When you configured the dLink did you do so for 2.4 ghz mode or 5

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

Are you able to ping the "roboRIO-team.local" address from the windows command line, or just the resolved IP address?

Both should work, the first does the lookup similar to the DS and the second verifies that the device responds independent of mDNS.

Greg McKaskle

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

We were having issues with this. These are the troubleshooting steps we went through.

• Ensure that you imaged the roboRIO for your team number.
• Allow UDP port 5353 through the firewall on both inbound and outbound connections.
• Make sure your computer is set to receive its IP via DNS, which is different from last year, when our team used a script to set static IP.
• Try logging into the D-Link web interface at 10.TE.AM.1, with username 'Admin' and a blank password. Click Advanced, then on the left, DHCP. Scroll down to see the list of DHCP clients, and see if the roboRIO is assigned an address.

See if any of these resolve your issue.

EDIT: Additionally, your DLink should be in 2.5Ghz AP mode, not 5Ghz.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

Your AP can be at 5GHz as long as your laptop and other clients support 5GHz. And if they do, it would be better to use than 2.4GHz.

Greg McKaskle

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

We have everything running on 5 GHz. We used the same setup hardware-wise last year and didn't have any problems.
I've been able to ping the roboRIO IP on the Windows side, but I am unable to perform the mDNS lookup.

I'll try to reconfigure our DLink on 2.4 GHz, but we've traditionally used 5 GHz because our campus wifi and apartments next door tend to generate quite a bit of wireless interference.

Thanks for the help guys. I'll let you know if it works.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

Based on other threads, I'd first verify that the firewall is off and isn't interfering. I don't see how 2.4 and 5 has anything to do with mDNS.

If you have an Axis M1013 camera, you may also check to see if axis-camera.local works to access it. Or you could test with any other device that supports Bonjour or mDNS. Since this is a VM, can you see if there is a later version, or configuration that has disabled it?

Greg McKaskle

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

I don't think switching to 2.4 GHz will change anything either, but stranger things have happened. Never hurts to try.

I've triple-checked the Windows Firewall and made sure that both the driver station and the mDNS resolver have permission to access the network.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

Try switching the VM network setting to NAT instead of bridged.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

The VM is already running in bridged mode. Thanks for the suggestion, though.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

If you have an antivirus program installed, it might have its own firewall. Check that too.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

Try NAT instead.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

This looks like the same issue we had as discussed in this thread:

http://www.chiefdelphi.com/forums/sh...d.php?t=132607

On the router in Setup->LAN Settings page, set the IPV6 connection type to "Autoconfiguration(SLAAC/DHCPv6)

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

Our problem is the reverse of this problem; the OS X side can resolve it while the Windows VM can not. I tried it though, and it didn't seem to help the problem. I'll keep this in mind if future problems arise, though. Tweaking IPv6 settings never occurred to me. Thanks!

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

This fixed the problem with resolving the mDNS address, but now we have a different one. I am able to properly resolve the mDNS name over wi-fi and connect to it via web console, but the 2015 DS software is unable to ping it or otherwise establish robot communication.