I had my Rio Receiver running on HPNA but I had to remove the card so I could install a second NIC. Before, I could get the Rio functioning with the first installed NIC using a cross-over cable (The Riocar also worked with this setup). Now I cannot get the ARM software to recognize the Rio with the second installed NIC with cross-over cable.(the RioCar still functions on the second NIC).

I think I have researched and tried everything at his point...

Any suggestions?

Setup - XP, ARM1.04

Have you tried forcing the NIC to 10baseT half duplex?

Have you tried plugging both the computer and the Receiver into a cheap 10baseT hub?

Couple of things to check if you haven't done so:

Make sure the correct adapter is listed under IP configuration screen of the ARM, since you have 2 ethernet adapters. Also, the box at the bottom of the IP configuration should be checked.

Make sure that you have unplugged the RIO unit, waited a bit, then restarted the unit. Try with and without auto configuration enabled on the ARM IP configuration screen. I usually deleted the old units showing up in ARM prior to this step.

View network connections under Windows XP. Determine if ethernet adapter you are using has an IP address. You might try to let WIndows XP software bridge the 2 ethernet connections, then go to the IP configuration in ARM and use the bridge to serve up the Rios.

I had some annoying issues once I went to Windows XP and finally had to get rid of the multiple network adapters in my server to create stability. I currently have one ethernet card in the music server which connects to a cheap ($20) Linksys switch. Connected to the switch are other computers in the same room, a Rio, and a 2 wire router with HPNA support for the rest of the computers and Rios in my house. Its very stable now..

Good luck.

Hipped1 (and FAQmaster TFabris)
Thanks for the great, great tips. I tried all of them. I even, at his point, disabled the second ethernet NIC and am running (successfully) my cable broadband through a "cheap" 10baseT hub I have. I also enabled the empeg through this device (did I mention I love my empeg?). However...

Problems still exist. I can set the ARM software to Enable Autoconfiguration's IP using first address of :192.168.0.5 and second address of: 192.168.0.5 and even though the Receiver still fails to be recognized by the ARM software the "failure" IP address on the Receiver screen reads "info net:eth ip 192.168.0.2 255.255.255.240 g:24.136.179.XXX (g is my fixed cable IP address). At least the Rio receiving the IP address.

Sorry to be a pain but what next?... is this Receiver "baked"?


Sean in NC
510sRus

PS. Maybe I will sell this POS and make or buy another mlord home dock and carry my empeg around instead... hahaha

I'm not a networking expert so I'll pose the question to more knowledgeable users. Should the fixed cable IP address be showing up on the Rio screen or might this be part of Sean's connection issues?

eth ip 192.168.0.2 255.255.255.240 g:24.136.179.XXX

That means it's trying to get to ip 192.168.0.2 via your ethernet card (g = gateway). That won't work. Get to a command prompt and type "route print" That will print your routing table.

You need to make sure that your HPNA card is listed and can get to the 192.168.0.2/255.255.255.240 network.

If that doesn't work, post the output of route print, and I'll see if I can suggest something.

Ok, I did get the RIO Receiver working, abet temporarily. The problem was that I had the second Address not set the same as the first. It worked great. When I turn the unit off the ARM software cannot connect to the Rio again...

Setup:
Rio Receiver connected through a crossover cable to a NIC:

ARM settings:
First address: 192.168.0.2
Second address: 192.168.0.2
Network Mask: 255.255.255.0
Player IP address: 192.168.0.26 (changes each reboot)

NIC settings:
IP address: 192.168.0.1
Subnet Mask: 255.255.255.0
Gateway: blank

This thing is about to become a RIO Paperweight or a RIO Frisbee...

Sean in NC