[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).