Can connect to the roboRIO by IP but not by hostname

[Hsifeulbhsifder]

We have run into this issue where one laptop (the programming laptop) is not able to connect to the roborio by hostname (roborio-5428-frc.local), but we can connect via IP (10.54.28.90). This problem only exists with this laptop, however, it is our programming laptop, and we are unable to upload code or ssh files into the rio by hostname. This also causes the driverstation to not be able to connect to the robot, even though it can connect to the radio. Using another laptop is not feasible right now. I hypothesize the issue occurs on the side of the laptop.

[Mark McLeod]

The standard questions apply:
- What is the operating system on the troublesome PC?
- Are all firewalls off?
- All anti-virus off?
- Extra NIC's Disabled?
- Is the mDNS service running (NI mDNS Responder Service)?
- Is anything listed when you click on the arrow beside the team number on the Driver Station Setup tab?

If Windows 10 there are a couple of extra steps to turn things off.

[Hsifeulbhsifder]

It is a windows 10 laptop. Firewalls and antivirus are off. Not sure if the extra NIC's are disabled. nimDNSResponder is running. Robot Radio is the only green light on the ds setup tab.

[rfolea]

Is the laptop set for static ip or dhcp?

[Hsifeulbhsifder]

Originally Posted by rfolea

Is the laptop set for static ip or dhcp?

It is set to DHCP.

[Mark McLeod]

For Windows 10 there is an additional step to turning off the firewall.
MamaSpoldi reported this one:
- On the regular firewall page is a link to Advanced settings.
- The Advanced settings page will be divided into several sections, but at the bottom of the first section (Overview) will be another link to Windows firewall properties.
- Under that turn the first item from On to Off.
- Then reboot the Win 10 machine for it to take effect.

[tr6scott]

We had a almost 2 hours FTA visit at Waterford Thursday night. Not happy, could not get through inspection because our drivers station would not connect with robot, to power the pneumatic tests. Many, Many things were checked and tested, and after the roborio was reflashed and re firmwared and reloaded something clicked and it started working. Arron the FTA is excellent, and very knowledgeable, have worked with him in the past, and always a pleasure.

I have been posting our issues with this for months now, we were a beta test team. There is something still a miss, somewhere.

I can plug in last years dlink, and everything works, and quick.

The one thing I did learn this weekend, is the new system needs IPv6 enabled. We always turned that off in the past. Maybe it will help someone.

[Hsifeulbhsifder]

Originally Posted by Mark McLeod

For Windows 10 there is an additional step to turning off the firewall.
MamaSpoldi reported this one:
- On the regular firewall page is a link to Advanced settings.
- The Advanced settings page will be divided into several sections, but at the bottom of the first section (Overview) will be another link to Windows firewall properties.
- Under that turn the first item from On to Off.
- Then reboot the Win 10 machine for it to take effect.

Did this, but to no avail. The issue still exists.

[Mark McLeod]

Try Disabling/reEnabling the NIC you are using to connect the PC.

[Alan Anderson]

We have one laptop where the Driver Station doesn't want to make an initial network connection to the robot until we physically reset the roboRIO. It's a minor hassle so far.

[Tom Line]

I know this is slightly off topic, but since someone mentioned windows 10....

Be very aware of windows 10 and all the helpful features microsoft has created. For instance our driver station laptop managed to download an update while in the competition venue and rebooted and installed it - without our giving permission. This wouldn't have been such a problem if we weren't trying to USE IT with the robot to, you know.... drive.

It also re-enabled the firewall during the update, causing us 20 minutes of "why can't we connect to the robot" afterwards.

Windows 10 has a fantastic feature where it doesn't even have to connect to the internet to download updates. As long as another windows machine has it on the network you are connected to it will utilize a peer to peer system to grab the update.

[SuperBK]

Can you ping the roborio by host name? Does it display the correct IP when you ping? You might try ipconfig /flushdns (from a prompt) to clear any cached names.

Has anyone by chance modified the hosts file by adding the host name to it?

We switched to static addresses this year, added its name to the hosts file and connected at our first district competition just fine. We set to roboRio to .2 and the driver station to .5 Note that the driver's station must have a mask of 255.0.0.0. Also, I believe we did turn off IPv6 on the DS. I haven't heard about needing it. Maybe Greg McKaskle could comment on that.

The other tip that keeps coming up is plugging the roborio into the connector on the radio closest to the power plug.

Brian

[rich2202]

Originally Posted by Hsifeulbhsifder

but we can connect via IP (10.54.28.90)

Try giving your RoboRio the IP address of: 10.54.28.2

[tr6scott]

Was told the IPv6 has something to do with the Driver Station idiot lights on the communications tab. Even when it was working the Driver Station never reported the "correct" lights.

Enet Link
DS Radio
Robot Radio
Robot
FMS

In pit only Robot and Robot Radio would turn green, yet we could enable the robot.

[Mark McLeod]

Originally Posted by tr6scott

Was told the IPv6 has something to do with the Driver Station idiot lights on the communications tab. Even when it was working the Driver Station never reported the "correct" lights.

Enet Link
DS Radio
Robot Radio
Robot
FMS

In pit only Robot and Robot Radio would turn green, yet we could enable the robot.

That sounds normal.
In the Pit the lights that are green depend on how you tether.
You'll see different lights while on USB then on Ethernet directly to the roboRIO, or Ethernet through the robot radio.