The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Re: rio receiver 'lost' :(


  • To: <ukha_d@xxxxxxx>
  • Subject: RE: Re: rio receiver 'lost' :(
  • From: "Jon Bhargava" <jonathan.bhargava@xxxxxxx>
  • Date: Sat, 2 Mar 2002 14:05:12 -0000
  • Delivered-to: mailing list ukha_d@xxxxxxx
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

thanks Patrick, all seems to be ok now :)

-----Original Message-----
From: PatrickLidstone [mailto:patrickl@xxxxxxx]
Sent: Saturday, March 02, 2002 13:53
To: ukha_d@xxxxxxx
Subject: [ukha_d] Re: rio receiver 'lost' :(


--- In ukha_d@y..., "Brian G. Reynolds"
<brian.g.reynolds@n...> wrote:
> Hi Jon, I think the DDAR/Rio looks for the server.
>

Yes, the RIO requests an IP address from the PC server when the RIO
boots. On the DDAR this happens during when "Searching for
server" is
displayed on the LCD - I guess the RIO says something similar. At the
point where the address is successfully allocated, the server
software icon turns from red to blue and the DDAR/RIO should appear
in the Audio Receiver Manager.
It's also worth checking the Tools/IP Configuration settings to
ensure that (a) AutoConfiguration is enabled (b) against the right
interface if your PC has more than one network connection (unlikely)
and (c) that both the IP address range AND netmask is right for your
network.

Patrick





For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/





Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.