I've had my rio receivers for about 9 months. I've only setup one place to hook them up. First one worked great for about 4-5 months and then stopped powering up correctly. It would come up with a 169.x.x.x address (my dhcp server is supposed to hand out stuff in the 192.168.1.100+ range).

So I swapped over to the other unit and it worked fine for another 4-5 months. Now it is doing the same thing!

So I loaded ethereal on my PC and watched what was happening. They are both doing the same thing. They make a DHCP request, then almost immediately after arp out a who-has the 169.x.x.x address (I guess checking their backup IP?), my dhcp server comes back with a perfectly acceptable response but the rio ignores it. It goes through this cycle a few times and then the rio decides on the 169.x.x.x address.

It then makes a upnp request to my server and my server responds with a proper looking url back to my server on port 21076 to /descriptor.xml. But it just seems to ignore this request and ask the same thing, over and over again.

It's almost like these rios can talk but they can't listen on the ethernet ports. But two failing the same way? It just seems unlikely.

What gives? Any suggestions would be greatly appreciated.

Thanks,

Al Youngwerth

P.S. I can post a captured trace if that'd help

Dumb question, but did you check/change/mangle the cable? I had exactly this problem with some cabling, caused by one of the pairs being broken.

I realize this is an ancient thread, but I was looking for info on the Central serving Receivers, and couldn't find what I was looking for. Maybe some more advanced future civilization will find this and wink knowingly about it...

Although it appears the Central might be capable of serving DHCP if hacked properly, apparently it does not do this--my sole Rio Receiver always gets an IP address from my server box (presently a Magnia SG10) in the range of 192.168.1.120-125 (along w/a few other gizmos I have that need DHCP).

Since Rio had to assume it would have some customers whose only network would be a Central and one or more Receivers, they must have planted some way to deal with this, i.e. maybe if the Receiver can't find a DHCP server on the network, it takes on a 169.x.x.x number and by some other magic (hey, I'm no TCP/IP expert!) establishes communication with the Central.

Dunno what the original poster's problem turned-out to be, but I'd guess his DHCP server was down at some inopportune moment, or a hub/switch failure occurred somewhere, and the Receivers got confused about it.

I wish the Central served-up DHCP since it is on 24/7--maybe some day when I've become a self-taught expert on Linux I will hack-in to it and make that work...

Okay, here it is. Addresses are my own, of course you would change them to whatever you wanted on your LAN:

Main menu.
Setup menu.
Network configuration.
External Adapter 1.
Configuration: Manual.
IP address: 192.168.1.4
Subnet mask 255.255.0.0 (I do this special so two local subnets can both reach the Central)
Defailt gateway: 0.0.0.0
Serve receiver units: Checked.
Use this adapter for internet lookup: Checked.

AT THIS POINT pressing the down arrow button one more time will get you to the RECEIVERS... button. Press the right arrow button and BOOM, you're in the screen you couldn't find before. On mine I'm set to:
First address: 192.168.1.90
Last address: 192.168.1.99
Subnet mask: 255.255.0.0
DONE.