need help with DHCP and NFS problem

I have an existing (WinProxy) DHCP server on 192.168.0.1 and the Audio Manager Windows software installed on 192.168.0.8. Anyways the rio receiver gets it's IP address (192.168.0.5) from the WinProxy box and then just sits there saying looking for music server. From reading on the internet - it looks like it's trying to NFS mount somewhere which brings me to my question:

How does it decide where to try to NFS mount? Is it trying to NFS mount on 192.168.0.1 where there is no Audio Manager software installed or is it trying to go to 192.168.0.8? How can I debug this? I desparately want to use my new Rio Receiver but I can't give up my WinProxy box because Starband (satellite internet) requires it

If you open up the server manager, does it see the receiver? You should have an icon for your receiver in the window. If not, the server isn't communicating with the receiver, and I'd imagine its not even getting as far as mounting the NFS share.

Go into the settings of the Server Software and disable DHCP. If you're feeding it an IP address from somewhere else, you won't need to have DHCP running on your RIO Server.

It should be trying to mount the NFS Share from your server, 192.168.0.8 in your case.

I don't know too much about the internals of the server, but Tony or Roger (and many others around here) may be able to give you some more tricks and tips.

:d:

It does a broadcast to find the NFS server. This should work fine as long as the server and the Rio Receiver are on the same subnet (in your case, they are).

Are you sure that the server software is running correctly? If your proxy is handing out DHCP addresses, then the Receiver manager doesn't need to be running for that.

Thanks for the reply - yes the server manager sees the receiver and I have an icon for the receiver but I'm pretty sure somehow the NFS mount is failing. I can use a web browser and go to the server manager and get a list of albums. The server manager (192.168.0.8) is also sending out "are you there" UDP messages but the rio receiver (192.168.0.5) isn't completely up (again I believe due to NFS mount failure).

Any other thoughts on solving this? I can't wait to use my new toy

Is there anything displayed on the Receiver's screen?

Can you explain what you mean the Receiver manager doesn't need to be running for that? I have the Enable Audio Configuration disabled but I need the Receiver manager software to dish out the boot image and the song lists, etc.

Just the RIO splash screen and the message Searching for a music server.

Is your proxy software blocking the necessary ports that are required for the player-to-server communication?

It (WinProxy) is not blocking the UDP broadcasts as I can see them using Ethereal but I don't see any NFS traffic so I'll look into that.

WinProxy and the Rio Receiver don't get along at all - I've tried all the different settings I could think of in WinProxy and no go. Could someone who understands the rio receiver/networking better than I install WinProxy (www.winproxy.com) and help me out with getting the two to co-exist.

Thanks so much,

Brent

Perhaps you need to tell the proxy server to port-forward the necessary ports?

Which ports would those be? Do I need to port-forward even though it's on the local network (192.168.0.x)? I thought that you only needed to do that to get in/out of the external network.

Well, I don't know how your proxy server is configured, so I don't know. And I'm not clear on which ports are used (the FAQ links a page that shows the ports used for HTTP but I don't know about NFS). But I thought that any time you run something like this through a proxy, you have to let the proxy know about it and handle it appropriately. Proxies are not always transparent.

Well I've made some progress! The Rio Receiver is INCOMPATIBLE with the WinProxy DHCP server. I haven't figured out why but when I disable the WinProxy DHCP the Rio Receiver works fine. So WinProxy is routing NFS, HTTP, etc properly.

hmmm this sounds a little like a problem I had...

I've got a linksys router (running DHCP) though instead of WinProxy.

What I wound up doing is decreasing the number of DHCP clients the router can serve (dropped it to like 16, in the range 192.168.1.10 to 192.168.1.25), then set the PC that is running the receiver manager to a static IP address OUTSIDE the range of DHCP addresses (192.168.1.50) and then telling it to serve music to receivers in the range of DHCP (go to "tools"->"IP Configuration"->"Enable Autoconfig")

But it could be some other part of my setup that forced this solution (I run wireless to one receiver)

~fiddy