cannot ping roborio

[MikePerreman]

i think im having issues with mdns, can anyone recommend any fixes, dont take anything for granted, all i claim to have done is install the frc update suite

[Mark McLeod]

Turn off Windows Firewall
Turn off any anti-virus programs
Disable all Network adaptors except for the one you are using
Check your PC's network adaptor to see that it is set to Dynamic or DHCP
Connect your PC to the roboRIO via USB-A/B cable and ping 172.22.11.2
Ping roboRIO-247-frc.local
Ping roboRIO-247-frc.lan
Fire up the roboRIO_ImagingTool to see if it can find the roboRIO
Ping the IP address found by the ImagingTool
Fire up the Driver Station, look on the setup tab and hit the down arrow beside your team number to see what rios it has listed and choose one.
Check the Driver Station -> Diagnostics tab to see what it is pinging
Use Task Manager -> Services tab (sort by name) and look for the status of nimDNSResponder

Alternate:

Setup your robot radio for home use
Set your PC to use DHCP
Connect your PC to the robot radio via wireless and connect the roboRIO via Ethernet to the radio
Fire up the roboRIO_ImagingTool to see if it can find the roboRIO


Read Troubleshooting: http://wpilib.screenstepslive.com/s/4485/m/24193/l/284355-roborio-network-troubleshooting
Radio for Home Use: http://wpilib.screenstepslive.com/s/4485/m/13503/l/144986-programming-your-radio-for-home-use

[MikePerreman]

if this helps at all, over ethernet, no problems, only over wifi, the only antivirus i can find is windows defender. firewall is off

the only light on the diagnostic page is the robot radio

over ethernet, there is no problem

i did reimage the radio using the newest tool off of team forge. still no luck

[Mark McLeod]

What works?
PC Ethernet to radio to roboRIO?
PC Ethernet direct to roboRIO?

[MikePerreman]

pc -> ethernet -> radio -> roborio

[Mark McLeod]

So it's just the wireless that's broken.

I'd check your PC's wireless adapter settings to see if they are the same as the PC Ethernet adapter settings.

You can login to the radio and check those settings as well, or just run it through the radio kiosk one more time to verify that the right team number was used.

[MikePerreman]

so, the settings apear to be equivalent, in network and sharing > change adapter settings (Ethernet {qualcomm atheros}) (wifi {ralink RT3090 802.11n wifi adapter})

what else is there to do?

[Mark McLeod]

Connect via wireless, then check to see what IP your PC got assigned.
cmd prompt> ipconfig /all
also
> arp -a

[MikePerreman]

ok, my ip is 10.2.47.163 on wireless

[Mark McLeod]

What is your roboRIO's IP?

Can you ping the roboRIO IP?

[MikePerreman]

i dont quite know what you are asking, here is a gDoc link to cmd's output
https://drive.google.com/open?id=1CE8LdLM6NGlDsGPeluR8viiQCe2DoDnuE8AklELx7 Q4

[MikePerreman]

ok, lab's closing for the night, i wont have any new information untill 4:00pm (eastern) tomorrow. goodnight all.

[Mark McLeod]

Do you have another robot radio to verify with?
It can actually be just about any AP you might have lying around, and doesn't need to be setup with the radio kiosk.
It also doesn't need to be mounted on the robot, just use a wall power supply for it and connect the Ethernet to the roboRIO.

Double check that the radio is connected to 12v power from the VRM(if it's the 2016 Open Mesh radio). Lower power will affect wireless operation first.
Check to see that you have a fresh robot battery, too.

You can also check the status lights on the radio. It should have a green wireless light, a power light and at least one Ethernet light on.
Then check the roboRIO Ethernet port to see if it shows both solid green (hardware) and blinking yellow(communications) lights on.

[MikePerreman]

i dont have another radio to varified with, the lights on the ethernet of the rio are blinking, all of the lights on the radio are as they should, other computers have no problem deploying code, and connecting with the driver station. i, however, still see that "destination host unreachable" when pinging roboRIO-247_FRC.local

[Mark McLeod]

According to the arp -a result you posted yesterday, at the time your laptop was connected to the rio via USB-A/B (172.22.11.2) just fine, but your wireless could only see as far as the radio (10.2.47.129). The rio would have shown up as 10.2.47.90 or something similar in that part of the listing.
In addition, your radio should also have shown up at address 10.2.47.1, which it did not.
That means the DNS address won't work under any circumstances, because there is no IP address to associate with it.
When you connect, do it with just one active connection (wireless or USB) rather than both active at the same time, and disable the other via the Network Connections Control Panel.

Try an arp -a after connecting one of your other working laptops wirelessly to see what it should look like.

I'd suggest connecting via USB again and using the web browser to check what Ethernet address the radio DHCP has given the rio.
It'll be the non-172.22.11.2 address.
Then try pinging that IP address (it'll try to go through the wireless connection if it is active).

[MikePerreman]

well, new development if i connect over ethernet, then connect over wifi, all is well, untill, i connect to a different wifi, then back to the bot, it wont re-connect to the bot.

[Mark McLeod]

When it fails to connect to the roboRIO, to see if it helps you might try:
cmd prompt> ipconfig /renew

Your PC may be retaining the previous DHCP address it was given.

[MikePerreman]

alright, if this works, is there a way to automatically do this every time i connect to a new network?

EDIT: i found out that task scheduler existed.

[MikePerreman]

Alright, it seems to be working now. ill update if anything goes wrong. Thanks for the help, Mr. McLeod!

[Mark McLeod]

Glad you got it working!

[MikePerreman]

nope, i spoke to soon, its not re-establishing comms after putting ipconfig /renew into run once i connect to the bot radio. however, if i reboot, then, before connecting to any other networks, it connects fine, but once i connect to the shop internet, it no longer works, even with ipconfig /renew

[MikePerreman]

also, im not sure if this is related, but i keep dropping connection to the shop wifi, when i do, i can connect to the bot, 9/10. this is starting to sketch me right the frig out.

[Mark McLeod]

Here's another series of commands to try (all as administrator):

cmd prompt> netsh winsock reset
cmd prompt> netsh int ip reset
cmd prompt> ipconfig /release
cmd prompt> ipconfig /renew (just listing this for completeness)
cmd prompt> ipconfig /flushdns


You can try reinstalling or updating the PC's wireless driver through the Device Manager (Update Driver on the Driver tab for the wireless adapter) or if you can locate the latest network adapter driver software on the manufacturers website.

When the PC doesn't connect, you can try disabling, then re-enabling just the wireless adaptor.

See if you can find a local network expert to take a look at what your pc is doing. Without being able to put my hands on it I'm just going to be shooting in the dark at this point.
That doesn't mean I won't try. :)

[G_rupp]

We had a Windows 8.? computer at a quick build a couple of years ago with a similar issue. The operator selected Public from the list of network location choices (Home, Work or Public) this caused it to block the IP of the wireless connection on the router.

Depending on the Windows version, this can be difficult to diagnose and reset to allow it.

Search for "how to change network location to private" and follow instructions based on Windows version.

[MikePerreman]

here is the response out of the terminal:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.


C:\WINDOWS\system32>netsh int ip reset
Resetting Interface, OK!
Resetting , failed.
Access is denied.

Restart the computer to complete this action.


C:\WINDOWS\system32>ipconfig /release

Windows IP Configuration

No operation can be performed on Ethernet while it has its media disconnected.

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : lan

Wireless LAN adapter Wi-Fi 2:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::7890:2e26:f32e:b804%14
Default Gateway . . . . . . . . . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\WINDOWS\system32>ipconfig /renew

Windows IP Configuration

No operation can be performed on Ethernet while it has its media disconnected.

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : lan

Wireless LAN adapter Wi-Fi 2:

Connection-specific DNS Suffix . : lan
Link-local IPv6 Address . . . . . : fe80::7890:2e26:f32e:b804%14
IPv4 Address. . . . . . . . . . . : 10.2.47.166
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.2.47.129

Tunnel adapter isatap.lan:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : lan

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\WINDOWS\system32>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\WINDOWS\system32>

[MikePerreman]

yes, the network is private, and there is no network professional available to us, we could do something like team veiwer, but i dont know.