I'm trying to set up my Rio for Ethernet since my HPNA card flaked out on me. The Rio Receiver gets an IP from my DHCP server, but never seems to talk to the music software. An icon for it shows up in the software.

The Rio shows "Searching for Music Server" for several minutes but then times out and shows the IP info, which it got from the DHCP server. I also tried using the Rio software as a DHCP server with the same result.

I put a packet sniffer on the wire and I see the Rio come up and get it's IP. The server then starts sending out it's "What's going down?" status messages but eventually the Rio stops responding to them (then it shows IP info on the LCD).

Any ideas? The Rio is plugged in to a switch which crosses a wireless bridge to the main network. The wireless connection works fine as I tested it with my notebook. Putting my notebook on the same switch with the Rio software doesn't work either.

Update:

It's the wireless. I just tried my notebook on the same switch again and it works every time. Not sure what the deal was earlier. But, it's the wireless. Any ideas why? I can access the rest of the network with NO problems while plugged in to the switch and going over the wireless bridge.

Using the sniffer I see packets from the Rio on the other side of the bridge, but the connection is never fully made.... HELP.

Is this network set up in a bridged fashion or are there two separate subnets? Is the SSDP packet sent on port 21075 from the Rio making across the wireless LAN link?

It's bridged with a single subnet. Everything has a 192.168.100.0/24 address. Yes, I see that SSDP go across. I see it look for a server using the uPnP string. Then...nothing.

Really weird.

I'm sure this really doesn't help, but I have been unsuccessful in using a Rio Receiver or Audiotron with an Orinoco EC. Sometimes it would work, then it would not work. It really bugged me... a lot. In fact it bugged me enough to put my wireless router/switch and music server in my stereo cabinet.

I tried getting it working for months alternating between the Rio being wireless and the server being wireless. Each setup caused the same problem you have after an short period of working. I then realized that if I reset the router (SMC Barricade), the problem would be fixed.... for a short period of time. I am reasonably sure that the problem was with the SMC router. If you have an SMC, that would only serve to prove my theory. I have been able to "crash" this SMC router on other occasions as well with large file transfers.

Both to Rob and Netjunkie:

Have you guys tried getting more recent firmware for the routers?

Running the latest then and now.

FYI i'm using the linksys wep11 wireless access point as my ehternet bridge for the empeg (configured in client mode) works fine..

Had a wierd problem w/ dhcp though; w2k's dhcp implementation didn't agree with it..

(w2k's nat-auto dhcp works fine though..)
-m

I'm using Linksys WAP11 v2.2s on both sides. I have one connected to my wired network acting as a normal AP and the other one is sitting in my theater cabinet running in Client Access mode acting as a bridge.

I'm running the latest firmware on both. It's really odd since I see the Rio going across the bridge on the sniffer. I've even seen it ask for the descriptor.xml file, but that's it. It just sits and sits and eventually times out.

I have the sniffer traces from Network Monitor saved if anyone is interested.

I had the exact same symptoms although not with the same hardware and found that the Rio Receiver did not get along with the DHCP in WinProxy. As soon as I had my linux server do the DHCP instead of WinProxy all three of my rios started working. Could you try a different DHCP server?

So far I've tried Windows 2000 Server DHCP and the Rio Software DHCP. It gets an IP from both..but then nothing....

Have you tried to remove the power, I mean physically unplug the RIO, since you switched from the HPNA?

I know, but sometimes the fix is easier than we think...
:d:

Yep, did that...like 20 times. I did that each time I changed DHCP systems to make sure everything got cleared.

I fixed it. I read on here before that the Rio sometimes doesn't like switches. I had this on a dumb (non-managed, no spanning-tree) 10/100 Switching Hub. It doesn't sit and wait for negotiation like most managed switches, so I thought I was safe.

As a last resort today I dug out an old 10Mb hub at the office and tried that. Fired up right away. It's odd that some packets made it across but it never worked all the way. I'm just glad it works. It's not a big deal since the only two items on that side of the bridge will be my Rio and the XBox (or other network enabled consoles and TiVo devices). But 10Mb shouldn't limit them, especially since my wireless is currently 11Mb/sec.

The odd question is, why did it work with the notebook on the switch, though? Timing issue maybe? Everything local maybe timing was fine, but across the switch and then the wireless bridge maybe it was too much or something.

Orinoco EC has been working fine for me, with Dell receivers and Empegs. Get some audio break up when you start playing sometimes, but fine after a few seconds.